<?xml version="1.0" encoding="UTF-8"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:lang="en">
  <teiHeader>
    <fileDesc>
      <titleStmt>
        <title>Big Data: Astronomical or Genomical?</title>
        <author>Zachary D. Stephens</author>
        <author>Skylar Y. Lee</author>
        <author>Faraz Faghri</author>
        <author>et al.</author>
      </titleStmt>
      <publicationStmt>
        <p>Tag layer of the DHSS Meta-Tagging Project. The article text is reproduced from the
           staged copy named in sourceDesc and is not altered; the tags are held separately in
           standOff so that overlapping and nested spans are preserved.</p>
      </publicationStmt>
      <sourceDesc>
        <bibl>
          <title>Big Data: Astronomical or Genomical?</title>
          <date>2015</date>
          <publisher>PLOS Biology</publisher>
          <idno type="DOI">10.1371/journal.pbio.1002195</idno>
          
          <idno type="record">stephens2015-genomical</idno>
          <note type="staged-file">stephens2015-genomical.txt, the project's staged copy</note>
          <note type="text-sha1">59d29b7e3ca9b8886f25d25ff649d5447c52db39</note>
          <note type="rights">open-access</note>
        </bibl>
      </sourceDesc>
    </fileDesc>
    <profileDesc>
      <textClass><keywords><term>biology</term></keywords></textClass>
      <particDesc>
        <person xml:id="paper"><p>the paper's own words</p></person>
        <person xml:id="tagger"><p>the tag layer; a sentence written by the tagger about the
          paper, always anchored to a quotation but not itself a quotation</p></person>
      </particDesc>
    </profileDesc>
    <revisionDesc>
      <change when="2026-10-06"
              who="build_paper_edition.py">131 spans located by searching the stored text for the quote's exact words, allowing any whitespace between them</change>
    </revisionDesc>
  </teiHeader>
  <standOff>
    <spanGrp type="tags">
      <span xml:id="t0" from="#a15" to="#a17" type="object_of_study" ana="#object_of_study" resp="#paper">The computational demands of genomics in 2025 - acquisition, storage, distribution and analysis - set against astronomy, YouTube and Twitter.</span>
      <span xml:id="t1" from="#a1" to="#a4" type="research_question" ana="#research_question" resp="#paper">Genomics is growing fast, but is it about to become the most computationally demanding Big Data science, or merely one among several?</span>
      <span xml:id="t2" from="#a7" to="#a10" type="contribution" ana="#contribution" resp="#paper">A like-for-like projection across four domains showing genomics is on par with or ahead of all of them on every phase of the data lifecycle.</span>
      <span xml:id="t3" from="#a73" to="#a75" type="claim_type" ana="#claim_type" resp="#paper">prediction</span>
      <span xml:id="t4" from="#a42" to="#a45" type="phenomenon" ana="#phenomenon" resp="#paper">growth of genomic data volume</span>
      <span xml:id="t5" from="#a15" to="#a17" type="method" ana="#method" resp="#paper">computational-model<term>computational-model</term></span>
      <span xml:id="t6" from="#a15" to="#a17" type="mechanisms" ana="#mechanisms[0]" resp="#tagger" cert="1.0">mechanisms<term>a common four-part framework - the dataset life cycle - is what makes four unlike domains comparable; without it the comparison has no cells to fill</term></span>
      <span xml:id="t7" from="#a24" to="#a25" type="mechanisms" ana="#mechanisms[1]" resp="#tagger" cert="1.0">mechanisms<term>acquisition architecture differs by domain: astronomy centralises at a few facilities, YouTube and Twitter distribute under standard protocols, genomics distributes with no standard format at all</term></span>
      <span xml:id="t8" from="#a71" to="#a72" type="mechanisms" ana="#mechanisms[2]" resp="#tagger" cert="1.0">mechanisms<term>the projection is anchored on a doubling time, and holds under three different ones - seven, twelve or eighteen months - which is what makes it robust rather than a single extrapolation</term></span>
      <span xml:id="t9" from="#a11" to="#a12" type="mechanisms" ana="#mechanisms[3]" resp="#tagger" cert="1.0">mechanisms<term>a domain&#x27;s data footprint is set by what it DISCARDS, not only by what it acquires - particle physics generates massive volumes and keeps almost none</term></span>
      <span xml:id="t10" from="#a2" to="#a3" type="limitations" ana="#limitations[0]" resp="#tagger">it is not known whether genomics needs will exceed other Big Data domains<note>what this limits: the paper&#x27;s central comparative question, which it leaves open: IT IS NOT KNOWN WHETHER THE NEEDS OF GENOMICS WILL EXCEED OTHER BIG DATA DOMAINS</note></span>
      <span xml:id="t11" from="#a67" to="#a68" type="limitations" ana="#limitations[1]" resp="#tagger">Projections become less reliable the further ahead they reach.<note>what this limits: the far end of the projections: THE PROJECT GROWTH BECOMES MORE UNPREDICTABLE THE FURTHER OUT WE CONSIDER</note></span>
      <span xml:id="t12" from="#a76" to="#a77" type="limitations" ana="#limitations[2]" resp="#tagger">Storage estimates omit the replication factor for redundancy.<note>what this limits: every storage figure quoted: OUR ESTIMATES HERE IGNORE THE REPLICATION FACTOR THAT MULTIPLIES STORAGE NEEDS BY ~4, FOR REDUNDANCY</note></span>
      <span xml:id="t13" from="#a13" to="#a14" type="limitations" ana="#limitations[3]" resp="#tagger">Particle physics, a fifth massive data producer, was deliberately left out of the comparison.<note>what this limits: the scope of the four-domain comparison: WE DO NOT INCLUDE THE DOMAIN IN FULL DETAIL HERE - particle physics, a fifth massive producer, is left out</note></span>
      <span xml:id="t14" from="#a78" to="#a79" type="limitations" ana="#limitations[4]" resp="#tagger">Storage projections are contingent on sequencing accuracy and application.<note>what this limits: the storage projections specifically: PROJECTIONS OF STORAGE REQUIREMENTS FOR SEQUENCE DATA DEPEND ON THE ACCURACY AND APPLICATION OF THE SEQUENCING</note></span>
      <span xml:id="t15" from="#a13" to="#a14" type="limitations" ana="#limitations[5]" resp="#tagger" cert="1.0">Particle physics was excluded from the full comparison, so the framework is applied to four domains rather than to the five the authors identify.<note>duplicate of: limitations[3] · what this limits: the same scope as limitations[3] - four domains compared, not five</note></span>
      <span xml:id="t16" from="#a67" to="#a68" type="limitations" ana="#limitations[6]" resp="#tagger" cert="1.0">The authors state the projections become less reliable the further out they run.<note>duplicate of: limitations[1] · what this limits: the same scope as limitations[1] - reliability falls with horizon</note></span>
      <span xml:id="t17" from="#a61" to="#a62" type="limitations" ana="#limitations[7]" resp="#tagger" cert="1.0">The archived data is a small and unquantified fraction of what is produced, so the baseline for the whole projection is an estimate from instrument specifications rather than a count.<note>what this limits: the baseline the whole projection is built from: THE 3.6 PETABASES REPRESENT A SMALL FRACTION OF THE TOTAL PRODUCED; MOST OF IT IS NOT YET IN THESE ARCHIVES</note></span>
      <span xml:id="t18" from="#a49" to="#a52" type="limitations" ana="#limitations[8]" resp="#tagger" cert="0.9">Bases are converted to bytes at a stated approximate factor, which propagates into every storage figure.<note>what this limits: every bases-to-bytes conversion in the paper: AN APPROXIMATE CONVERSION FACTOR TO USE IN INTERPRETING THESE NUMBERS IS 4 BASES = 1 BYTE - stated as approximate, and it propagates</note></span>
      <span xml:id="t19" from="#a111" to="#a112" type="transfers" ana="#transfers[0]" resp="#tagger">large-scale machine learning and big-data computing infrastructure applied to genomics</span>
      <span xml:id="t20" from="#a88" to="#a89" type="transfers" ana="#transfers[1]" resp="#tagger" cert="0.85">the data-retention practice of particle physics - discard the raw data after processing and keep only the reduced product - held up as the lesson genomics should learn as sequencing volumes outgrow storage</span>
      <span xml:id="t21" from="#a40" to="#a41" type="concepts" ana="#concepts[0]" resp="#paper">genomics<term>genomics</term></span>
      <span xml:id="t22" from="#a1" to="#a4" type="concepts" ana="#concepts[1]" resp="#paper">big data<term>big data</term></span>
      <span xml:id="t23" from="#a15" to="#a17" type="concepts" ana="#concepts[4]" resp="#paper" cert="1.0">life cycle<term>life cycle</term></span>
      <span xml:id="t24" from="#a18" to="#a20" type="concepts" ana="#concepts[5]" resp="#paper" cert="0.85">acquisition<term>acquisition</term></span>
      <span xml:id="t25" from="#a22" to="#a23" type="concepts" ana="#concepts[6]" resp="#paper" cert="1.0">astronomy<term>astronomy</term></span>
      <span xml:id="t26" from="#a11" to="#a12" type="concepts" ana="#concepts[7]" resp="#paper" cert="1.0">particle physics<term>particle physics</term></span>
      <span xml:id="t27" from="#a63" to="#a66" type="concepts" ana="#concepts[8]" resp="#paper" cert="1.0">sequencing capacity<term>sequencing capacity</term></span>
      <span xml:id="t28" from="#a71" to="#a72" type="concepts" ana="#concepts[9]" resp="#paper" cert="1.0">Moore’s law<term>Moore’s law</term></span>
      <span xml:id="t29" from="#a15" to="#a16" type="concepts" ana="#concepts[10]" resp="#paper" cert="0.95">storage<term>storage</term></span>
      <span xml:id="t30" from="#a15" to="#a16" type="concepts" ana="#concepts[11]" resp="#paper" cert="0.95">distribution<term>distribution</term></span>
      <span xml:id="t31" from="#a15" to="#a16" type="concepts" ana="#concepts[12]" resp="#paper" cert="0.95">analysis<term>analysis</term></span>
      <span xml:id="t32" from="#a80" to="#a81" type="concepts" ana="#concepts[13]" resp="#paper" cert="0.95">effective data compression<term>effective data compression</term></span>
      <span xml:id="t33" from="#a78" to="#a81" type="concepts" ana="#concepts[14]" resp="#paper" cert="0.95">storage requirements<term>storage requirements</term></span>
      <span xml:id="t34" from="#a80" to="#a81" type="concepts" ana="#concepts[15]" resp="#paper" cert="0.95">compressive genomics<term>compressive genomics</term></span>
      <span xml:id="t35" from="#a82" to="#a83" type="concepts" ana="#concepts[16]" resp="#paper" cert="0.95">single-molecule sequencing technologies<term>single-molecule sequencing technologies</term></span>
      <span xml:id="t36" from="#a82" to="#a83" type="concepts" ana="#concepts[17]" resp="#paper" cert="0.95">raw sequence data<term>raw sequence data</term></span>
      <span xml:id="t37" from="#a84" to="#a85" type="concepts" ana="#concepts[18]" resp="#paper" cert="0.95">delta encoding<term>delta encoding</term></span>
      <span xml:id="t38" from="#a84" to="#a85" type="concepts" ana="#concepts[19]" resp="#paper" cert="0.95">list of variants relative to a reference collection<term>list of variants relative to a reference collection</term></span>
      <span xml:id="t39" from="#a86" to="#a87" type="concepts" ana="#concepts[20]" resp="#paper" cert="0.95">data reduction<term>data reduction</term></span>
      <span xml:id="t40" from="#a86" to="#a87" type="concepts" ana="#concepts[21]" resp="#paper" cert="0.95">real-time analysis<term>real-time analysis</term></span>
      <span xml:id="t41" from="#a86" to="#a87" type="concepts" ana="#concepts[22]" resp="#paper" cert="0.95">“streaming” algorithms<term>“streaming” algorithms</term></span>
      <span xml:id="t42" from="#a86" to="#a87" type="concepts" ana="#concepts[23]" resp="#paper" cert="0.95">nonstreaming counterparts<term>nonstreaming counterparts</term></span>
      <span xml:id="t43" from="#a90" to="#a91" type="concepts" ana="#concepts[24]" resp="#paper" cert="0.95">hierarchical systems<term>hierarchical systems</term></span>
      <span xml:id="t44" from="#a92" to="#a93" type="concepts" ana="#concepts[25]" resp="#paper" cert="0.95">cloud computing<term>cloud computing</term></span>
      <span xml:id="t45" from="#a92" to="#a93" type="concepts" ana="#concepts[26]" resp="#paper" cert="0.95">bandwidth for distribution of genomic data<term>bandwidth for distribution of genomic data</term></span>
      <span xml:id="t46" from="#a92" to="#a93" type="concepts" ana="#concepts[27]" resp="#paper" cert="0.95">remote machines that already have data<term>remote machines that already have data</term></span>
      <span xml:id="t47" from="#a92" to="#a93" type="concepts" ana="#concepts[28]" resp="#paper" cert="0.95">computing resources necessary for distribution<term>computing resources necessary for distribution</term></span>
      <span xml:id="t48" from="#a94" to="#a95" type="concepts" ana="#concepts[29]" resp="#paper" cert="0.95">data reliability<term>data reliability</term></span>
      <span xml:id="t49" from="#a94" to="#a95" type="concepts" ana="#concepts[30]" resp="#paper" cert="0.95">security<term>security</term></span>
      <span xml:id="t50" from="#a94" to="#a95" type="concepts" ana="#concepts[31]" resp="#paper" cert="0.95">privacy<term>privacy</term></span>
      <span xml:id="t51" from="#a94" to="#a95" type="concepts" ana="#concepts[32]" resp="#paper" cert="0.95">Homomorphic encryption systems<term>Homomorphic encryption systems</term></span>
      <span xml:id="t52" from="#a96" to="#a97" type="concepts" ana="#concepts[33]" resp="#paper" cert="0.95">Variant calling<term>Variant calling</term></span>
      <span xml:id="t53" from="#a98" to="#a99" type="concepts" ana="#concepts[34]" resp="#paper" cert="0.95">Whole genome alignment<term>Whole genome alignment</term></span>
      <span xml:id="t54" from="#a100" to="#a101" type="concepts" ana="#concepts[35]" resp="#paper" cert="0.95">CPU capabilities<term>CPU capabilities</term></span>
      <span xml:id="t55" from="#a100" to="#a101" type="concepts" ana="#concepts[36]" resp="#paper" cert="0.95">input/output (I/O) hardware<term>input/output (I/O) hardware</term></span>
      <span xml:id="t56" from="#a100" to="#a101" type="concepts" ana="#concepts[37]" resp="#paper" cert="0.95">parallel I/O hardware and algorithms<term>parallel I/O hardware and algorithms</term></span>
      <span xml:id="t57" from="#a102" to="#a103" type="concepts" ana="#concepts[38]" resp="#paper" cert="0.95">integrative approaches<term>integrative approaches</term></span>
      <span xml:id="t58" from="#a102" to="#a103" type="concepts" ana="#concepts[39]" resp="#paper" cert="0.95">single advance or technology<term>single advance or technology</term></span>
      <span xml:id="t59" from="#a104" to="#a105" type="concepts" ana="#concepts[40]" resp="#paper" cert="0.95">isolated, private data collections<term>isolated, private data collections</term></span>
      <span xml:id="t60" from="#a106" to="#a107" type="concepts" ana="#concepts[41]" resp="#paper" cert="0.95">trust among institutions, scientists, and the public<term>trust among institutions, scientists, and the public</term></span>
      <span xml:id="t61" from="#a108" to="#a109" type="concepts" ana="#concepts[42]" resp="#paper" cert="0.95">application programming interfaces (APIs)<term>application programming interfaces (APIs)</term></span>
      <span xml:id="t62" from="#a110" to="#a113" type="concepts" ana="#concepts[43]" resp="#paper" cert="0.95">large-scale machine learning systems<term>large-scale machine learning systems</term></span>
      <span xml:id="t63" from="#a114" to="#a115" type="concepts" ana="#concepts[44]" resp="#paper" cert="0.95">data science into graduate, undergraduate, and high-school curricula<term>data science into graduate, undergraduate, and high-school curricula</term></span>
      <span xml:id="t64" from="#a84" to="#a85" type="unhoused_relations" ana="#unhoused_relations[0]" resp="#tagger" cert="0.95">delta encoding → list of variants relative to a reference collection<note>Delta encoding represents genomes as reference-relative variant lists; represents-as is absent from the edge registry.</note></span>
      <span xml:id="t65" from="#a94" to="#a95" type="unhoused_relations" ana="#unhoused_relations[1]" resp="#tagger" cert="0.95">Homomorphic encryption systems → privacy<note>Homomorphic encryption enables controlled queries without raw-data disclosure; enables is absent from the edge registry.</note></span>
      <span xml:id="t66" from="#a106" to="#a107" type="unhoused_relations" ana="#unhoused_relations[2]" resp="#tagger" cert="0.95">trust among institutions, scientists, and the public → connecting these resources<note>Trust is a prerequisite for connecting genomic resources; prerequisite-for is absent from the edge registry.</note></span>
      <span xml:id="t67" from="#a108" to="#a109" type="unhoused_relations" ana="#unhoused_relations[3]" resp="#tagger" cert="0.95">application programming interfaces (APIs) → discovering and querying large datasets on remote systems<note>APIs enable discovery and query of remote datasets; enables is absent from the edge registry.</note></span>
      <span xml:id="t68" from="#a82" to="#a83" type="unhoused_relations" ana="#unhoused_relations[4]" resp="#tagger" cert="0.9">single-molecule sequencing technologies → raw sequence data<note>Mature long-read methods may eliminate the need to retain raw sequence data; enables-omission is absent from the edge registry.</note></span>
      <span xml:id="t69" from="#a5" to="#a6" type="senses" ana="#senses[0]" resp="#tagger" cert="1.0">Big Data - as a comparison class of domains, each with its own acquisition architecture, rather than as a property a dataset has</span>
      <span xml:id="t70" from="#a11" to="#a12" type="senses" ana="#senses[1]" resp="#tagger" cert="1.0">data volume - as ACQUIRED, which for particle physics is enormous</span>
      <span xml:id="t71" from="#a61" to="#a62" type="senses" ana="#senses[2]" resp="#tagger" cert="1.0">data volume - as STORED, which for genomics is a small fraction of what is produced and for particle physics is smaller still</span>
      <span xml:id="t72" from="#a15" to="#a16" type="senses" ana="#senses[3]" resp="#tagger" cert="0.95">Storage / distribution / analysis - three lifecycle components alongside acquisition</span>
      <span xml:id="t73" from="#a80" to="#a81" type="senses" ana="#senses[4]" resp="#tagger" cert="0.95">Compressive genomics - storage reduction constrained by decompression time and fidelity</span>
      <span xml:id="t74" from="#a82" to="#a83" type="senses" ana="#senses[5]" resp="#tagger" cert="0.9">Long-read sequencing - mature technology that may remove the need to retain raw reads</span>
      <span xml:id="t75" from="#a84" to="#a85" type="senses" ana="#senses[6]" resp="#tagger" cert="0.95">Delta encoding - retention of reference-relative variant lists instead of complete genomes</span>
      <span xml:id="t76" from="#a86" to="#a87" type="senses" ana="#senses[7]" resp="#tagger" cert="0.95">Streaming omics analysis - real-time inference performing at least as well as nonstreaming methods</span>
      <span xml:id="t77" from="#a90" to="#a91" type="senses" ana="#senses[8]" resp="#tagger" cert="0.95">Hierarchical genomic archive - data and summaries exposed at multiple compression and latency levels</span>
      <span xml:id="t78" from="#a92" to="#a93" type="senses" ana="#senses[9]" resp="#tagger" cert="0.95">Cloud genomic analysis - code moves to remote machines already holding the data</span>
      <span xml:id="t79" from="#a94" to="#a95" type="senses" ana="#senses[10]" resp="#tagger" cert="0.95">Homomorphic encryption - controlled analysis of encrypted data without revealing raw genomes</span>
      <span xml:id="t80" from="#a96" to="#a97" type="senses" ana="#senses[11]" resp="#tagger" cert="0.95">Variant calling - computationally intensive identification of variants in each individual genome</span>
      <span xml:id="t81" from="#a98" to="#a99" type="senses" ana="#senses[12]" resp="#tagger" cert="0.95">Whole-genome alignment - comparative method for phylogeny reconstruction and genome annotation</span>
      <span xml:id="t82" from="#a100" to="#a101" type="senses" ana="#senses[13]" resp="#tagger" cert="0.9">I/O bottleneck - data shuttling between storage and processors rather than CPU arithmetic</span>
      <span xml:id="t83" from="#a104" to="#a105" type="senses" ana="#senses[14]" resp="#tagger" cert="0.95">Genomic data sharing - protection against isolated collections too underpowered for subtle signals</span>
      <span xml:id="t84" from="#a69" to="#a70" type="alternatives" ana="#alternatives.claim_type" resp="#tagger">claim_type: prediction<note>a second reading reaching the same value. Recorded: prediction — note: a second reading reaching the same value from a different sentence. Not applied - a person decides.</note></span>
      <span xml:id="t85" from="#a5" to="#a6" type="alternatives" ana="#alternatives.method" resp="#tagger">method: comparative<note>a second reading DIFFERING from the recorded value. Recorded: computational-model — note: a second reading, verbatim-verified, disagreeing with the value on the record. Not applied - a person decides.</note></span>
      <span xml:id="t86" from="#a42" to="#a45" type="alternatives" ana="#alternatives.phenomenon" resp="#tagger">phenomenon: exponential growth of genomic sequence data relative to other Big Data domains<note>a second reading DIFFERING from the recorded value. Recorded: growth of genomic data volume — note: a second reading, verbatim-verified, disagreeing with the value on the record. Not applied - a person decides.</note></span>
      <span xml:id="t87" from="#a71" to="#a72" type="claim_relations" ana="#claim_relations[0]" resp="#tagger" cert="1.0">builds-on → the OmicsMaps catalogue of sequencing instruments and Illumina&#x27;s own growth estimate</span>
      <span xml:id="t88" from="#a5" to="#a6" type="claim_relations" ana="#claim_relations[1]" resp="#tagger" cert="1.0">extends → the Big Data literature on astronomy, computational social science and video platforms</span>
      <span xml:id="t89" from="#a15" to="#a17" type="concept_edges" ana="#concept_edges[0]" resp="#tagger">acquisition —part-of→ life cycle<note>strength of the relation: 1</note><term>acquisition</term><term>life cycle</term></span>
      <span xml:id="t90" from="#a1" to="#a4" type="concept_edges" ana="#concept_edges[1]" resp="#tagger">genomics —is-a→ Big Data<note>strength of the relation: 1</note><term>genomics</term><term>Big Data</term></span>
      <span xml:id="t91" from="#a15" to="#a17" type="concept_edges" ana="#concept_edges[4]" resp="#tagger">Big Data —operationalised-as→ life cycle<note>strength of the relation: 1
Audit 2026-09-28: DOUBTFUL - read against its span and kept, but the life cycle is the frame for comparing the domains; it is not an operationalisation of Big Data.</note><term>Big Data</term><term>life cycle</term></span>
      <span xml:id="t92" from="#a15" to="#a16" type="concept_edges" ana="#concept_edges[7]" resp="#tagger" cert="0.95">storage —part-of→ life cycle<note>the relation itself is separately evidenced · strength of the relation: 1 · note: Storage is explicitly one of four components comprising the dataset lifecycle.</note><term>storage</term><term>life cycle</term></span>
      <span xml:id="t93" from="#a15" to="#a16" type="concept_edges" ana="#concept_edges[8]" resp="#tagger" cert="0.95">distribution —part-of→ life cycle<note>the relation itself is separately evidenced · strength of the relation: 1 · note: Distribution is explicitly one of four components comprising the dataset lifecycle.</note><term>distribution</term><term>life cycle</term></span>
      <span xml:id="t94" from="#a15" to="#a16" type="concept_edges" ana="#concept_edges[9]" resp="#tagger" cert="0.95">analysis —part-of→ life cycle<note>the relation itself is separately evidenced · strength of the relation: 1 · note: Analysis is explicitly one of four components comprising the dataset lifecycle.</note><term>analysis</term><term>life cycle</term></span>
      <span xml:id="t95" from="#a80" to="#a81" type="concept_edges" ana="#concept_edges[10]" resp="#tagger" cert="0.95">effective data compression —causes→ storage requirements<note>direction on the measure: reduces · the relation itself is separately evidenced · strength of the relation: 1 · note: The paper states storage needs can be diminished with effective compression.
Audit 2026-09-28: DOUBTFUL - read against its full span and kept, but the span says these needs CAN be diminished with effective compression; hedged.</note><term>effective data compression</term><term>storage requirements</term></span>
      <span xml:id="t96" from="#a92" to="#a93" type="concept_edges" ana="#concept_edges[11]" resp="#tagger" cert="0.95">cloud computing —causes→ bandwidth for distribution of genomic data<note>direction on the measure: reduces · the relation itself is separately evidenced · strength of the relation: 1 · note: Cloud computing is stated to decrease distribution bandwidth.</note><term>cloud computing</term><term>bandwidth for distribution of genomic data</term></span>
      <span xml:id="t97" from="#a92" to="#a93" type="concept_edges" ana="#concept_edges[12]" resp="#tagger" cert="0.95">remote machines that already have data —causes→ computing resources necessary for distribution<note>direction on the measure: reduces · the relation itself is separately evidenced · strength of the relation: 1 · note: Running applications where data reside is stated to reduce distribution resources.</note><term>remote machines that already have data</term><term>computing resources necessary for distribution</term></span>
      <span xml:id="t98" from="#a100" to="#a101" type="concept_edges" ana="#concept_edges[13]" resp="#tagger" cert="0.9">CPU capabilities —contrasted-with→ input/output (I/O) hardware<note>the relation itself is separately evidenced · strength of the relation: 0.8 · note: The paper hedges that the larger future bottleneck may be I/O rather than CPU capability.
Audit 2026-09-28: DOUBTFUL - read against its full span and kept, but the span says the bigger bottleneck MAY not be in CPU but in I/O hardware; hedged.</note><term>CPU capabilities</term><term>input/output (I/O) hardware</term></span>
      <span xml:id="t99" from="#a43" to="#a44" type="content_tags" ana="#content_tags.quantities[0]" resp="#tagger">7 — doubling time of sequence data produced</span>
      <span xml:id="t100" from="#a46" to="#a47" type="content_tags" ana="#content_tags.quantities[1]" resp="#tagger">2,500 — high-throughput sequencers worldwide</span>
      <span xml:id="t101" from="#a46" to="#a48" type="content_tags" ana="#content_tags.quantities[2]" resp="#tagger">1,000 — global spread of sequencing centers</span>
      <span xml:id="t102" from="#a59" to="#a60" type="content_tags" ana="#content_tags.quantities[3]" resp="#tagger">3.6 — raw sequence data held in the SRA archive</span>
      <span xml:id="t103" from="#a27" to="#a28" type="content_tags" ana="#content_tags.quantities[4]" resp="#tagger">7.5 — ASKAP telescope image-data acquisition rate</span>
      <span xml:id="t104" from="#a33" to="#a34" type="content_tags" ana="#content_tags.quantities[5]" resp="#tagger">500 — current Twitter data generation</span>
      <span xml:id="t105" from="#a42" to="#a45" type="content_tags" ana="#content_tags.quantities[6]" resp="#tagger" cert="1.0">doubling every seven months — observed growth rate of sequence data production, the basis of the central projection</span>
      <span xml:id="t106" from="#a69" to="#a70" type="content_tags" ana="#content_tags.quantities[7]" resp="#tagger" cert="1.0">one zettabase per year by 2025 — projected genomic acquisition under the seven-month doubling</span>
      <span xml:id="t107" from="#a26" to="#a29" type="content_tags" ana="#content_tags.quantities[8]" resp="#tagger" cert="1.0">~25 zettabytes per year by 2025 — projected astronomy acquisition, from ASKAP scaling 7.5 to 750 terabytes/second</span>
      <span xml:id="t108" from="#a30" to="#a31" type="content_tags" ana="#content_tags.quantities[9]" resp="#tagger" cert="1.0">1–2 exabytes of video per year by 2025 — projected YouTube acquisition, from 300 hours uploaded per minute today</span>
      <span xml:id="t109" from="#a32" to="#a35" type="content_tags" ana="#content_tags.quantities[10]" resp="#tagger" cert="1.0">500 million tweets/day at ~3 kilobytes each — Twitter&#x27;s acquisition baseline, the smallest of the four by orders of magnitude</span>
      <span xml:id="t110" from="#a61" to="#a66" type="content_tags" ana="#content_tags.quantities[11]" resp="#tagger" cert="1.0">3.6 petabases archived; ~35 petabases/year capacity — what is in the SRA against what the world&#x27;s instruments can produce - the gap the paper flags</span>
      <span xml:id="t111" from="#a8" to="#a9" type="content_tags" ana="#content_tags.findings[0]" resp="#tagger">genomics is on par with or the most demanding of the Big Data domains</span>
      <span xml:id="t112" from="#a37" to="#a38" type="content_tags" ana="#content_tags.findings[1]" resp="#tagger">data acquisition is expected to grow by up to two orders of magnitude<note>about this quote: QUOTE RECOVERED FROM THE PAPER&#x27;S OWN CHARACTERS. The recorded quote was LETTERS-ONLY IDENTICAL to this stretch of the staged text but not an exact substring of it - spaces, hyphens, ligature glyphs or mathematical operators differed, so it could never anchor. This is the file&#x27;s own text between the same two letters: not produced by a rule about the damage, copied out of the file. Round-trip checked (the recovered span is letters-only equal to the original) and length-checked. The text as originally recorded is kept in evidence as extracted.</note></span>
      <span xml:id="t113" from="#a73" to="#a74" type="content_tags" ana="#content_tags.findings[2]" resp="#tagger">human genomes may grow four to five orders of magnitude by 2025</span>
      <span xml:id="t114" from="#a71" to="#a72" type="content_tags" ana="#content_tags.findings[3]" resp="#tagger">EVIDENCE CORRECTED (RE-GROUNDED - THE POINTER WAS WRONG, NOT THE CLAIM) · even conservative doubling (12-18 months) still yields exabase-scale genomics<note>EVIDENCE CORRECTED: RE-GROUNDED - THE POINTER WAS WRONG, NOT THE CLAIM. The old evidence was verbatim, anchored and correctly cut, and it contained NONE of this claim&#x27;s numbers (12, 18). The paper states the claim in one sentence elsewhere and the tagger did not use it. the project, 2026-08-23: &#x27;WE HAVE SPENT THE DAY VERIFYING THAT QUOTES ARE REAL AND NONE OF IT ASKS WHETHER THEY ARE RELEVANT.&#x27; Confirmed by reading the claim, the old span and the candidate together; the candidate carries every number AND the claim&#x27;s own content words.</note></span>
      <span xml:id="t115" from="#a7" to="#a10" type="content_tags" ana="#content_tags.findings[4]" resp="#tagger" cert="1.0">Genomics is a “four-headed beast”: on par with or the most demanding of the domains analysed in data acquisition, storage, distribution and analysis.</span>
      <span xml:id="t116" from="#a42" to="#a45" type="content_tags" ana="#content_tags.findings[5]" resp="#tagger" cert="1.0">Sequence data has been doubling roughly every seven months.</span>
      <span xml:id="t117" from="#a19" to="#a21" type="content_tags" ana="#content_tags.findings[6]" resp="#tagger" cert="1.0">The four Big Data domains differ sharply in how data are acquired.</span>
      <span xml:id="t118" from="#a36" to="#a39" type="content_tags" ana="#content_tags.findings[7]" resp="#tagger" cert="1.0">Across all domains, acquisition volume is expected to rise by up to two orders of magnitude in a decade.</span>
      <span xml:id="t119" from="#a64" to="#a65" type="content_tags" ana="#content_tags.variables[0]" resp="#tagger">worldwide sequencing capacity<term>worldwide sequencing capacity</term></span>
      <span xml:id="t120" from="#a50" to="#a51" type="content_tags" ana="#content_tags.variables[2]" resp="#tagger">conversion factor<term>conversion factor</term></span>
      <span xml:id="t121" from="#a5" to="#a6" type="content_tags" ana="#content_tags.variables[4]" resp="#tagger" cert="1.0">domain<term>domain</term></span>
      <span xml:id="t122" from="#a57" to="#a58" type="content_tags" ana="#content_tags.definitions[0]" resp="#tagger">Sequence Read Archive (SRA)<term>Sequence Read Archive (SRA)</term></span>
      <span xml:id="t123" from="#a53" to="#a54" type="content_tags" ana="#content_tags.definitions[2]" resp="#tagger">The Cancer Genome Atlas (TCGA)<term>The Cancer Genome Atlas (TCGA)</term></span>
      <span xml:id="t124" from="#a55" to="#a56" type="content_tags" ana="#content_tags.definitions[3]" resp="#tagger">Exome Aggregation Consortium (ExAC)<term>Exome Aggregation Consortium (ExAC)</term></span>
      <span xml:id="t125" from="#a15" to="#a17" type="content_tags" ana="#content_tags.definitions[4]" resp="#tagger" cert="1.0">life cycle<term>life cycle</term></span>
      <span xml:id="t126" from="#a1" to="#a4" type="content_tags" ana="#content_tags.definitions[5]" resp="#tagger" cert="1.0">genomics<term>genomics</term></span>
      <span xml:id="t127" from="#a49" to="#a52" type="content_tags" ana="#content_tags.definitions[6]" resp="#tagger" cert="1.0">conversion factor<term>conversion factor</term></span>
      <span xml:id="t128" from="#a42" to="#a45" type="content_tags" ana="#content_tags.statistics[0]" resp="#tagger" cert="1.0">exponential-growth<term>exponential-growth</term></span>
      <span xml:id="t129" from="#a30" to="#a31" type="content_tags" ana="#content_tags.statistics[1]" resp="#tagger" cert="1.0">extrapolation<term>extrapolation</term></span>
      <span xml:id="t130" from="#a36" to="#a39" type="content_tags" ana="#content_tags.statistics[2]" resp="#tagger" cert="1.0">order-of-magnitude<term>order-of-magnitude</term></span>
    </spanGrp>
  </standOff>
  <text>
    <body>
        <p><anchor xml:id="a0"/> Abstract</p>
        <p><anchor xml:id="a1"/>Genomics is a Big Data science and is going to get much bigger, very soon, but <anchor xml:id="a2"/>it is not known whether the needs of genomics will exceed other Big Data domains<anchor xml:id="a3"/>.<anchor xml:id="a4"/> <anchor xml:id="a5"/>Projecting to the year 2025, we compared genomics with three other major generators of Big Data: astronomy, YouTube, and Twitter.<anchor xml:id="a6"/> <anchor xml:id="a7"/>Our estimates show that genomics is a “four-headed beast”—<anchor xml:id="a8"/>it is either on par with or the most demanding of the domains analyzed here in terms of data acquisition, storage, distribution, and analysis<anchor xml:id="a9"/>.<anchor xml:id="a10"/> We discuss aspects of new technologies that will need to be developed to rise up and meet the computational challenges that genomics poses for the near future. Now is the time for concerted, community-wide planning for the “genomical” challenges of the next decade.</p>
        <p>This perspective considers the growth of genomics over the next ten years and assesses the computational needs that we will face relative to other &quot;Big Data&quot; activities such as astronomy, YouTube, and Twitter.</p>
        <p>We compared genomics with three other major generators of Big Data: astronomy, YouTube, and Twitter. Astronomy has faced the challenges of Big Data for over 20 years and continues with ever-more ambitious studies of the universe. YouTube burst on the scene in 2005 and has sparked extraordinary worldwide interest in creating and sharing huge numbers of videos. Twitter, created in 2006, has become the poster child of the burgeoning movement in computational social science [ 6 ], with unprecedented opportunities for new insights by mining the enormous and ever-growing amount of textual data [ 7 ]. <anchor xml:id="a11"/>Particle physics also produces massive quantities of raw data, although the footprint is surprisingly limited since the vast majority of data are discarded soon after acquisition using the processing power that is coupled to the sensors [ 8 ].<anchor xml:id="a12"/> <anchor xml:id="a13"/>Consequently, we do not include the domain in full detail here, although that model of rapid filtering and analysis will surely play an increasingly important role in genomics as the field matures.<anchor xml:id="a14"/></p>
        <p><anchor xml:id="a15"/>To compare these four disparate domains, we considered the four components that comprise the “life cycle” of a dataset: acquisition, storage, distribution, and analysis<anchor xml:id="a16"/> ( Table 1 ).<anchor xml:id="a17"/></p>
        <p>Table 1. Four domains of Big Data in 2025.</p>
        <p>In each of the four domains, the projected annual storage and computing needs are presented across the data lifecycle.</p>
        <p>Data Phase</p>
        <p>Astronomy</p>
        <p>Twitter</p>
        <p>YouTube</p>
        <p>Genomics</p>
        <p>Acquisition</p>
        <p>25 zetta-bytes/year   0.5–15 billion tweets/year   500–900 million hours/year   1 zetta-bases/year</p>
        <p>Storage</p>
        <p>1 EB/year   1–17 PB/year   1–2 EB/year   2–40 EB/year</p>
        <p>Analysis</p>
        <p>In situ data reduction   Topic and sentiment mining   Limited requirements   Heterogeneous data and analysis</p>
        <p>Real-time processing   Metadata analysis</p>
        <p>Variant calling, ~2 trillion central processing unit (CPU) hours</p>
        <p>Massive volumes</p>
        <p>All-pairs genome alignments, ~10,000 trillion CPU hours</p>
        <p>Distribution</p>
        <p>Dedicated lines from antennae to server (600 TB/s)   Small units of distribution   Major component of modern user’s bandwidth (10 MB/s)   Many small (10 MB/s) and fewer massive (10 TB/s) data movement</p>
        <p>Open in a new tab</p>
        <p><anchor xml:id="a18"/>Data Acquisition</p>
        <p><anchor xml:id="a19"/>The four Big Data domains differ sharply in how data are acquired<anchor xml:id="a20"/>.<anchor xml:id="a21"/> <anchor xml:id="a22"/>Most astronomy data are acquired from a few highly centralized facilities [ 9 ].<anchor xml:id="a23"/> <anchor xml:id="a24"/>By contrast, YouTube and Twitter acquire data in a highly distributed manner, but under a few standardized protocols.<anchor xml:id="a25"/> Astronomy, YouTube, and Twitter are expected to show continued dramatic growth in the volume of data to be acquired. For example, <anchor xml:id="a26"/>the Australian Square Kilometre Array Pathfinder (ASKAP) project <anchor xml:id="a27"/>currently acquires 7.5 terabytes/second of sample image data<anchor xml:id="a28"/>, a rate projected to increase 100-fold to 750 terabytes/second (~25 zettabytes per year) by 2025<anchor xml:id="a29"/> [ 9 , 10 ]. <anchor xml:id="a30"/>YouTube currently has 300 hours of video being uploaded every minute, and this could grow to 1,000–1,700 hours per minute (1–2 exabytes of video data per year) by 2025 if we extrapolate from current trends ( S1 Note ).<anchor xml:id="a31"/> <anchor xml:id="a32"/>Today, <anchor xml:id="a33"/>Twitter generates 500 million tweets/day<anchor xml:id="a34"/>, each about 3 kilobytes including metadata ( S2 Note ).<anchor xml:id="a35"/> While this figure is beginning to plateau, a projected logarithmic growth rate would suggest a 2.4-fold growth by 2025, to 1.2 billion tweets per day, 1.36 petabytes/year. <anchor xml:id="a36"/>In short, <anchor xml:id="a37"/>data acquisition in these domains is expected to grow by up to two orders of magnitude<anchor xml:id="a38"/> in the next decade.<anchor xml:id="a39"/></p>
        <p><anchor xml:id="a40"/>For genomics, data acquisition is highly distributed and involves heterogeneous formats.<anchor xml:id="a41"/> <anchor xml:id="a42"/>The rate of growth over the last decade has also been truly astonishing, with the total amount of sequence data produced <anchor xml:id="a43"/>doubling approximately every seven months<anchor xml:id="a44"/> ( Fig 1 ).<anchor xml:id="a45"/> <anchor xml:id="a46"/>The OmicsMaps catalog of all known sequencing instruments in the world [ 11 ] reports that currently there are more than 2,500 high-throughput instruments<anchor xml:id="a47"/>, manufactured by several different companies, located in nearly 1,000 sequencing centers in 55 countries<anchor xml:id="a48"/> in universities, hospitals, and other research laboratories. These centers range in size from small laboratories with a few instruments generating a few terabases per year to large dedicated facilities producing several petabases a year. <anchor xml:id="a49"/>(<anchor xml:id="a50"/>An approximate conversion factor to use in interpreting these numbers is 4<anchor xml:id="a51"/> bases = 1 byte, though we will revisit this below.)<anchor xml:id="a52"/></p>
        <p>Fig 1. Growth of DNA sequencing.</p>
        <p>Open in a new tab</p>
        <p>The plot shows the growth of DNA sequencing both in the total number of human genomes sequenced (left axis) as well as the worldwide annual sequencing capacity (right axis: Tera-basepairs (Tbp), Peta-basepairs (Pbp), Exa-basepairs (Ebp), Zetta-basepairs (Zbps)). The values through 2015 are based on the historical publication record, with selected milestones in sequencing (first Sanger through first PacBio human genome published) as well as three exemplar projects using large-scale sequencing: the 1000 Genomes Project, aggregating hundreds of human genomes by 2012 [ 3 ]; <anchor xml:id="a53"/>The Cancer Genome Atlas (TCGA), aggregating over several thousand tumor/normal genome pairs<anchor xml:id="a54"/> [ 4 ]; and <anchor xml:id="a55"/>the Exome Aggregation Consortium (ExAC),<anchor xml:id="a56"/> aggregating over 60,000 human exomes [ 5 ]. Many of the genomes sequenced to date have been whole exome rather than whole genome, but we expect the ratio to be increasingly favored towards whole genome in the future. The values beyond 2015 represent our projection under three possible growth curves as described in the main text.</p>
        <p>The raw sequencing reads used in most published studies are archived at either the <anchor xml:id="a57"/>Sequence Read Archive (SRA) maintained by the United States National Institutes of Health<anchor xml:id="a58"/> National Center for Biotechnology Information (NIH/NCBI) or one of the international counterparts. <anchor xml:id="a59"/>The SRA currently contains more than 3.6 petabases of raw sequence data<anchor xml:id="a60"/> ( S1 Fig ), which reflects the ~32,000 microbial genomes, ~5,000 plant and animal genomes, and ~250,000 individual human genomes that have been sequenced or are in progress thus far [ 12 ]. <anchor xml:id="a61"/>However, the 3.6 petabases represent a small fraction of the total produced; most of it is not yet in these archives.<anchor xml:id="a62"/> <anchor xml:id="a63"/>Based on manufacturer specifications of the instruments, we estimate the current <anchor xml:id="a64"/>worldwide sequencing capacity to exceed 35 petabases per year<anchor xml:id="a65"/>, including the sixteen Illumina X-Ten systems that have been sold so far [ 13 ], each with a capacity of ~2 petabases per year [ 14 ].<anchor xml:id="a66"/></p>
        <p><anchor xml:id="a67"/>Over the next ten years, we expect sequencing capacities will continue to grow very rapidly, although the project growth becomes more unpredictable the further out we consider.<anchor xml:id="a68"/> <anchor xml:id="a69"/>If the growth continues at the current rate by doubling every seven months, then we should reach more than one exabase of sequence per year in the next five years and approach one zettabase of sequence per year by 2025 ( Fig 1 , Table 1 ).<anchor xml:id="a70"/> <anchor xml:id="a71"/>Interestingly, even at the more conservative estimates of doubling every 12 months (Illumina’s current own estimate [ 12 ]) or every 18 months (equivalent to Moore’s law), we should reach exabase-scale genomics well within the next decade.<anchor xml:id="a72"/> We anticipate this sequencing will encompass genome sequences for most of the approximately 1.2 million described species of plants and animals [ 15 ]. With these genomes, plus those of thousands of individuals of “high value” species for energy, environmental, and agricultural reasons, we estimate that there will be at least 2.5 million plant and animal genome sequences by 2025. For example, the genomics powerhouse BGI, in conjunction with the International Rice Research Institute and the Chinese Academy of Agricultural Sciences, has already sequenced 3,000 varieties of rice [ 16 ] and announced a massive project of their own to sequence one million plant and animal genomes [ 17 ]. The Smithsonian Institute also has similar plans to “capture and catalog all the DNA from the world’s flora and fauna.” There also will be genomes for several millions of microbes, with explosive growth projected for both medical and environmental microbe metagenomic sequencing [ 18 , 19 ].</p>
        <p>These estimates, however, are dwarfed by the very reasonable possibility that a significant fraction of the world’s human population will have their genomes sequenced. The leading driver of this trend is the promise of genomic medicine to revolutionize the diagnosis and treatment of disease, with some countries contemplating sequencing large portions of their populations: both England [ 20 ] and Saudi Arabia [ 21 ] have announced plans to sequence 100,000 of their citizens, one-third of Iceland’s 320,000 citizens have donated blood for genetic testing [ 22 ], and researchers in both the US [ 23 ] and China [ 17 ] both aim to sequence 1 million genomes in the next few years. With the world’s population projected to top 8 billion by 2025, it is possible that as many as 25% of the population in developed nations and half of that in less-developed nations will have their genomes sequenced (comparable to the current worldwide distribution of Internet users [ 24 ]).</p>
        <p><anchor xml:id="a73"/>We therefore estimate between 100 million and as many as 2 billion human genomes could be sequenced by 2025, representing four to five orders of magnitude growth in ten years and far exceeding the growth for the three other Big Data domains<anchor xml:id="a74"/>.<anchor xml:id="a75"/> Indeed, this number could grow even larger, especially since new single-cell genome sequencing technologies are starting to reveal previously unimagined levels of variation, especially in cancers, necessitating sequencing the genomes of thousands of separate cells in a single tumor [ 10 ].</p>
        <p>Moreover, the technology used to sequence DNA is deployed creatively for other applications (e.g., transcriptome, epigenome, proteome, metabolome, and microbiome sequencing) necessitating generating new sequencing data multiple times per person to monitor molecular activity [ 25 ]. These applications require precise quantitative counts of sequencing reads to capture diversity of expression or diversity of abundances, thus requiring millions of reads to accurately estimate underlying distributions as they change over time. For medicine, just having the genome will not be sufficient: for each individual, it will need to be coupled with other relevant ‘omics data sets, some collected periodically and from different tissues, to compare healthy and diseased states [ 26 ]. Computational challenges will increase because of dramatic increases in the total volume of genomic data per person, as will the complexities of integrating these diverse data sources to improve health and cure diseases. Genomics thus appears to pose the greatest challenges for data acquisition of the four Big Data domains.</p>
        <p>Data Storage</p>
        <p>Data storage requirements for all four domains are projected to be enormous. Today, the largest astronomy data center devotes ~100 petabytes to storage, and the completion of the Square Kilometre Array (SKA) project is expected to lead to a storage demand of 1 exabyte per year. YouTube currently requires from 100 petabytes to 1 exabyte for storage and may be projected to require between 1 and 2 exabytes additional storage per year by 2025. Twitter’s storage needs today are estimated at 0.5 petabytes per year, which may increase to 1.5 petabytes in the next ten years. <anchor xml:id="a76"/>(Our estimates here ignore the “replication factor” that multiplies storage needs by ~4, for redundancy.)<anchor xml:id="a77"/> For genomics, we have determined more than 100 petabytes of storage are currently used by only 20 of the largest institutions ( S1 Table ).</p>
        <p><anchor xml:id="a78"/>Projections of storage requirements for sequence data depend on the accuracy and application of the sequencing.<anchor xml:id="a79"/> For every 3 billion bases of human genome sequence, 30-fold more data (~100 gigabases) must be collected because of errors in sequencing, base calling, and genome alignment. This means that as much as 2–40 exabytes of storage capacity will be needed by 2025 just for the human genomes ( S3 Note ). <anchor xml:id="a80"/>These needs can be diminished with effective data compression [ 27 ], but decompression times and fidelity are a major concern in compressive genomics<anchor xml:id="a81"/> [ 28 ].</p>
        <p><anchor xml:id="a82"/>Are the emerging “third-generation” single-molecule sequencing technologies with much longer reads, such as those from Pacific Biosciences and Oxford Nanopore, a computational panacea? Though error rates currently are higher and throughput lower than short-read technologies, as they mature, these technologies are starting to be used to sequence and assemble nearly entire chromosomes [ 29 ]. This will minimize the need to oversample as much, and eventually, the raw sequence data may not need to be stored at all<anchor xml:id="a83"/>. However, eliminating the need to store raw sequence data and only retaining complete genomes will have relatively little impact overall—perhaps one or two orders of magnitude less data storage. <anchor xml:id="a84"/>More significant reductions in storage demand will come when improvements in sequencing accuracy and database comprehensiveness reach the point at which genome sequences themselves do not need to be stored, just the list of variants relative to a reference collection (“delta encoding”)<anchor xml:id="a85"/> [ 30 ]. This works well for cataloging the simplest variants in a human genome, but it may not be as useful for complex samples, such as cancer genomes, that have many novel rearrangements and mutations. While certainly helpful, we thus do not expect long-read sequencing technology or delta encoding to solve the storage challenges for genome sequencing in 2025.</p>
        <p><anchor xml:id="a86"/>In contrast, we do see great opportunities for data reduction and real-time analysis of other ‘omics analysis. For example, once sequencing becomes fast enough and the methods mature enough to correctly infer transcript expression levels in real time, we anticipate that raw RNA-seq reads will no longer be stored, except for specific research purposes. Already several such “streaming” algorithms have been published for this purpose, performing as well as or superior to their nonstreaming counterparts<anchor xml:id="a87"/> [ 31 ]. <anchor xml:id="a88"/>For RNA-seq and other ‘omics applications, genomics will benefit greatly from the lessons learned in particle physics, in which in most cases raw data are discarded almost as fast as they are generated in favor of higher level and greatly compressed summaries.<anchor xml:id="a89"/></p>
        <p>Altogether, we anticipate the development of huge genomics archives used for storing millions of genomes along with the associated ‘omics measurements over time. Ideally, these archives will also collect or be linked to the patient phenotypic data, especially disease outcomes and treatments provided to support retrospective analysis as new relationships are discovered. <anchor xml:id="a90"/>To make it practical to search and query through such vast collections, the data will be stored in hierarchical systems that make data and their statistical summaries available at different levels of compression and latency<anchor xml:id="a91"/>, as used in astronomy [ 32 ] and text analysis [ 33 ]. Thus, although total genomic data could far exceed the demands for the others, with the right new innovations the net requirements could be similar to the domains of astronomy and YouTube.</p>
        <p>Data Distribution</p>
        <p>Astronomy, YouTube, Twitter, and genomics also differ greatly in data distribution patterns. The major bandwidth requirement of the SKA project is to get data from its 3,000 antennae to a central server, requiring as much as 600 terabytes/second [ 34 ]. The bandwidth usage of YouTube is relatively small for a single download and well supported by the average consumer’s 10 Mbps connection, but aggregate needs worldwide are enormous, with estimates up to 240 petabytes/day ( S4 Note ) [ 35 ]. The distribution patterns of genomics data are much more heterogeneous, involving elements of both situations [ 36 ].</p>
        <p>Genomic data are distributed in units spanning a wide range of sizes, from comparisons of a few bases or gene sequences to large multiterabyte bulk downloads from central repositories. <anchor xml:id="a92"/>For large-scale analysis, cloud computing is particularly suited to decreasing the bandwidth for distribution of genomic data [ 37 ] so that applications can run on remote machines that already have data [ 38 ]. Only small segments of code are uploaded and highly processed outputs are downloaded, thus significantly reducing the computing resources necessary for distribution<anchor xml:id="a93"/>.</p>
        <p>But in addition to tailoring genomics applications for the cloud, <anchor xml:id="a94"/>new methods of data reliability and security are required to ensure privacy, much more so than for the other three domains. A serious breach of medically sensitive genomic data would have permanent consequences and could seriously hinder the development of genomic medicine. Homomorphic encryption systems, in which encrypted data can be analyzed and manipulated for certain controlled queries without disclosing the raw data, are currently too computationally expensive for widespread use, but these and related cryptographic techniques are promising areas of research<anchor xml:id="a95"/> [ 39 ].</p>
        <p>Data Analysis</p>
        <p>Astronomy, YouTube, Twitter, and genomics differ most in computational requirements for data analysis. Astronomy data require extensive specialized analysis, but the bulk of this requirement is for in situ processing and reduction of data by computers located near the telescopes [ 40 ]. This initial analysis is daunting because of its real-time nature and huge data volumes but can often be effectively performed in parallel on thousands of cores. YouTube videos are primarily meant to be viewed, along with some automated analysis for advertisements or copyright infringements. Twitter data are the subject of intense research in the social sciences [ 41 ], especially for topic and sentiment mining, which is performed chiefly on textual “tweets” in the context of associated metadata (e.g., user demographics and temporal information).</p>
        <p>Analysis of genomic data involves a more diverse range of approaches because of the variety of steps involved in reading a genome sequence and deriving useful information from it. <anchor xml:id="a96"/>For population and medical genomics, identifying the genomic variants in each individual genome is currently one of the most computationally complex phases<anchor xml:id="a97"/>. Variant calling on 2 billion genomes per year, with 100,000 CPUs in parallel, would require methods that process 2 genomes per CPU-hour, three-to-four orders of magnitude faster than current capabilities [ 42 ]. <anchor xml:id="a98"/>Whole genome alignment is another important form of genomic data analysis, used for a variety of goals, from phylogeny reconstruction to genome annotation via comparative methodologies. Just a single whole genome alignment between human and mouse consumes ~100 CPU hours [ 43 ]. Aligning all pairs of the ~2.5 million species expected to be available by 2025 amounts to 50–100 trillion such whole genome alignments, which would need to be six orders of magnitude faster than possible today<anchor xml:id="a99"/>.</p>
        <p><anchor xml:id="a100"/>Improvements to CPU capabilities, as anticipated by Moore’s Law, should help close the gap, but trends in computing power are often geared towards floating point operations and do not necessarily provide improvements in genome analysis, in which string operations and memory management often pose the most significant challenges. Moreover, the bigger bottleneck of Big Data analysis in the future may not be in CPU capabilities but in the input/output (I/O) hardware that shuttles data between storage and processors [ 44 ], a problem requiring research into new parallel I/O hardware and algorithms that can effectively utilize them<anchor xml:id="a101"/>.</p>
        <p>The Long Road Ahead</p>
        <p>Genomics clearly poses some of the most severe computational challenges facing us in the next decade. Genomics is a “four-headed beast”; considering the computational demands across the lifecycle of a dataset—acquisition, storage, distribution, and analysis—genomics is either on par with or the most demanding of the Big Data domains. <anchor xml:id="a102"/>New integrative approaches need to be developed that take into account the challenges in all four aspects: it is unlikely that a single advance or technology will solve the genomics data problem<anchor xml:id="a103"/>. Several key technologies that are most critically needed to support future solutions are discussed in Box 1 .</p>
        <p>In human health, the major needs are driven by the realization that for precision medicine and similar efforts to be most effective, genomes and related ‘omics data need to be shared and compared in huge numbers. <anchor xml:id="a104"/>If we do not commit as a scientific community to sharing now, we run the risk of establishing thousands of isolated, private data collections, each too underpowered to allow subtle signals to be extracted<anchor xml:id="a105"/>. More than anything else, <anchor xml:id="a106"/>connecting these resources requires trust among institutions, scientists, and the public to ensure the collections will be used for medical purposes and not to discriminate or penalize individuals because of their genetic makeup<anchor xml:id="a107"/>.</p>
        <p>Finally, the exascale data and computing centers that are emerging today to meet Big Data challenges in several domains (YouTube [ 50 ], Google [ 51 ], Facebook [ 51 ], and the National Security Agency [ 52 ]), are the result of far-sighted planning and commitment by the respective organizations. Now is the time for concerted, community-wide planning for the “genomical” challenges of the next decade.</p>
        <p>Box 1. Key Technological Needs for Big Data Genomics</p>
        <p>(1) Acquisition</p>
        <p>The most important need to sustain the explosive growth in genomic data acquisition is continued advances in sequencing technologies to reduce costs, improve throughput, and achieve very high accuracy. The current costs of ~US$1,000 per human genome begin to make it practical to sequence human genomes in large numbers, especially for critical medical treatments, but to scale to populations of hundreds of millions to billions of genomes, costs must be reduced by at least another one to two orders of magnitude or more. For many medical applications, the time for sequencing must also be reduced so that it can be completed in near real time, especially to rapidly diagnosis acute infections and conditions. Finally, to make a genome sequence most useful, it must be paired with automated methods to collect metadata and phenotype data, all according to appropriate standards so that data collected in one environment can be compared to those collected in another.</p>
        <p>(2) Storage</p>
        <p>The community needs to start designing and constructing data centers with fast, tiered storage systems to query and aggregate over large collections of genomes and ‘omics data. There are new technologies on the horizon that will help support these needs, including 3-D memory, integrated computing technologies that overcome the I/O bottleneck, and networks that are two-to-five orders of magnitude faster because of optical switching [ 45 , 46 ]. Similarly, efficient compression and indexing systems are critical to make the best use out of each available byte while making the data highly accessible. We also expect algorithmic developments that can represent large collections of personal genomes as a compact graph, making it more efficient and robust to compare one genome to many others. Beyond these approaches, we see the rise of streaming approaches to make on-the-fly comparisons that will allow us to rapidly discard data, especially for sequencing applications that use the sequence data as a means to infer abundances or other molecular activity.</p>
        <p>(3) Distribution</p>
        <p>The most practical, and perhaps only, solution for distributing genome sequences at a population scale is to use cloud-computing systems that minimize data movement and maximize code federation [ 47 ]. New developments from companies such as Google, Amazon, and Facebook that include applications built to fit the frameworks of distributed computing efficient data centers and distributed storage and cloud computing paradigms will be part of the solution. Already, large cloud-based genomic resources are being developed using these technologies, especially to support the needs of the largest sequencing centers or to support the needs of large communities (BGI-cloud, TCGA, the International Cancer Genome Consortium [ICGC], etc.). To make these online systems most useful, <anchor xml:id="a108"/>the community needs to develop application programming interfaces (APIs) for discovering and querying large datasets on remote systems<anchor xml:id="a109"/>. The Global Alliance for Genomics and Health [ 48 ] and others are beginning to develop such standards for human genomic data, and we expect other communities to follow. Finally, authentication, encryption, and other security safeguards must be developed to ensure that genomic data remain private.</p>
        <p>(4) Analysis</p>
        <p><anchor xml:id="a110"/>Our ultimate goal is to be able to interpret genomic sequences and answer how DNA mutations, expression changes, or other molecular measurements relate to disease, development, behavior, or evolution. Accomplishing this goal will clearly require integration of biological domain expertise, <anchor xml:id="a111"/>large-scale machine learning systems, and a computing infrastructure that can support flexible and dynamic queries<anchor xml:id="a112"/> to search for patterns over very large collections in very high dimensions<anchor xml:id="a113"/>. A number of “data science technologies,” including R, Mahout, and other machine learning systems powered by Hadoop and other highly scalable systems, are a start, but the current offerings are still difficult and expensive to use. The community would also benefit from libraries of highly optimized algorithms within a simple interface that can be combined and reused in many contexts as the problems emerge. Data science companies as well as open-source initiatives are already starting to develop such components, such as Amazon’s recent “Amazon Machine Learning” prediction system. But because genomics poses unique challenges in terms of data acquisition, distribution, storage, and especially analysis, waiting for innovations from outside our field is unlikely to be sufficient. We must face these challenges ourselves, <anchor xml:id="a114"/>starting with integrating data science into graduate, undergraduate, and high-school curricula to train the next generations of quantitative biologists, bioinformaticians, and computer scientists and engineers<anchor xml:id="a115"/> [ 49 ].</p>
        <p>Supporting Information</p>
        <p>S1 Fig. Growth of GenBank. The y -axis shows the total sequence in bp. (Blue = GenBank, red = whole genome shotgun [WGS] sequences.) Each line is double of the previous. The x -axis indicates time. Each line is 6 months after the previous. Source: http://www.ncbi.nlm.nih.gov/genbank/statistics .</p>
        <p>(TIF)</p>
        <p>Click here for additional data file. (1.9MB, tif)</p>
        <p>S1 Note. YouTube data estimates. (DOCX)</p>
        <p>Click here for additional data file. (65.6KB, docx)</p>
        <p>S2 Note. Twitter data estimates. (DOCX)</p>
        <p>Click here for additional data file. (84.9KB, docx)</p>
        <p>S3 Note. Human genomic data storage estimates for 2025. (DOCX)</p>
        <p>Click here for additional data file. (39.9KB, docx)</p>
        <p>S4 Note. YouTube distribution statistics (current). (DOCX)</p>
        <p>Click here for additional data file. (37.8KB, docx)</p>
        <p>S1 Table. Capacities of 20 major genomics institutions. The number of sequencers as listed from OmicsMaps.com and their storage capacities from the listed citation. These 20 institutions alone collectively have more than 100 PB of storage available.</p>
        <p>(DOCX)</p>
        <p>Click here for additional data file. (171.6KB, docx)</p>
        <p>Acknowledgments</p>
        <p>We thank V. Jongeneel, M. Baker, and the anonymous reviewers for comments that improved the manuscript and the Illinois CompGen Initiative for providing the collaborative structure that fostered the idea for this analysis. We would also like to thank all of the participants of the 2014 Keystone Symposium on “Big Data in Biology” (organized by Lincoln D. Stein, Doreen Ware, and MCS) for their inspiration for this analysis.</p>
        <p>Abbreviations</p>
        <p>API   application programming interface</p>
        <p>ASKAP   Australian Square Kilometre Array Pathfinder</p>
        <p>CPU   central processing unit</p>
        <p>ExAC   Exome Aggregation Consortium</p>
        <p>ICGC   International Cancer Genome Consortium</p>
        <p>I/O   input/output</p>
        <p>NIH/NCBI   National Institutes of Health National Center for Biotechnology Information</p>
        <p>SKA   Square Kilometre Array</p>
        <p>SRA   Sequence Read Archive</p>
        <p>TCGA   The Cancer Genome Atlas</p>
        <p>WGS   whole genome shotgun</p>
        <p>Funding Statement</p>
        <p>This research was supported, in part, by grant 1U54GM114838 awarded by NIGMS to SS through funds provided by the trans-NIH Big Data to Knowledge (BD2K) initiative and by National Institutes of Health award (R01-HG006677) to MCS. ZDS and RKI were supported by NSF grant MRI13-37732 (S.S. Lumetta, PI). The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript.<anchor xml:id="a116"/></p>
    </body>
  </text>
</TEI>
