Team:Berkeley/Attributions
From 2012.igem.org
Line 45: | Line 45: | ||
<b>Wetlab</b> | <b>Wetlab</b> | ||
<p> | <p> | ||
- | Many of our basic parts (promoters, terminators, and fluorescent proteins) are courtesy of the <a href="http://dueberlab.berkeley.edu/">Dueber Lab</a> at UC Berkeley, our host this year. | + | Many of our basic parts (promoters, terminators, and fluorescent proteins) are courtesy of the <a href="http://dueberlab.berkeley.edu/">Dueber Lab</a> at UC Berkeley, our host this year. Our iGEM team chose the targeting proteins and sequences from the the <a href="http://yeastgfp.yeastgenome.org/"> Yeast GFP Database</a> created by the O'Shea and Weissman Labs at UCSF, and either PCRed them from genomic DNA or synthesized them via gene synthesis. We then combined these parts with the basic parts provided by the Dueber Lab to build all the devices they utilized. |
<p> | <p> | ||
- | All the device cloning was done by | + | All the device cloning was done by our iGEM team. This involved many Golden Gate Assembly reactions, minipreps, transformations, digestions, yeast integrations, etc. While some of the Golden Gate backbones were provided by the Dueber Lab, many of the parts specific to MiCode project, specifically the backbones for multigene and full MiCode assembly, were designed and cloned by us. |
<p> | <p> | ||
- | The leucine zipper sequences were courtesy of the <a href="http://web.mit.edu/biology/keating/KeatingLab/Home.html"> | + | The leucine zipper sequences were provided courtesy of the <a href="http://web.mit.edu/biology/keating/KeatingLab/Home.html"> |
- | Keating Lab</a> at MIT, in a collaborative effort to identify an orthogonal interaction set. With the sequences provided, | + | Keating Lab</a> at MIT, in a collaborative effort to identify an orthogonal interaction set. With the sequences provided, we constructed the leucine zippers via gene synthesis, combined them into their MiCode construction scheme, and assayed them in yeast. |
<p> | <p> | ||
Line 71: | Line 71: | ||
<br> | <br> | ||
<p> | <p> | ||
- | With their permission, we began with the template of the <a href="https://2011.igem.org/Team:Berkeley">Berkeley 2011 iGEM team</a>, and tweaked it to our needs this year. | + | With their permission, we began with the template of the <a href="https://2011.igem.org/Team:Berkeley">Berkeley 2011 iGEM team</a>, and tweaked it to our needs this year. All the content were created by us except for the blue banner and Berkeley logo, which were provided by the University. |
</p> | </p> | ||
</html> | </html> |
Revision as of 10:15, 29 September 2012
Wetlab
Many of our basic parts (promoters, terminators, and fluorescent proteins) are courtesy of the Dueber Lab at UC Berkeley, our host this year. Our iGEM team chose the targeting proteins and sequences from the the Yeast GFP Database created by the O'Shea and Weissman Labs at UCSF, and either PCRed them from genomic DNA or synthesized them via gene synthesis. We then combined these parts with the basic parts provided by the Dueber Lab to build all the devices they utilized.
All the device cloning was done by our iGEM team. This involved many Golden Gate Assembly reactions, minipreps, transformations, digestions, yeast integrations, etc. While some of the Golden Gate backbones were provided by the Dueber Lab, many of the parts specific to MiCode project, specifically the backbones for multigene and full MiCode assembly, were designed and cloned by us.
The leucine zipper sequences were provided courtesy of the Keating Lab at MIT, in a collaborative effort to identify an orthogonal interaction set. With the sequences provided, we constructed the leucine zippers via gene synthesis, combined them into their MiCode construction scheme, and assayed them in yeast.
Computational
On the software side, the iGEM team wrote the MATLAB code, constructed the Cell Profiler pipeline for automated image analysis, and tested it using images generated by the iGEM team.
Website
With their permission, we began with the template of the Berkeley 2011 iGEM team, and tweaked it to our needs this year. All the content were created by us except for the blue banner and Berkeley logo, which were provided by the University.