Team:Freiburg Bioware/Team/Collaboration

From 2010.igem.org

(Difference between revisions)
Line 4: Line 4:
[http://2010.igem.org/Team:Freiburg_Bioware/Team => Back to Team overview]
[http://2010.igem.org/Team:Freiburg_Bioware/Team => Back to Team overview]
<html>
<html>
-
<h1 style='text-align:justify'><span lang=EN-US>Collaborations</span></h1>
+
<h1 style='text-align:justify'><span lang=EN-US>Collaboration</span></h1>
<h2><span lang=EN-US>Collaboration with the iGEM 2010 Team ESBS-Strasbourg</span></h2>
<h2><span lang=EN-US>Collaboration with the iGEM 2010 Team ESBS-Strasbourg</span></h2>
Line 50: Line 50:
<p class=MsoNormal style='margin-bottom:0cm;margin-bottom:.0001pt;text-align:
<p class=MsoNormal style='margin-bottom:0cm;margin-bottom:.0001pt;text-align:
justify'><span lang=EN-US>&nbsp;</span></p>
justify'><span lang=EN-US>&nbsp;</span></p>
-
<h2><span lang=EN-US>Helping out the <span class=apple-style-span>iGEM Team
+
<h2><span lang=EN-US>Collaboration with the iGEM 2010 Team Stockholm </span></span></h2>
-
Stockholm 2010 </span></span></h2>
+
<img width="200px" height="auto" src="http://2010.igem.org/wiki/images/2/21/Freiburg10_Logo_iGEM_Stockholm.png" />
<img width="200px" height="auto" src="http://2010.igem.org/wiki/images/2/21/Freiburg10_Logo_iGEM_Stockholm.png" />
Line 77: Line 76:
future problems and sent the correct sequence to the iGEM headquarters. Based
future problems and sent the correct sequence to the iGEM headquarters. Based
on these findings iGEM headquarters introduced versioning of the plasmid
on these findings iGEM headquarters introduced versioning of the plasmid
-
backbones and our pSB1C3 was named pSB1C3_001.</span></p>
+
backbones and our pSB1C3 was named pSB1C3_001.
 +
<br/>
 +
 
 +
<p class=MsoNormal style='margin-bottom:0cm;margin-bottom:.0001pt;text-align:
 +
justify'><span lang=EN-US>Mutations in the pSB1C3 backbone:</span></p>
 +
<br/>
<img width="600px" height="auto" src="http://2010.igem.org/wiki/images/e/e6/Freiburg10_pSB1C3_mutations.png" />
<img width="600px" height="auto" src="http://2010.igem.org/wiki/images/e/e6/Freiburg10_pSB1C3_mutations.png" />
-
 
+
<p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;line-height:115%'>&nbsp;</span></p>
-
 
+
-
<p class=MsoNormal style='text-align:justify'><span lang=EN-US>&nbsp;</span></p>
+
<h2 style='text-align:justify'><span lang=EN-US>Collaboration with BIOSS and
<h2 style='text-align:justify'><span lang=EN-US>Collaboration with BIOSS and
Europa Park</span></h2>
Europa Park</span></h2>
-
<p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;line-height:115%'>&nbsp;</span></p>
+
<img width="300px" height="auto" src="http://2010.igem.org/wiki/images/6/65/Freiburg10_Logo_BIOSS.jpg" />
 +
<img width="300px" height="auto" src="http://2010.igem.org/wiki/images/f/f2/Freiburg10_Logo_Europapark.jpg" />
 +
<p class=MsoNormal style='text-align:justify'><span lang=EN-US>TEXTTEXTETXTEXT.
 +
<br/>
<p class=MsoNormal style='text-align:justify'><span lang=EN-US>&nbsp;</span></p>
<p class=MsoNormal style='text-align:justify'><span lang=EN-US>&nbsp;</span></p>

Revision as of 18:41, 25 October 2010

=> Back to Team overview

Collaboration

Collaboration with the iGEM 2010 Team ESBS-Strasbourg

We established a collaboration with the iGEM 2010 Team ESBS-Strasbourg, who asked for our assembled Biobricks of YFP and CFP cloned into the standard pSB1C3 backbone. We sent out the plasmids so that they could use and test the plasmids for their cloning purposes. To expand our collaboration, the Strasbourg team visited us at our laboratory. Both teams made a presentation of their project and exchanged impressions and ideas about iGEM and the daily laboratory work. After that, we spent time together having a nice barbecue.

 

Collaboration with the iGEM 2010 Team Freiburg Software

The Software Team Freiburg programmed Add-on robots for many applications and could offer us some useful features for our cloning approaches. One of them is for example a primer designer.  The primers are designed by choosing the melting temperature and the binding site of the template sequence. The robot finally creates the sequence of the forward primer (Primer 1) and the reverse Primer (Primer 2).  Furthermore, the Software Team supported us in the design and coding of our homepage. In return, our team helped with information about biological interests and cloning procedures and organized the t-shirts and the trip to Boston.

Example for the functioning of the primer designer robot:


 

 

Collaboration with the iGEM 2010 Team Stockholm

The iGEM Team Stockholm 2010 was interested in using the Freiburg standard 25 and contacted us in order to get information about cloning vectors from our stocks concerning the three pSB1X3-derived BBa_J18901-3 plasmids, as well as the pMA (-BBRF) vector (BBa_K157000) available in the Registry.  We made the advice that the Freiburg iGEM 2009 team last year used the pMA vector for almost all cloning steps. The plasmid is small and delivers high yields of plasmid DNA. In comparison to that the larger BBa_J18901-3 plasmids carry two antibiotic resistances making the part assembly more restricted.


Collaboration with iGEM headquarters

In addition to the usual team collaborations, we communicated with the iGEM headquarters and pointed out that we had difficulties with the pSB1C3 plasmid vector sequence.  A restriction digest of the backbone yielded more fragments than expected. Therefore we sequenced the whole backbone and found 7 mutations. Although the vector replicated fine and the antibiotic resistance was functional, we feared potential future problems and sent the correct sequence to the iGEM headquarters. Based on these findings iGEM headquarters introduced versioning of the plasmid backbones and our pSB1C3 was named pSB1C3_001.

Mutations in the pSB1C3 backbone:


 

Collaboration with BIOSS and Europa Park

TEXTTEXTETXTEXT.

 

Collaboration with the iGEM Team ESBS-Strasbourg

Text

Collaboration with the iGEM Team Freiburg_Software

Text

Cuckoo Clock Competition - Impressions from all over the world

Text

Sequencing the pSB1C3 backbone

Text