Team:Berkeley Wetlab/Automation
From 2009.igem.org
Jennbrophy (Talk | contribs) (→Clonebots) |
Jennbrophy (Talk | contribs) (→oligoDesigner) |
||
(209 intermediate revisions not shown) | |||
Line 1: | Line 1: | ||
+ | __NOTOC__ | ||
+ | |||
{{newtemplateBerkeley}} | {{newtemplateBerkeley}} | ||
<html> | <html> | ||
Line 13: | Line 15: | ||
===Why Automate?=== | ===Why Automate?=== | ||
- | Our approach to characterizing cell surface display required us to make a lot of parts. Without an automated mode of assembly it would not be possible for us to make enough parts to characterize cell surface display | + | Our approach to characterizing cell surface display required us to make a lot of parts. Without an automated mode of assembly it would not be possible for us to make enough parts to characterize cell surface display using a combinatorial method. |
==Making Basic Parts== | ==Making Basic Parts== | ||
- | Making basic parts is the first step toward making any synthetic biology device. | + | Making basic parts is the first step toward making any synthetic biology device. After designing all of the basic parts we needed for our cell surface display project, our team developed a method for doing cheap in-house gene synthesis. This method allowed us to easily make a very large number of basic parts.<br> |
- | + | [[Image:Berkeleybasicpartmaking.png|500px|center]] | |
- | + | ====oligoDesigner==== | |
- | + | We created a software called oligoDesigner to facilitate gene synthesis and PCR-based cloning for BglBrick parts. You can download it [https://andersonlab.qb3.berkeley.edu/Software/oligoDesigner.zip here]. OligoDesigner will take a list of goal part sequences as input, remove restriction sites, and output all of the oligo nucleotides needed to fabricate the goal part. OligoDesigner will also output an IDT ([http://www.idtdna.com/Home/Home.aspx Integrated DNA Technologies]) order form to order all of the oligonucleotides it designed for PCR or gene synthesis.<br> | |
+ | {|cellpadding="5" cellspacing="0" | ||
+ | |[[Image:BerkeleyoligoDesigner.jpg|oligoDesigner|150px]]<br> | ||
+ | '''oligoDesigner'''<br> | ||
+ | ||[[Image:Berkeleyarrow.png|25px]] | ||
+ | ||[[Image:BerkeleyIDT.jpg|120px|IDT Ordering Form]]<br> | ||
+ | '''IDT Ordering Form'''<br> | ||
+ | ||[[Image:Berkeleyarrow.png|25px]] | ||
+ | ||[[Image:IDT96berkeley.png|125px]]<br> | ||
+ | <center>'''IDT 96 well plate'''</center> | ||
+ | ||[[Image:Berkeleyarrow.png|25px]] | ||
+ | |[[Image:BerkeleyLiquidRobot.jpg|200px]]<br> | ||
+ | <center>'''Liquid Handling Robot'''</center> | ||
+ | ||[[Image:Berkeleyarrow.png|25px]] | ||
+ | |[[Image:Berkeleybasicparts.png|170px]]<br> | ||
+ | <center>'''Basic Parts'''</center> | ||
+ | |} | ||
+ | Oligo nucleotides arrive from IDT in a 96 well plate format. OligoDesigner will then generate commands for a liquid handling robot to resuspend the oligo nucleotides to the correct concentrations. It will also generate commands that tell the liquid handling robot how to mix the oligos in order to get the correct PCR products. <br> | ||
+ | After the liquid handling robot finishes mixing oligo nucleotides, all we need to do to get our basic parts is add the correct buffers and enzymes and put the resultant tubes in a thermocycler for PCR. | ||
==Making Composite Parts== | ==Making Composite Parts== | ||
- | The next step, after making new basic parts, is to assemble those basic parts into composite part devices. There has been a lot of work being done at UC Berkeley to automate the process of composite part assembly. | + | The next step, after making new basic parts, is to assemble those basic parts into composite part devices. There has been a lot of work being done at UC Berkeley to automate the process of composite part assembly. This year our team was able to implement many newly developed techniques to create a large number of composite parts. |
- | === | + | ===2AB Layered Assembly=== |
- | [[Image:BerkeleyAssembly.png| | + | Our team used a method of basic part assembly called Two AntiBiotic (2AB) Assembly to create composite parts. 2AB assembly is a straight-forward and robust method for combining two or more basic parts into a destination vector. It is a layered assembly scheme used by the Anderson Lab at UC Berkeley. For more information about 2AB Assembly please visit the [https://2008.igem.org/Team:UC_Berkeley/LayeredAssembly Layered Assembly page] of the 2008 Berkeley iGEM wiki.<br> |
+ | <center>'''Basic 2AB Assembly Schematic'''</center> | ||
+ | [[Image:BerkeleyAssembly.png|300px|center]] | ||
+ | The 2AB assembly method lends itself well to automation because it consists mostly of liquid handling. Basic parts must be put into the correct specialized assembly vector, and then mixed with other basic parts in the correct order, to yield goal composite parts. The process of putting basic parts into the correct specialized assembly vectors is based on the Gateway recombination chemistry from Invitrogen. An in vivo gateway scheme amenable to high throughput was developed by the 2008 Berkeley iGEM team. This year we were able to use their in vivo gateway scheme to put our basic parts into the correct specialized assembly vectors. To read more about in vivo gateway visit the 2008 Berkeley iGEM wiki [https://2008.igem.org/Team:UC_Berkeley here].<br> | ||
+ | <center>'''Gateway Concept'''</center> | ||
+ | [[Image:BerkeleyGateway.png|center|500px]] | ||
+ | |||
+ | ===Clotho and Liquid Handling Robot=== | ||
+ | 2AB assembly utilizes six different types of specialized assembly vectors to make composite parts. In order to make composite parts in the least number of steps, an assembly tree, outlining the assembly process, must be generated. Assembly trees specify which specialized assembly vector to put basic parts in and specify the order in which composite part intermediates should be made. Generating assembly trees manually can be very difficult, especially when you need to make a large number of complicated parts. This year Berkeley's Computational Team built a plugin for Clotho (their software project) to help us make assembly trees. After generating assembly trees with Clotho and gateway-ing our parts into the correct vectors we can begin to build composite parts. To read more about Clotho please visit the [https://2009.igem.org/Team:Berkeley_Software 2009 Berkeley Computational Team wiki].<br> | ||
- | + | [[Image:BerkeleyWetlabClotho.png|450px|center]] <br> | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | To build composite parts we use another Clotho tool built by the 2009 Berkeley Computational Team. This Clotho tool, named Kepler, generates a series of commands for a liquid handling robot to build goal composite parts based on the assembly tree it generated. Kepler will also output a series of human readable instructions that can guide researchers though the un-automated steps of the assembly protocol. By utilizing a combination of specialized software, liquid handling hardware, and newly developed chemistry, we were able to automate our composite part assembly process.<br> | |
- | + | <br> | |
+ | [[Image:BerkeleyAssemblyAutomation.png|800px|center]] | ||
- | ==Success | + | ==Success== |
Using our newly developed automated assembly processes we were able to make over 800 parts (both basic and composite) in one summer! This magnitude of part making is unprecedented in iGEM competitions and enabled us to test a very large number of variations on cell surface display systems. | Using our newly developed automated assembly processes we were able to make over 800 parts (both basic and composite) in one summer! This magnitude of part making is unprecedented in iGEM competitions and enabled us to test a very large number of variations on cell surface display systems. | ||
===Success Rates=== | ===Success Rates=== | ||
- | The assembly scheme we developed works just as well as assembly by hand and is much faster. | + | '''Stats:'''<br> |
- | + | * <7% of every assembly set yielded no colonies | |
- | + | * 12-15% of the colonies in each set that did grow were co-transformed (meaning the cells took up more than one of our specialized assembly vectors, which is undesirable). We have a simple screening test to check for co-transformation, so this was not a problem. | |
- | + | * We sequenced approximately 10% of all final products, and found that 90% of the things we sequenced were correct. When assembly sets were found to be incorrect, we started the set over again from the last successful intermediate, and we were usually able to trace the flaw in the assembly to a human error. | |
- | + | The assembly scheme we developed works just as well as assembly by hand and is much faster. Visit Jenn Brophy and Gabriela Guzman's [https://2009.igem.org/Team:Berkeley_Wetlab/NoteBooks notebooks] for notes on assembly. | |
- | + | ||
- | + | ||
- | + |
Latest revision as of 00:14, 22 October 2009
Why Automate?
Our approach to characterizing cell surface display required us to make a lot of parts. Without an automated mode of assembly it would not be possible for us to make enough parts to characterize cell surface display using a combinatorial method.
Making Basic Parts
Making basic parts is the first step toward making any synthetic biology device. After designing all of the basic parts we needed for our cell surface display project, our team developed a method for doing cheap in-house gene synthesis. This method allowed us to easily make a very large number of basic parts.
oligoDesigner
We created a software called oligoDesigner to facilitate gene synthesis and PCR-based cloning for BglBrick parts. You can download it here. OligoDesigner will take a list of goal part sequences as input, remove restriction sites, and output all of the oligo nucleotides needed to fabricate the goal part. OligoDesigner will also output an IDT ([http://www.idtdna.com/Home/Home.aspx Integrated DNA Technologies]) order form to order all of the oligonucleotides it designed for PCR or gene synthesis.
oligoDesigner | IDT Ordering Form |
Oligo nucleotides arrive from IDT in a 96 well plate format. OligoDesigner will then generate commands for a liquid handling robot to resuspend the oligo nucleotides to the correct concentrations. It will also generate commands that tell the liquid handling robot how to mix the oligos in order to get the correct PCR products.
After the liquid handling robot finishes mixing oligo nucleotides, all we need to do to get our basic parts is add the correct buffers and enzymes and put the resultant tubes in a thermocycler for PCR.
Making Composite Parts
The next step, after making new basic parts, is to assemble those basic parts into composite part devices. There has been a lot of work being done at UC Berkeley to automate the process of composite part assembly. This year our team was able to implement many newly developed techniques to create a large number of composite parts.
2AB Layered Assembly
Our team used a method of basic part assembly called Two AntiBiotic (2AB) Assembly to create composite parts. 2AB assembly is a straight-forward and robust method for combining two or more basic parts into a destination vector. It is a layered assembly scheme used by the Anderson Lab at UC Berkeley. For more information about 2AB Assembly please visit the Layered Assembly page of the 2008 Berkeley iGEM wiki.
The 2AB assembly method lends itself well to automation because it consists mostly of liquid handling. Basic parts must be put into the correct specialized assembly vector, and then mixed with other basic parts in the correct order, to yield goal composite parts. The process of putting basic parts into the correct specialized assembly vectors is based on the Gateway recombination chemistry from Invitrogen. An in vivo gateway scheme amenable to high throughput was developed by the 2008 Berkeley iGEM team. This year we were able to use their in vivo gateway scheme to put our basic parts into the correct specialized assembly vectors. To read more about in vivo gateway visit the 2008 Berkeley iGEM wiki here.
Clotho and Liquid Handling Robot
2AB assembly utilizes six different types of specialized assembly vectors to make composite parts. In order to make composite parts in the least number of steps, an assembly tree, outlining the assembly process, must be generated. Assembly trees specify which specialized assembly vector to put basic parts in and specify the order in which composite part intermediates should be made. Generating assembly trees manually can be very difficult, especially when you need to make a large number of complicated parts. This year Berkeley's Computational Team built a plugin for Clotho (their software project) to help us make assembly trees. After generating assembly trees with Clotho and gateway-ing our parts into the correct vectors we can begin to build composite parts. To read more about Clotho please visit the 2009 Berkeley Computational Team wiki.
To build composite parts we use another Clotho tool built by the 2009 Berkeley Computational Team. This Clotho tool, named Kepler, generates a series of commands for a liquid handling robot to build goal composite parts based on the assembly tree it generated. Kepler will also output a series of human readable instructions that can guide researchers though the un-automated steps of the assembly protocol. By utilizing a combination of specialized software, liquid handling hardware, and newly developed chemistry, we were able to automate our composite part assembly process.
Success
Using our newly developed automated assembly processes we were able to make over 800 parts (both basic and composite) in one summer! This magnitude of part making is unprecedented in iGEM competitions and enabled us to test a very large number of variations on cell surface display systems.
Success Rates
Stats:
- <7% of every assembly set yielded no colonies
- 12-15% of the colonies in each set that did grow were co-transformed (meaning the cells took up more than one of our specialized assembly vectors, which is undesirable). We have a simple screening test to check for co-transformation, so this was not a problem.
- We sequenced approximately 10% of all final products, and found that 90% of the things we sequenced were correct. When assembly sets were found to be incorrect, we started the set over again from the last successful intermediate, and we were usually able to trace the flaw in the assembly to a human error.
The assembly scheme we developed works just as well as assembly by hand and is much faster. Visit Jenn Brophy and Gabriela Guzman's notebooks for notes on assembly.