Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Scaling Science
Search
Matt Wood
November 21, 2012
Science
3
500
Scaling Science
Introducing five principles for reproducibility.
Matt Wood
November 21, 2012
Tweet
Share
More Decks by Matt Wood
See All by Matt Wood
Field Notes from Expeditions in the Cloud
mza
2
390
A Platform for Big Data
mza
6
740
The Data Lifecycle
mza
5
500
Provision Throughput Like a Boss
mza
0
440
Impact of Cloud Computing: Life Sciences
mza
2
850
Latency's Worst Nightmare: Performance Tuning Tips and Tricks
mza
4
1.1k
Under the Covers of DynamoDB
mza
4
1k
From Analytics to Intelligence: Amazon Redshift
mza
9
990
High Performance Web Applications
mza
6
630
Other Decks in Science
See All in Science
点群ライブラリPDALをGoogleColabにて実行する方法の紹介
kentaitakura
1
250
観察研究における因果推論
nearme_tech
PRO
1
240
Marvin Minsky - 'Society of Mind'
__ymgc__
2
110
Introd_Img_Process_2_Frequ
hachama
0
550
SciPyDataJapan 2025
schwalbe10
0
230
(論文読み)贈り物の交換による地位の競争と社会構造の変化 - 文化人類学への統計物理学的アプローチ -
__ymgc__
1
220
ほたるのひかり/RayTracingCamp10
kugimasa
1
670
データベース05: SQL(2/3) 結合質問
trycycle
PRO
0
680
創薬における機械学習技術について
kanojikajino
16
5.2k
How were Quaternion discovered
kinakomoti321
2
1.3k
Valuable Lessons Learned on Kaggle’s ARC AGI LLM Challenge (PyDataGlobal 2024)
ianozsvald
0
370
マウス肝炎ウイルス感染の遺伝子発現へのテンソル分解の適用によるSARS-CoV-2感染関連重要ヒト遺伝子と有効な薬剤の同定
tagtag
0
100
Featured
See All Featured
Code Reviewing Like a Champion
maltzj
523
40k
The Cult of Friendly URLs
andyhume
78
6.4k
Being A Developer After 40
akosma
91
590k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
42
2.3k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
PRO
180
53k
Why Our Code Smells
bkeepers
PRO
336
57k
How to Ace a Technical Interview
jacobian
276
23k
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
194
16k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
45
9.6k
Designing for Performance
lara
608
69k
The Art of Programming - Codeland 2020
erikaheidi
54
13k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
106
19k
Transcript
Scaling Science
[email protected]
Dr. Matt Wood
Hello
Science
Beautiful, unique.
Impossible to re-create
Snowflake Science
Reproducibility
Reproducibility scales science
Reproduce. Reuse. Remix.
Value++
None
How do we get from here to there? 5PRINCIPLES REPRODUCIBILITY
OF
1. Data has Gravity 5 PRINCIPLES REPRODUCIBILITY OF
Increasingly large data collections
1000 Genomes Project: 200Tb
Challenging to obtain and manage
Expensive to experiment
Large barrier to reproducibility
Data size will increase
Data integration will increase
Data dependencies will increase
Move data to the users
Move data to the users X
Move tools to the data
Place data where it can consumed by tools
Place tools where they can access data
None
None
None
Canonical source
None
More data, more users, more uses, more locations
Cost
Force multiplier
Cost
Complexity
Cost and complexity kill reproducibility
Utility computing
Availability
Pay-as-you-go
Flexibility
Performance
CPU + IO
Intel Xeon E5 NVIDIA Tesla GPUs
240 TFLOPS
90 - 120k IOPS on SSDs
Performance through productivity
Cost
On-demand access
Reserved capacity
100% Reserved capacity
100% Reserved capacity On-demand
100% Reserved capacity On-demand
Spot instances
Utility computing enhanced reproducibility
None
2. Ease of use is a pre-requisite 5 PRINCIPLES REPRODUCIBILITY
OF
http://headrush.typepad.com/creating_passionate_users/2005/10/getting_users_p.html
Help overcome the suck threshold
Easy to embrace and extend
Choose the right abstraction for the user
$ ec2-run-instances
$ starcluster start
None
Package and automate
Package and automate Amazon machine images, VM import
Package and automate Amazon machine images, VM import Deployment scripts,
CloudFormation, Chef, Puppet
Expert-as-a-service
None
None
1000 Genomes Cloud BioLinux
None
Your HiSeq data Illumina BaseSpace
Architectural freedom
Freedom of abstraction
3. Reuse is as important as reproduction 5 PRINCIPLES REPRODUCIBILITY
OF
Seven Deadly sins of Bioinformatics: http://www.slideshare.net/dullhunk/the-seven-deadly-sins-of-bioinformatics
Seven Deadly sins of Bioinformatics: http://www.slideshare.net/dullhunk/the-seven-deadly-sins-of-bioinformatics
Infonauts are hackers
They have their own way of working
The ‘Big Red Button’
Fire and forget reproduction is a good first step, but
limits longer term value.
Monolithic, one-stop-shop
Work well for intended purpose
Challenging to install, dependency heavy
Di cult to grok
Inflexible
Infonauts are hackers: embrace it.
Small things. Loosely coupled.
Easier to grok
Easier to reuse
Easier to integrate
Lower barrier to entry
Scale out
Build for reuse. Be remix friendly. Maximize value.
4. Build for collaboration 5 PRINCIPLES REPRODUCIBILITY OF
Workflows are memes
Reproduction is just the first step
Bill of materials: code, data, configuration, infrastructure
Full definition for reproduction
Utility computing provides a playground for bioinformatics
Code + AMI + custom datasets + public datasets +
databases + compute + result data
Code + AMI + custom datasets + public datasets +
databases + compute + result data
Code + AMI + custom datasets + public datasets +
databases + compute + result data
Code + AMI + custom datasets + public datasets +
databases + compute + result data
Package, automate, contribute.
Utility platform provides scale for production runs
Drug discovery on 50k cores: Less than $1000
5. Provenance is a first class object 5 PRINCIPLES REPRODUCIBILITY
OF
Versioning becomes really important
Especially in an active community
Doubly so with loosely coupled tools
Provenance metadata is a first class entity
Distributed provenance
1. Data has gravity 2. Ease of use is a
pre-requisite 3. Reuse is as important as reproduction 4. Build for collaboration 5. Provenance is a first class object 5PRINCIPLES REPRODUCIBILITY OF
None
Thank you aws.amazon.com @mza
[email protected]