Difference between revisions of "Team:Marburg/Collaborations"

Line 362: Line 362:
 
                         designing their first own in-silico parts with our guidance.
 
                         designing their first own in-silico parts with our guidance.
 
                       </p>
 
                       </p>
                       <p>
+
                       <p style="margin-bottom: 25px;">
 
                         The main documents of the Golgen Gate Webinar<br>
 
                         The main documents of the Golgen Gate Webinar<br>
 
                         → Download: <a
 
                         → Download: <a
Line 392: Line 392:
 
                     <div class="content-inner" style="text-align: left;">
 
                     <div class="content-inner" style="text-align: left;">
 
                       <h3>Interlab - Accelerate Golden Gate Assembly</h3>
 
                       <h3>Interlab - Accelerate Golden Gate Assembly</h3>
                       <figure style="float:left; margin-left: 25px;">
+
                       <div style="display: flex; flex-direction: row;">
                         <img src="  https://static.igem.org/mediawiki/2019/7/79/T--marburg--interlab_button.svg"
+
                         <p>
                           alt="Interlab button">
+
                           Interlab - Accelerate Golden Gate Assembly
                      </figure>
+
                          As we are constantly working on improving the efficiency of Golden Gate. We clearly
                      Interlab - Accelerate Golden Gate Assembly
+
                          saw the main bottleneck of the reaction was the long assembly time in the cycler.
                      As we are constantly working on improving the efficiency of Golden Gate. We clearly
+
                          In the webinar and in ourGolden Gate community weprovided protocols with three different
                      saw the main bottleneck of the reaction was the long assembly time in the cycler.
+
                          cycler settings for different applications.
                      In the webinar and in ourGolden Gate community weprovided protocols with three different
+
                          Although these threeprotocols were tested before, they were never compared to each other in
                      cycler settings for different applications.
+
                          their efficiency.<br>
                      Although these threeprotocols were tested before, they were never compared to each other in
+
                          We conducted our own Interlab study in collaboration with the iGEM Teams from
                      their efficiency.<br>
+
                          <a style="padding: 0;" href="https://2019.igem.org/Team:TUDelft"> TUDelft </a>,
                      We conducted our own Interlab study in collaboration with the iGEM Teams from
+
                          <a style="padding: 0;" href="https://2019.igem.org/Team:Humboldt_Berlin"> HUmboldt Berlin </a>
                      <a href="https://2019.igem.org/Team:TUDelft"> TUDelft </a>,
+
                          and
                      <a href="https://2019.igem.org/Team:Humboldt_Berlin"> HUmboldt Berlin </a> and
+
                          <a style="padding: 0;" href="https://2019.igem.org/Team:TU_Kaiserslautern"> TU Kaiserslautern
                      <a href="https://2019.igem.org/Team:TU_Kaiserslautern"> TU Kaiserslautern </a>
+
                          </a>
                      In order to find the best protocol, we supplied the teams with specific Level 0
+
                          In order to find the best protocol, we supplied the teams with specific Level 0
                      parts,that should be assembled to a Level 1 vector using the three different cycler
+
                          parts,that should be assembled to a Level 1 vector using the three different cycler
                      conditions.
+
                          conditions. The provided parts areshown in the table
                      The provided parts areshown in this table:
+
                        </p>
 +
                        <figure style="float:left; margin-left: 25px;">
 +
                          <img src="  https://static.igem.org/mediawiki/2019/7/79/T--marburg--interlab_button.svg"
 +
                            alt="Interlab button">
 +
                        </figure>
 +
                      </div>
 +
 
 +
 
 
                       <br> <br>
 
                       <br> <br>
 
                       <table>
 
                       <table>

Revision as of 20:53, 21 October 2019

C O L L A B O R A T I O N S


Through this iGEM year we interacted with so many iGEM Teams all around the world. It was a pleasure working with all the different teams and learn from each other. We got so many impressions about other projects and hope we could help with our collaborations. A huge Thank you for every team collaboration!


C O L O N Y
P I C T U R E S


In our colony picking collaboration we asked other iGEM teams to supply us with data for our picking algorithm. Thanks to this group effort we could build our colony picking unit.

T H EAG O L D E NAG A T E

C O L L A B O R A T I O N


B E R L I N / D E L F T


U CAD A V I S


U F L O R I D A


I N T E R A C T I O N S

W I T H

O T H E RAT E A M S


M E E T U P S