Jump to content

User:Cglife.bmarcus/sandbox

From Wikipedia, the free encyclopedia

A cloud laboratory is a heavily automated, centralized research laboratory where scientists can run an entire experimental process from a computer in a remote location.[1][2] Cloud laboratories offer the execution of life science research experiments as a service, allowing researchers to retain full control over experimental design.[3][4][5] Users create experimental protocols through a high-level API and the experiment is executed in the cloud laboratory where users do not need to track its progression.[1][5]

Cloud labs reduce variability in experimental execution, as the code can be interrogated, analyzed, and executed repeatedly.Cite error: A <ref> tag is missing the closing </ref> (see the help page).[6] They also reduce costs by sharing capital costs across many users, by running experiments in parallel, and reducing instrument downtime.[6] Finally, they facilitate collaboration by make it easier to share protocols, data, and data processing methods through the cloud.[7]

Infrastructure

[edit]

Cloud labs offer common scientific techniques including genotyping, nucleic acid synthesis, protein extraction, liquid transfer, plate reading, Western blotting, high-performance liquid chromatography, upstream bioprocessing, sequencing, and others.Cite error: A <ref> tag is missing the closing </ref> (see the help page).[8] Users begin by signing up and logging in to the web-based software interface.[5] Researchers submit their protocols via a dedicated web application or through an API and when the order arrives at the laboratory, human operators set up the experiment and transfer plates from machine to machine. Data is automatically uploaded to the cloud lab via an API where users can access and analyze it. Users can review controls, machine settings, and reagents used.[9] Multiple experiments can be run in parallel, 24 hours a day.[10][3][11]

Cloud labs are defined by five unique features:[12][13][14]

  1. Users must be able to conduct experiments on-demand at any time from any location, all through a computer interface.
  2. The cloud laboratory must enable a user to digitally replicate the experience of standing in a traditional laboratory and manually operating instruments. It must allow users to specify all aspects of their experiments remotely without lead time, additional software, or outside experts
  3. Users must have on-demand access to all the instruments needed to perform their experiment, making a physical laboratory redundant and unnecessary.
  4. Users must be able to perform all aspects of sample preparation, storage, and handling from a remote setting.
  5. Users must be able to script and connect multiple experiments as well as process, analyze, visualize, and interpret data using a single standardized computer interface.

Using a Cloud Laboratory vs. High Throughput Experimentation

[edit]
See also: High-throughput screening

High-Throughput Experimentation involves increasing throughput by scaling up the number of experiments that can be run in parallel using a common sample form factor and technique.[15][16] But when space or materials are limited, minor factors must be assigned to progressively smaller fractions to increase the number of replicants.[17] Cloud labs, on the other hand, don't fundamentally scale up a single experiment but rather increase the number of types of experiments that can be run in parallel.[18] For example, with a cloud lab, a scientist could simultaneously attempt dozens of different purification methods that each uses completely unique equipment sets.[19]

HTE work cells can sometimes be accessed remotely to trigger a run on a library or digitally monitor a run. However, this remote monitoring or screen triggering does not impact the development that must take place in advance of a run.[15] Often with HTE, scientists must group samples into libraries that use the same or very similar form factor containers such that the work cell can more easily traffic and address each sample in an integrated manner.Cite error: A <ref> tag is missing the closing </ref> (see the help page). [20]

History

[edit]

Cloud laboratories were built on advancements made in laboratory automation in the 1990s. In the early 1990s, the modularity project of the Consortium of Automated Analytical Laboratory Systems worked to define standards by which biotechnology manufacturers could produce products that could be integrated into automated systems.[21] In 1996, the National Committee for Clinical Laboratory Standards (now the Clinical and Laboratory Standards Institute) proposed laboratory automation standards that aimed to enable consumers of laboratory technology to purchase hardware and software from different vendors and connect them to each other seamlessly.[22] The Committee launched five subcommittees in 1997 and released standardization protocols to guide product development through the early 2000s.[23][24]

These early developments in interoperability led to early examples of lab automation using cloud infrastructure, such as the Robot Scientist “Adam” in 2009. This robot encapsulated and connected all the laboratory equipment necessary to perform microbial batch experiments.[25]

In 2010, D.J. Kleinbaum and Brian Frezza founded antiviral developer Emerald Therapeutics. To simplify laboratory testing, the group wrote centralized management software for their collection of scientific instruments and a database to store all metadata and results.[26]

In 2012, Transcriptic founded a robotic cloud laboratory for on-demand scientific research, which performed select tasks including DNA cloning remotely.[27]

In 2014, Emerald Therapeutics spun out the Emerald Cloud Lab to fully replace the need for a traditional lab environment, enabling scientists from around the world to perform all necessary activities, from experimental design to data acquisition and analysis.[28]

Carnegie Mellon University's Mellon College of Science is building the world’s first academic cloud laboratory on their campus.[29] The 20,000 square foot laboratory will be completed in 2023 and offer access to CMU researchers and eventually to other schools and life-sciences startups in Pittsburgh.[30]

  1. ^ a b Jessop-Fabre, Mathew M; Sonnenschein, Nikolaus (Feb 11, 2019). "Improving Reproducibility in Synthetic Biology". Frontiers in Bioengineering and Biotechnology. 7. Frontiers Media SA. doi:10.3389/fbioe.2019.00018. ISSN 2296-4185.{{cite journal}}: CS1 maint: unflagged free DOI (link)
  2. ^ Groth, Paul; Cox, Jessica (Nov 8, 2017). "Indicators for the use of robotic labs in basic biomedical research: a literature analysis". PeerJ. 5. PeerJ: e3997. doi:10.7717/peerj.3997. ISSN 2167-8359.{{cite journal}}: CS1 maint: unflagged free DOI (link)
  3. ^ a b "Exploring the Cloud Laboratory: Advances in Biotech & Science-as-a-Service". Nordic APIs. May 17, 2016. Retrieved Dec 9, 2021.
  4. ^ Bates, Maxwell; Berliner, Aaron J.; Lachoff, Joe; Jaschke, Paul R.; Groban, Eli S. (Sep 2, 2016). "Wet Lab Accelerator: A Web-Based Application Democratizing Laboratory Automation for Synthetic Biology". ACS Synthetic Biology. 6 (1). American Chemical Society (ACS): 167–171. doi:10.1021/acssynbio.6b00108. ISSN 2161-5063.
  5. ^ a b c "Laboratories in the cloud". Bulletin of the Atomic Scientists. Retrieved Dec 9, 2021.
  6. ^ a b Wykstra, Stephanie (Jun 30, 2016). "Robotic Cloud Labs May Be One Way to Make Research More Reproducible". Slate Magazine. Retrieved Dec 9, 2021.
  7. ^ Cite error: The named reference Mok Newstack was invoked but never defined (see the help page).
  8. ^ "Culture riding virtual R&D wave, latest funding round enables development of cloud bioreactors". Biopharmaceutical Manufacturing, Upstream, Downstream processing news. Nov 12, 2021. Retrieved Dec 9, 2021.
  9. ^ Cite error: The named reference Nature 2014 was invoked but never defined (see the help page).
  10. ^ Mouratidis, Yiannis (Feb 27, 2019). "A Cloud Lab Dedicated To Cancer Drug Discovery". Forbes. Retrieved Dec 9, 2021.
  11. ^ "An operating system for the biology lab". Nature. Sep 25, 2019. Retrieved Dec 9, 2021.
  12. ^ "5 criteria of a true cloud laboratory". Drug Discovery & Development. February 25, 2022. Retrieved Mar 17, 2022.
  13. ^ "What are the criteria of a true cloud laboratory?". Drug Discovery & Development. March 16, 2022. Retrieved Mar 17, 2022.
  14. ^ "Accelerating Scientific Research Using the Cloud". PharmTech. May 4, 2022. Retrieved May 5, 2022.
  15. ^ a b Shevlin M (2019). "The Evolution of High-Throughput Experimentation in Pharmaceutical Development and Perspectives on the Future". Org Process Res Dev. 23 (6): 1213–1242. doi:10.1021/acs.oprd.9b00140.
  16. ^ Mennen S (2017). "Practical High-Throughput Experimentation for Chemists". ACS Med Chem Lett. 8 (6): 601–607. doi:10.1021/acsmedchemlett.7b00165. PMC 5467193. PMID 28626518.
  17. ^ Shevlin M (2017). "Practical High-Throughput Experimentation for Chemists". ACS Med Chem Lett. 8 (6): 601–607. doi:10.1021/acsmedchemlett.7b00165. PMC 5467193. PMID 28626518.
  18. ^ "Carnegie Mellon University and Emerald Cloud Lab to Build World's First University Cloud Lab". CMU.edu. Aug 30, 2021. Retrieved Mar 24, 2022.
  19. ^ Cite error: The named reference DDD2” was invoked but never defined (see the help page).
  20. ^ "Cloud lab solution empowers access of research tech from miles away". Outsourcing Pharma. Aug 26, 2021. Retrieved May 9, 2022.
  21. ^ Salit, Marc L.; Guenther, Franklin R.; Kramer, Gary W.; Griesmeyer, J. Michael (Mar 15, 1994). "Integrating Automated Systems With Modular Architecture". Analytical Chemistry. 66 (6). American Chemical Society (ACS): 361A–367A. doi:10.1021/ac00078a727. ISSN 0003-2700.
  22. ^ "A Report of the NCCLS Area Committee on Automation 4th Quarter of 1998". JALA: Journal of the Association for Laboratory Automation. 3 (6). SAGE Publications: 93–93. 1998. doi:10.1177/221106829800300618. ISSN 1535-5535.
  23. ^ AUTO5A.Laboratory Automation: Electromechanical Interfaces; Approved Standard (Report). Clinical and Laboratory Standards Institute. 2001.
  24. ^ Hawker, Charles D; Schlank, Marc R (Apr 1, 2000). "Development of Standards for Laboratory Automation". Clinical Chemistry. 46 (5). Oxford University Press (OUP): 746–750. doi:10.1093/clinchem/46.5.746. ISSN 0009-9147.
  25. ^ King, Ross D.; Rowland, Jem; Oliver, Stephen G.; Young, Michael; Aubrey, Wayne; Byrne, Emma; Liakata, Maria; Markham, Magdalena; Pir, Pinar; Soldatova, Larisa N.; Sparkes, Andrew; Whelan, Kenneth E.; Clare, Amanda (Apr 3, 2009). "The Automation of Science". Science. 324 (5923). American Association for the Advancement of Science (AAAS): 85–89. doi:10.1126/science.1165620. ISSN 0036-8075.
  26. ^ Vance, Ashlee (3 July 2014). "Emerald Therapeutics: Biotech Lab for Hire". Bloomberg. Archived from the original on 5 July 2017. Retrieved 30 October 2019.
  27. ^ "Biotech Startup Transcriptic Receives $1.2M In Seed Funding Led By Google Ventures And FF Angel". TechCrunch. Dec 13, 2012. Retrieved Dec 12, 2012.
  28. ^ Buhr, Sarah (Jul 8, 2014). "Emerald Cloud Laboratory Is Experimenting With Drugs In The Cloud – TechCrunch". TechCrunch. Retrieved Dec 9, 2021.
  29. ^ "Carnegie Mellon Gets $150M Grant for Science and Robotics". GovTech. May 27, 2021. Retrieved Dec 9, 2021.
  30. ^ Castellanos, Sara (Aug 30, 2021). "Carnegie Mellon's Cloud Lab to Automate Labor-Intensive Science Experiments". WSJ. Retrieved Dec 9, 2021.
Retrieved from "https://en.wikipedia.org/w/index.php?title=User:Cglife.bmarcus/sandbox&oldid=1087006154"