"
Team:Berkeley/Attributions
From 2012.igem.org
| (18 intermediate revisions not shown) | |||
| Line 6: | Line 6: | ||
| - | |||
| - | + | <div class = "col12" id = "spacer4"> | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | <div class="col12" id="spacer4" | + | |
| - | + | ||
</div> | </div> | ||
| - | |||
<div class="row"> | <div class="row"> | ||
| Line 45: | Line 22: | ||
<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. 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 | + | 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 ourselves. We then combined these parts with the basic parts provided by the Dueber Lab to build all the devices we utilized. |
| + | <br> | ||
| + | <br> | ||
| - | |||
| - | |||
<p> | <p> | ||
| - | + | All the higher-order (cassette, multigene, full MiCode) device cloning, which mainly involved Golden Gate Assembly, was done by our iGEM team. 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. Additionally, we produced all the yeast strains necessary throughout our entire iGEM project and did all the image acquisition and analysis. | |
| - | + | <br> | |
| + | <br> | ||
<p> | <p> | ||
| + | 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, we constructed the leucine zippers via gene synthesis, combined them into our MiCode construction scheme, and assayed them in yeast. | ||
<br> | <br> | ||
| Line 63: | Line 42: | ||
<p> | <p> | ||
| - | On the software side, we wrote | + | On the software side, we wrote the MATLAB code, constructed the Cell Profiler pipeline for automated image analysis, and tested it using images generated by our iGEM team. Matlab object identification functions from the <a href="http://www.mathworks.com/matlabcentral/">community forum</a> were used as templates for the basis of our own code. We developed CellProfiler pipelines with the aid of the <a href="http://www.cellprofiler.org/CPmanual/">CellProfiler manual</a> and sample pipelines from the <a href="http://cellprofiler.org/forum/"> online forum</a>. |
| + | |||
<br> | <br> | ||
<br> | <br> | ||
<br> | <br> | ||
| - | <b>Website</b> | + | <b>Website, Presentation, and Poster</b> |
<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. All the content was created by us except for the blue banner and Berkeley logo (provided by the <a href="http://www.berkeley.edu/">University</a>), and the Javascript necessary for our slideshow (provided by <a href="http://nivo.dev7studios.com/">Dev7 Studios</a>). | + | With their permission, we began with the website 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 was created by us except for the blue banner and Berkeley logo (provided by the <a href="http://www.berkeley.edu/">University</a>), and the Javascript necessary for our slideshow on the front page (provided by <a href="http://nivo.dev7studios.com/">Dev7 Studios</a>). |
| + | |||
| + | <p> | ||
| + | For the presentation and poster, any images not of our creation are cited where relevant. | ||
| + | |||
</p> | </p> | ||
</html> | </html> | ||
Latest revision as of 07:50, 17 October 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 ourselves. We then combined these parts with the basic parts provided by the Dueber Lab to build all the devices we utilized.
All the higher-order (cassette, multigene, full MiCode) device cloning, which mainly involved Golden Gate Assembly, was done by our iGEM team. 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. Additionally, we produced all the yeast strains necessary throughout our entire iGEM project and did all the image acquisition and analysis.
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 our MiCode construction scheme, and assayed them in yeast.
Computational
On the software side, we wrote the MATLAB code, constructed the Cell Profiler pipeline for automated image analysis, and tested it using images generated by our iGEM team. Matlab object identification functions from the community forum were used as templates for the basis of our own code. We developed CellProfiler pipelines with the aid of the CellProfiler manual and sample pipelines from the online forum.
Website, Presentation, and Poster
With their permission, we began with the website template of the Berkeley 2011 iGEM team, and tweaked it to our needs this year. All the content was created by us except for the blue banner and Berkeley logo (provided by the University), and the Javascript necessary for our slideshow on the front page (provided by Dev7 Studios).
For the presentation and poster, any images not of our creation are cited where relevant.
