Difference between revisions of "Team:Marburg/test joana"

 
(18 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
<html>
 
<html>
 
   <style>
 
   <style>
−
    .popup-content {
 
−
      max-height: calc(100vh - 88px - 4em) !important;
 
−
    }
 
−
 
−
    .lbl-toggle {
 
−
      text-align: inherit !important;
 
−
    }
 
−
 
 
     .sub {
 
     .sub {
 
       height: 300px !important;
 
       height: 300px !important;
−
    }
 
−
 
−
    .popup li {
 
−
      font-size: large !important;
 
−
    }
 
−
 
−
    .box-dark {
 
−
      background-color: #3d404d;
 
−
      min-height: 30vh;
 
−
      box-shadow: 1px 1px 40px black;
 
−
      margin-left: -10vw;
 
−
      width: 120vw;
 
−
      position: relative;
 
−
      z-index: 2;
 
−
      display: flex;
 
−
      flex-direction: column;
 
−
      align-items: center;
 
−
      transform: rotate(355deg);
 
−
      justify-content: center;
 
−
      margin-top: -12vh;
 
−
    }
 
−
 
−
    .heading {
 
−
      color: #f5f5f5;
 
−
      text-align: center;
 
−
      font-size: 1.75em;
 
−
      width: fit-content;
 
−
      margin-top: 25px;
 
−
      margin-bottom: unset !important;
 
−
      transform: rotate(-355deg);
 
−
    }
 
−
 
−
    .line {
 
−
      border-top: 2px solid #f5f5f5;
 
−
      background-color: #f5f5f5;
 
−
      border-width: 2px;
 
−
      display: block;
 
−
      width: 100px;
 
−
      margin-top: 25px;
 
−
      margin-bottom: unset;
 
−
      transform: rotate(-355deg);
 
−
    }
 
−
 
−
    .logo {
 
−
      width: 100px;
 
−
      height: 100px;
 
−
      position: absolute;
 
−
      bottom: -50px;
 
−
      transform: rotate(-355deg);
 
−
      margin-left: -10px;
 
−
    }
 
−
 
−
    .main {
 
−
      overflow-x: hidden;
 
−
    }
 
−
 
−
    hr {
 
−
      display: block;
 
−
      height: 1px;
 
−
      border: 0;
 
−
      border-top: 2px solid #3d404d;
 
−
      padding: 0;
 
−
      margin: 1em auto;
 
−
      width: 50vw;
 
−
    }
 
−
 
−
    @media (max-width: 810px) {
 
−
 
−
      .logo,
 
−
      .line,
 
−
      .heading {
 
−
        margin-left: -30px;
 
−
      }
 
−
 
−
      .line {
 
−
        margin: 1.5rem 0 !important;
 
−
        margin-left: -40px !important;
 
−
      }
 
 
     }
 
     }
 
   </style>
 
   </style>
Line 480: Line 394:
 
                           href=https://static.igem.org/mediawiki/2019/a/a0/T--marburg--Interlab_protocoll.pdf>here </a>. </p>
 
                           href=https://static.igem.org/mediawiki/2019/a/a0/T--marburg--Interlab_protocoll.pdf>here </a>. </p>
 
                           <p>
 
                           <p>
 +
                              <br>
 
                               <b>results</b>
 
                               <b>results</b>
−
                               lkdjsdjf
+
                               <br>
 +
                              First we wanted to know which protocol worked best for every team. For this we analysed the data of the correct assembled green colonies for every protocol. The data of the different teams is shown in table 1. The total colony count is hard to compare directly, cause the numbers differ very much between the teams. This could come through the different transformation efficiencies for example because of the variating competent cells the teams used.<br>
 +
                              <br>
 +
                              <figure style="text-align:center">
 +
                                    <img style="height: 250px; width: 500px;" src="https://static.igem.org/mediawiki/2019/4/4a/T--Marburg--Tabelle_Interlab.png" alt="The results of the teams in Figure 1 show,  that the protocols work differently for the teams. In generell the most colonies were received with long Troubleshoot protocol, but also the Rapid and Improved protocols show high numbers of correct colonies.">
 +
                                    <figcaption style="max-width: 2400px; text-align: center">
 +
                                        Fig.1 - The results of the teams in Figure 1 show,  that the protocols work differently for the teams. In generell the most colonies were received with long Troubleshoot protocol, but also the Rapid and Improved protocols show high numbers of correct colonies.
 +
                                    </figcaption>
 +
                                </figure>
 +
                                <br>
 +
                                <figure style="text-align:center">
 +
                                        <img style="height: 400px; width: 500px;" src="https://static.igem.org/mediawiki/2019/3/3a/T--Marburg--Interlab_1.png" alt="The results of the teams in Figure 1 show,  that the protocols work differently for the teams. In generell the most colonies were received with long Troubleshoot protocol, but also the Rapid and Improved protocols show high numbers of correct colonies.">
 +
                                        <figcaption style="max-width: 2400px; text-align: center">
 +
                                            Fig.2
 +
                                        </figcaption>
 +
                                    </figure>
 +
                            <br>
 +
                            But which protocol is the most efficient one?
 +
To compare the results of the teams the ratio of the gained correct colonies between the protocols were averaged. The data are shown in Figure 2 and show, that the long Troubleshoot assembly works the best. The fastest assembly (rapid) works the second best. This is very interesting, because this assembly takes significant less time.<br>
 +
<br>
 +
We would propose to take the troubleshoot protocol for complicated assemblies and the rapid protocol for easy assemblies like lvl0.<br>
 +
<figure style="text-align:center">
 +
        <img style="height: 400px; width: 500px;" src="https://static.igem.org/mediawiki/2019/a/a1/T--Marburg--Interlab_3.png" alt="The results of the teams in Figure 1 show,  that the protocols work differently for the teams. In generell the most colonies were received with long Troubleshoot protocol, but also the Rapid and Improved protocols show high numbers of correct colonies.">
 +
        <figcaption style="max-width: 2400px; text-align: center">
 +
            Fig.3
 +
        </figcaption>
 +
    </figure>
 +
                             
 +
 
 
                           </p>
 
                           </p>
 
                           </div> </div> </div> </section> </div> </div> </div>
 
                           </div> </div> </div> </section> </div> </div> </div>

Latest revision as of 14:26, 8 December 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

Our team made itself the goal to introduce other iGEM Teams to Golden Gate. Therefore we hosted a webinar, build up a Communication Platform and made an Interlab.

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