Difference between revisions of "Team:Amsterdam/test/max/Collaborations"

(Created page with "<html> <head> <meta charset="utf-8"> <meta content="ie=edge" http-equiv="x-ua-compatible"> <meta content="width=device-width, initial-scale=1, shrink-to-fit=no" name...")
 
 
Line 7: Line 7:
 
       Collaboration
 
       Collaboration
 
     </title>
 
     </title>
    <!-- icons -->
 
    <!-- <link rel="stylesheet" href="/assets/css/font-awesome-4.7.0/css/font-awesome.min.css"> -->
 
 
     <!-- include normalizer -->
 
     <!-- include normalizer -->
 
     <link href="https://2017.igem.org/Team:Amsterdam/test/max/assets/css/normalize?action=raw&amp;ctype=text/css" rel="stylesheet"/>
 
     <link href="https://2017.igem.org/Team:Amsterdam/test/max/assets/css/normalize?action=raw&amp;ctype=text/css" rel="stylesheet"/>
Line 16: Line 14:
 
     <script src="https://2017.igem.org/Team:Amsterdam/test/max/assets/js/all?action=raw&amp;ctype=text/javascript">
 
     <script src="https://2017.igem.org/Team:Amsterdam/test/max/assets/js/all?action=raw&amp;ctype=text/javascript">
 
     </script>
 
     </script>
     <script src="https://2017.igem.org/Team:Amsterdam/test/max/https://cdn.rawgit.com/michalsnik/aos/2.1.1/dist/aos?action=raw&amp;ctype=text/javascript">
+
    <!-- include mathjax -->
 +
     <script src="https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.2/MathJax.js?config=TeX-MML-AM_CHTML">
 
     </script>
 
     </script>
 
     </meta>
 
     </meta>
Line 43: Line 42:
 
         <ul class="dropdown-menu">
 
         <ul class="dropdown-menu">
 
         <li>
 
         <li>
           <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Modeling">
+
           <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Produce">
          Modeling
+
          </a>
+
        </li>
+
        <li>
+
          <a class="nav-link" href="#">
+
 
           Production
 
           Production
 
           </a>
 
           </a>
 
         </li>
 
         </li>
 
         <li>
 
         <li>
           <a class="nav-link" href="#">
+
           <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Export">
           Transport
+
           Exportation
 
           </a>
 
           </a>
 
         </li>
 
         </li>
 
         <li>
 
         <li>
           <a class="nav-link" href="#">
+
           <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Detect">
           Biosensor
+
           Detection
 
           </a>
 
           </a>
 
         </li>
 
         </li>
 
         </ul>
 
         </ul>
 +
      </li>
 +
      <li class="list-inline-item">
 +
        <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Model">
 +
        Model
 +
        </a>
 
       </li>
 
       </li>
 
       <li class="list-inline-item dropdown">
 
       <li class="list-inline-item dropdown">
         <a class="nav-link" href="#">
+
         <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Practices">
 
         Practices
 
         Practices
 
         <span class="caret">
 
         <span class="caret">
Line 72: Line 71:
 
         <ul class="dropdown-menu">
 
         <ul class="dropdown-menu">
 
         <li>
 
         <li>
           <a class="nav-link" href="#">
+
           <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Carbon">
 
           Carbon Efficiency
 
           Carbon Efficiency
 
           </a>
 
           </a>
 
         </li>
 
         </li>
 
         <li>
 
         <li>
           <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Outreach">
+
           <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Silver">
           Outreach
+
           HP Silver
 +
          </a>
 +
        </li>
 +
        <li>
 +
          <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Gold_Integrated">
 +
          HP Gold
 +
          </a>
 +
        </li>
 +
        <li>
 +
          <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Engagement">
 +
          Engagement
 
           </a>
 
           </a>
 
         </li>
 
         </li>
Line 89: Line 98:
 
       </li>
 
       </li>
 
       <li class="list-inline-item dropdown">
 
       <li class="list-inline-item dropdown">
         <a class="nav-link" href="#">
+
         <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Lab">
 
         Lab
 
         Lab
 
         <span class="caret">
 
         <span class="caret">
Line 96: Line 105:
 
         <ul class="dropdown-menu">
 
         <ul class="dropdown-menu">
 
         <li>
 
         <li>
           <a class="nav-link" href="#">
+
           <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Parts">
 
           Parts
 
           Parts
 
           </a>
 
           </a>
Line 112: Line 121:
 
         <li>
 
         <li>
 
           <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Protocol">
 
           <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Protocol">
           Protocol
+
           Protocols
 
           </a>
 
           </a>
 
         </li>
 
         </li>
 
         <li>
 
         <li>
           <a class="nav-link" href="#">
+
           <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Methods">
 
           Methods
 
           Methods
 
           </a>
 
           </a>
Line 123: Line 132:
 
       </li>
 
       </li>
 
       <li class="list-inline-item dropdown">
 
       <li class="list-inline-item dropdown">
         <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/team">
+
         <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Team">
 
         Team
 
         Team
 
         <span class="caret">
 
         <span class="caret">
Line 147: Line 156:
 
       </li>
 
       </li>
 
       <li class="list-inline-item">
 
       <li class="list-inline-item">
         <a class="nav-link" href="#">
+
         <a class="nav-link" href="https://2017.igem.org/Team:Amsterdam/test/max/Achievements">
 
         Achievements
 
         Achievements
 
         </a>
 
         </a>
Line 155: Line 164:
 
     </nav>
 
     </nav>
 
     <div class="inner cover">
 
     <div class="inner cover">
     <div class="logo-spacer">
+
     <div class="summary-container" id="collaborations">
      <img src="https://static.igem.org/mediawiki/2017/c/cb/Logo_line1.png">
+
       <div class="summary-col-left">
      </img>
+
    </div>
+
    <div class="collab-sum-container">
+
       <div class="safety-sum-left">
+
 
       <img class="proto-icon" src="https://static.igem.org/mediawiki/2017/0/09/Collaboration.png">
 
       <img class="proto-icon" src="https://static.igem.org/mediawiki/2017/0/09/Collaboration.png">
 
       </img>
 
       </img>
 
       </div>
 
       </div>
       <div class="safety-sum-mid">
+
       <div class="summary-col-mid">
       <p class="inter-text">
+
       <p class="summary-text">
         Nobody can do science on their own, so collaborating is a necessity. We had a lot of contact with the other Dutch iGEM teams, via e-mail and at the different meet-ups we attended. Our biggest collaboration is with the team from the University of Nebraska-Lincoln, with whom we had a lot of contact in the past months. Furthermore we attended to two European meet-ups, one in Delft and one in Leuven, where we had a lot of good conversations about science, iGEM and life.
+
         Nobody can do science on their own, so collaborating is a necessity. We had a lot of contact with the other Dutch iGEM teams, via e-mail and at the different meet-ups we attended. Our biggest collaboration is with the team from the University of Nebraska-Lincoln, with whom we had a lot of contact in the past months. Furthermore we attended three international meet-ups, in Delft, Wageningen and Leuven, where we had a lot of good conversations about science, iGEM and
 +
        <a class="summary-text" name="nebraska">
 +
        life.
 +
        </a>
 
       </p>
 
       </p>
 
       </div>
 
       </div>
Line 172: Line 180:
 
       <div class="vertical-text-container">
 
       <div class="vertical-text-container">
 
         <p class="vertical-text">
 
         <p class="vertical-text">
         Collab
+
         Collaborate
 
         </p>
 
         </p>
 
       </div>
 
       </div>
 
       </div>
 
       </div>
 
     </div>
 
     </div>
     <div class="safety-main-container">
+
     <div class="collab-main-container" id="light">
       <div class="safety-main-left">
+
       <div class="collab-main-left">
 
       </div>
 
       </div>
       <div class="safety-main-mid">
+
       <div class="collab-main-mid" id="nebraska">
 
       <p class="collab-header">
 
       <p class="collab-header">
 
         University of Nebraska-Lincoln
 
         University of Nebraska-Lincoln
 
       </p>
 
       </p>
 
       <p class="collab-text">
 
       <p class="collab-text">
         BRAM WILL WRITE THIS SOON BRAM WILL WRITE THIS SOON BRAM WILL WRITE THIS SOON BRAM WILL WRITE THIS SOON BRAM WILL WRITE THIS SOON BRAM WILL WRITE THIS SOON BRAM WILL WRITE THIS SOON BRAM WILL WRITE THIS SOON BRAM WILL WRITE THIS SOON BRAM WILL WRITE THIS SOON BRAM WILL WRITE THIS SOON BRAM WILL WRITE THIS SOON BRAM WILL WRITE THIS SOON BRAM WILL WRITE THIS SOON BRAM WILL WRITE THIS SOON BRAM WILL WRITE THIS SOON BRAM WILL WRITE THIS SOON BRAM WILL WRITE THIS SOON
+
         After the UNL iGEM sent around there iGEM survey, The Amsterdam team and the UNL iGEM team got into contact about combining their knowledge and explore the possibilities of a combined future application of their projects.  In this collaboration, the UNL iGEM team and the Amsterdam iGEM team joined forces to come up with a way to reduce methane emissions. Methane emissions have a huge impact on climate change. iGEM team UNL and iGEM team Amsterdam explored the possibilities of feeding fumarate to cattle, in order to reduce methane emissions. We can conclude that fumarate seems a promising molecule for this application. However, since the literature about the possible effect of fumarate is not consistent, the physiology of cattle opposes some challenges and the maximum fumarate yields in certain organisms under our specific conditions are not yet defined.  Actual empirical research must show if this promising route can lead to lower methane emissions and a more sustainable world!
 
       </p>
 
       </p>
      </div>
+
      <div class="con-extension" id="collab" onclick="displayFunction(this.id)">
      <div class="vertical-text-container-outer">
+
         <p class="in-text-link" id="collabtext">
      <div class="vertical-text-container">
+
        ▶  Click here to display the full collaboration
         <p class="vertical-text">
+
 
         </p>
 
         </p>
 +
      </div>
 +
      <div id="collabextension" style="display:none;">
 +
        <div class="nlu-text-con">
 +
        <p class="collab-header" id="big">
 +
          Reducing methane emissions using thin air
 +
        </p>
 +
        <p class="collab-text" id="big">
 +
          iGEM UNL x iGEM Amsterdam
 +
        </p>
 +
        <p class="collab-header" id="nlu">
 +
          Introduction
 +
        </p>
 +
        <p class="collab-text">
 +
          In this collaboration, we combine the knowledge on genetic engineering to produce fumarate (team iGEM Amsterdam) and the knowledge on the possible impact of fumarate on cattle physiology (team iGEM UNL). Together, we explore the possibilities of using microorganisms to produce fumarate in cattle intestine, to reduce methane emissions by cattle. We explore the possibilities of ways to deliver fumarate in the cow digestive system and the hurdles to overcome with these strategies. As iGEM UNL is working on
 +
          <i>
 +
          E. Coli
 +
          </i>
 +
          and iGEM Amsterdam on the production of  fumarate, we first define a strategy to make a fumarate producing
 +
          <i>
 +
          E. Coli
 +
          </i>
 +
          mutant. Then we assess the mechanism to reduce methane emissions with fumarate. Finally, we explore different ways to deliver fumarate in the cow digestive system.
 +
        </p>
 +
        <p class="collab-header" id="nlu">
 +
          How
 +
          <i>
 +
          E. Coli
 +
          </i>
 +
          can produce fumarate
 +
        </p>
 +
        <p class="collab-text">
 +
          <i>
 +
          E. Coli
 +
          </i>
 +
          can in theory produce fumarate by an oxidative (aerobic) or a reductive (anaerobic) route. In the latter case, the fumarate molecule itself is used as a final electron donor in this process, which is believed to be coupled with cell growth in anaerobic conditions (Iverson
 +
          <i>
 +
          et al.
 +
          </i>
 +
          , 1999). It is assumed that for this reason, it is not possible to genetically engineer
 +
          <i>
 +
          E. Coli
 +
          </i>
 +
          to produce fumarate in anaerobic conditions (Song
 +
          <i>
 +
          et al.
 +
          </i>
 +
          , 2013). This is problematic,as the cattle rumen is anaerobic.
 +
          <br>
 +
          Now if it would be possible to introduce
 +
          <i>
 +
            E. Coli
 +
          </i>
 +
          in aerobic conditions in the cow’s digestive system, we would be able to use aerobically producing fumarate E. coli strains. For this, we could imitate a genetic engineering strategy used by the iGEM Amsterdam project.
 +
          </br>
 +
        </p>
 +
        <p class="collab-header" id="nlu">
 +
          How team Amsterdam produces fumarate in Cyanobacteria
 +
        </p>
 +
        <p class="collab-text">
 +
          In the Cyanobacterial model organism
 +
          <i>
 +
          Synechocystis PCC 6803
 +
          </i>
 +
          , iGEM team Amsterdam managed to produce fumarate in a genetically stable, growth-coupled way, by knocking out the fumarase encoding fumaric acid hydratase (fumC) gene.
 +
        </p>
 +
        <p class="collab-header" id="nlu">
 +
          How we can apply the Amsterdam genetic engineering strategy in
 +
          <i>
 +
          E. Coli
 +
          </i>
 +
        </p>
 +
        <p class="collab-text">
 +
          To apply a similar approach in
 +
          <i>
 +
          E. Coli
 +
          </i>
 +
          and to end up with a respectable titer, multiple gene knock-outs are required.
 +
          <i>
 +
          E. Coli
 +
          </i>
 +
          has more fumarase encoding genes, then Synechoscystis,  namely anaerobic class I fumaric acid hydratase (fumB) and aerobic class I fumaric acid hydratase (fumA), which both need to be knocked out as well (Song
 +
          <i>
 +
          et al.
 +
          </i>
 +
          , 2013). Knocking out the Fumarase proteins leads to a dysfunctional or a ‘broken’ TCA-cycle, since malate cannot be formed anymore from fumarate. This impairs the efficiency of the TCA-cycle and the production of amino acids; since some amino acids are formed from TCA-cycle intermediates (Waegeman
 +
          <i>
 +
          et al.
 +
          </i>
 +
          , 2011) (Fig 1a). Team Amsterdam faced a similar problem and aimed  to incorporate a glyoxylate shunt into Synechocystis to increase fumarate production.  The glyoxylate shunt is composed of two enzymes, which are Malate Synthase and Isocitrate Lyase. They form a shortcut in the TCA-cycle (Fig. 1b).  In this way, the glyoxylate shunt restores some of the flux through part of the TCA-cycle, which should lead to a more efficient TCA-cycle. This is predicted to be beneficial for the cell in terms of fitness, as modelled by iGEM team Amsterdam.  For E.coli, a similar approach could be adopted, since E.coli can express the glyoxylate shunt genes to produce malate from isocitrate via glyoxylate. Thereby, in the process of producing malate, also succinate is formed. Because the cell can produce FADH2 by converting succinate to fumarate, the formed succinate will go to fumarate. In this way we are able to gain fitness and fumarate production, by having the glyoxylate shunt active.
 +
        </p>
 +
        <figure class="collab-img-con">
 +
          <img class="collab-img" src="https://static.igem.org/mediawiki/2017/3/34/Collab-img1.png">
 +
          <figcaption class="collab-img-cap">
 +
            <b>
 +
            Figure 1. The TCA-cycle with and without glyoxylate shunt.
 +
            </b>
 +
            1a). Fumarate is produced in a growth coupled way as a side product of arginine production. By knocking out fumarase, it cannot be degraded to malate. This way Fumarate accumulates. The TCA-cycle however is ‘broken’.1b). By expressing Malate Synthaese (MS) and Isocytrate Lyase (ICL), we can partly fix the ‘broken’ cycle. Now Isocitrate is made into both glyoxylate from which malate is synthesized and into succinate, which can be converted into fumarate. This way we have a better functioning cycle and more fumarate production thanks to the glyoxylate shunt.
 +
          </figcaption>
 +
          </img>
 +
        </figure>
 +
        <p class="collab-text">
 +
          However, when we look at the
 +
          <i>
 +
          E. Coli
 +
          </i>
 +
          physiology, the glyoxylate shunt genes are already present, but repressed by a repressor encoded by the iclR gene (Waegeman
 +
          <i>
 +
          et al.
 +
          </i>
 +
          , 2011). Deleting this gene will make it possible to have an increased flux through the TCA cycle. Using this knockout with minimal mutations, we receive an
 +
          <i>
 +
          E. Coli
 +
          </i>
 +
          which follows the same metabolic engineering principles as the Synechocystis strain proposed by iGEM team Amsterdam, and is therefore expected to be stable in terms of production (Fig. 2).
 +
          <br>
 +
          This strain is previously made by Song
 +
          <i>
 +
            et al.
 +
          </i>
 +
          , (2013) and produced 1.45g/L fumaric acid from 15g/L glucose in 24h in flask culture under aerobic conditions. This strain can be further optimized for higher fumaric acid yields; however, this always comes at the risk of impairing other functions.
 +
          </br>
 +
        </p>
 +
        <figure class="collab-img-con">
 +
          <img class="collab-img" id="small" src="https://static.igem.org/mediawiki/2017/4/42/Collab-img2.png">
 +
          <figcaption class="collab-img-cap" id="small">
 +
            <b>
 +
            Figure 2. Central central metabolic pathways in E. coli after engineering E. coli for fumarate production.
 +
            </b>
 +
            Thick arrows indicate increased flux by the overexpression of the corresponding gene. The X indicates that the deletion of the corresponding gene. Enzymes encoded by the genes shown are: fumA,  aerobic Class I fumaric acid hydratase; fumB, anaerobic class I fumaric acid hydratase; fumC, fumaric acid hydratase (fumarase C); iclR, isocitrate lyase repressor. (Adapted from Song
 +
            <i>
 +
            et al.
 +
            </i>
 +
            (2013))
 +
          </figcaption>
 +
          </img>
 +
        </figure>
 +
        <p class="collab-header" id="nlu">
 +
          Fumarates effect on the microbiome of cattle
 +
        </p>
 +
        <p class="collab-text">
 +
          In theory, fumarate has the potential to decrease methane synthesis in cattle, as it can redirect the available hydrogen into propionate rather than into methane (Fig 3). Fumarate has been proven to reduce methane emission in both in vitro and in vivo studies (Mcginn
 +
          <i>
 +
          et al.
 +
          </i>
 +
          , 2004). However, a recent in vivo study found no effect of adding fumarate to cattle feed on methane emission. This finding contradicts earlier findings. It is possible that a higher level of supplementation than that used in the recent study would be needed to alter methane production in vivo. It is estimated that the level of supplementation in the recent study provided about 15 mM of fumaric acid (assuming a ruminal volume of 40 L; 116.07 g/mol), although these calculations do not account for fluid dilution rate and passage of fumaric acid from the rumen, which are in vivo factors that do not occur in vitro. In vivo, cattle were fed about twice the amount of fumaric acid (20 g/kg DMI) to cattle as that used in the more recent study (12 g/kg DMI) and, surprisingly, methane production decreased by 23%. However, in that study, only two animals per treatment were used, and methane measurements were made using ventilated hoods, which are known to be problematic. Also note there were differences between basal diets in the studies. This influences the microbiomes and may affect the outcome of the study. The figure below shows the theoretical framework made by iGEM UNL, that demonstrates the diversion of hydrogen away from the methanogens and to the process of fumarate production which in turn produces succinate and propionate. It is known that the higher the propionate to acetate ratio, the less methane the cow produces (Mcginn
 +
          <i>
 +
          et al.
 +
          </i>
 +
          , 2004).
 +
        </p>
 +
        <figure class="collab-img-con">
 +
          <img class="collab-img" src="https://static.igem.org/mediawiki/2017/5/5a/Collab-img3.png">
 +
          <figcaption class="collab-img-cap">
 +
            <b>
 +
            Figure 3. The theoretical framework of  the effect of fumarate on methane synthesis in the ruminants.
 +
            </b>
 +
            The synthesis of succinate out of fumarate competes for H
 +
            <sub>
 +
            2
 +
            </sub>
 +
            with the synthesis of methane. With a reduced concentration of substrate H
 +
            <sub>
 +
            2
 +
            </sub>
 +
            for methane synthesis reaction, less methane will be formed. (Adapted from Morgavi
 +
            <i>
 +
            et al.
 +
            </i>
 +
            (2010))
 +
          </figcaption>
 +
          </img>
 +
        </figure>
 +
        <p class="collab-header" id="nlu">
 +
          Strategies to overcome the problem of anaerobic production
 +
        </p>
 +
        <p class="collab-text">
 +
          Another way to get fumarate into in the microbiome of cattle would be to have bacteria produce fumarate in a bioreactor, and then dry and directly mix them with cattle feed. This way, there is no need to extract fumarate from the cell mixture and we also overcome the problem of anaerobic production. We could try to test different types of microorganisms and see which would be the most efficient and cost-effective at producing fumarate. Once the cells have produced enough fumarate, we, dry them and feed them to the cattle. We could compare the proposed
 +
          <i>
 +
          E. Coli
 +
          </i>
 +
          mutants, that produce fumaric acid and cyanobacterial cells from iGEM team Amsterdam that produce fumarate and see which one is more efficient at producing and delivering fumarate. As we aim to reduce greenhouse gasses in both our projects, we think it would be sensible to define the most efficient producer as the one that is the most carbon efficient. As calculated by team Amsterdam, this will most likely be the Cyanobacteria. Cyanobacteria convert CO
 +
          <sub>
 +
          2
 +
          </sub>
 +
          directly into fumarate, fuelled by sunlight. For
 +
          <i>
 +
          E. Coli
 +
          </i>
 +
          , on the contrary, you needs to grow sugar crops, harvest them, and extract the glucose as a carbon source to grow. Taking the whole process into consideration, cyanobacteria will yield more fumarate per CO
 +
          <sub>
 +
          2
 +
          </sub>
 +
          . Exploring other options such as these could provide an efficient and possibly cost-effective way to produce the fumarate that would lower methane emissions in cattle.
 +
        </p>
 +
        <p class="collab-header" id="nlu">
 +
          Conclusions
 +
        </p>
 +
        <p class="collab-text">
 +
          From this pleasant collaboration, we can conclude that adding fumarate to cattle feed remains a promising strategy to reduce methane emissions, although some hurdles have yet to be taken. Some studies report conflicting results about the effect of the addition of fumarate to cattle feed on methane production. Thereby, the absence of oxygen in cattle rumen opposes challenges for the growth of photoautotrophic organisms and oxidative growth of heterotrophic organisms.
 +
          <br>
 +
          On top of that, the exact yields of the strains developed by iGEM team Amsterdam and the proposed
 +
          <i>
 +
            E. Coli
 +
          </i>
 +
          mutant in this paper have yet to be defined. Nevertheless, as shown by the UNL iGEM team, methane emissions pose an enormous problem to our world, that need interdisciplinary teams to come up with out of the box-solutions such as these.
 +
          </br>
 +
        </p>
 +
        <p class="collab-header" id="nlu">
 +
          References
 +
        </p>
 +
        <ul>
 +
          <li class="collab-text">
 +
          Iverson, T. M., Luna-Chavez, C., Cecchini, G., &amp; Rees, D. C. (1999). Structure of the Escherichia coli fumarate reductase respiratory complex. Science, 284(5422), 1961-1966.
 +
          </li>
 +
          <li class="collab-text">
 +
          McGinn, S. M., Beauchemin, K. A., Coates, T., &amp; Colombatto, D. (2004). Methane emissions from beef cattle: Effects of monensin, sunflower oil, enzymes, yeast, and fumaric acid. Journal of animal science, 82(11), 3346-3356.
 +
          </li>
 +
          <li class="collab-text">
 +
          Song, C. W., Kim, D. I., Choi, S., Jang, J. W., &amp; Lee, S. Y. (2013). Metabolic engineering of Escherichia coli for the production of fumaric acid. Biotechnology and bioengineering, 110(7), 2025-2034.
 +
          </li>
 +
          <li class="collab-text">
 +
          Waegeman, H., Beauprez, J., Moens, H., Maertens, J., De Mey, M., Foulquié-Moreno, M. R., ... &amp; Soetaert, W. (2011). Effect of iclR and arcA knockouts on biomass formation and metabolic fluxes in Escherichia coli K12 and its implications on understanding the metabolism of Escherichia coli BL21 (DE3). BMC microbiology, 11(1), 70.
 +
          </li>
 +
        </ul>
 +
        <div class="con-extension" id="collab" onclick="displayFunction(this.id)">
 +
          <a class="con-extension" href="#nebraska">
 +
          <div class="col-arr">
 +
            <p class="in-text-link" id="collabarrow">
 +
            ▲
 +
            </p>
 +
          </div>
 +
          <p class="in-text-link">
 +
            Click here to hide the full collaboration
 +
          </p>
 +
          </a>
 +
        </div>
 +
        </div>
 
       </div>
 
       </div>
 
       </div>
 
       </div>
 
     </div>
 
     </div>
 
     <div class="collab-main-container">
 
     <div class="collab-main-container">
       <div class="safety-main-left">
+
       <div class="collab-main-left">
 
       </div>
 
       </div>
 
       <div class="collab-main-mid">
 
       <div class="collab-main-mid">
Line 203: Line 447:
 
       </p>
 
       </p>
 
       <p class="collab-text">
 
       <p class="collab-text">
         The first non-dutch iGEM contact we made was with the team from Lund, Sweden. Their university participated for the first time. We arranged a Skype meeting and shared to them our approach on different subjects. They had a lot of questions for us and we brainstormed with them about things like funding and time management. To help the other teams, we also filled in all the surveys that were on the iGEM website.
+
         TThe first non-dutch iGEM contact we made was with the team from Lund, Sweden. Their university participated for the first time. We arranged a Skype meeting and shared to them our approach on different subjects. They had a lot of questions for us and we brainstormed with them about things like funding and time management. Thanks team Lund!
 +
      </p>
 +
      <p class="collab-header">
 +
        TU Delft
 +
      </p>
 +
      <p class="collab-text">
 +
        In our early iGEM days we made contact with the iGEM team from Delft. They helped us out with questions we had about our wiki and in return we helped them out with some questions they had on bioinformatics. We have had a lot of contact with team Delft after this and would like to thank them for the pleasant collaboration.
 
       </p>
 
       </p>
 
       </div>
 
       </div>
Line 213: Line 463:
 
       </div>
 
       </div>
 
     </div>
 
     </div>
     <div class="safety-main-container">
+
     <div class="collab-main-container" id="light">
       <div class="safety-main-left">
+
       <div class="collab-main-left">
 
       </div>
 
       </div>
       <div class="safety-main-mid">
+
       <div class="collab-main-mid" id="meetup">
 
       <p class="collab-header">
 
       <p class="collab-header">
 
         Meet-up Wageningen
 
         Meet-up Wageningen
Line 235: Line 485:
 
         A month before the Giant Jamboree the team from KU Leuven organized a practice jamboree. During this event we got to practice our presentation and received feedback from the other teams. There were also some very inspiring speakers, that talked about being a scientist and the industrialization of products. It was a very informative afternoon and we are very grateful that the Leuven team set up this meeting!
 
         A month before the Giant Jamboree the team from KU Leuven organized a practice jamboree. During this event we got to practice our presentation and received feedback from the other teams. There were also some very inspiring speakers, that talked about being a scientist and the industrialization of products. It was a very informative afternoon and we are very grateful that the Leuven team set up this meeting!
 
       </p>
 
       </p>
      </div>
+
      <div class="slideshow-silver">
      <div class="vertical-text-container-outer">
+
        <div class="image-slideshow">
      <div class="vertical-text-container">
+
        <img class="slideshow-img-silver" src="https://static.igem.org/mediawiki/2017/5/59/Collab2.jpg">
         <p class="vertical-text">
+
        </img>
         </p>
+
        </div>
 +
        <div class="image-slideshow">
 +
        <img class="slideshow-img-silver" src="https://static.igem.org/mediawiki/2017/1/1b/Collab1.jpg">
 +
        </img>
 +
        </div>
 +
        <div class="image-slideshow">
 +
        <img class="slideshow-img-silver" src="https://static.igem.org/mediawiki/2017/d/db/Collab3.jpg">
 +
        </img>
 +
         </div>
 +
        <div class="image-slideshow">
 +
        <img class="slideshow-img-silver" src="https://static.igem.org/mediawiki/2017/6/6e/Collab6.jpg">
 +
        </img>
 +
        </div>
 +
        <div class="image-slideshow">
 +
        <img class="slideshow-img-silver" src="https://static.igem.org/mediawiki/2017/d/da/Collab5.jpg">
 +
        </img>
 +
        </div>
 +
        <a class="prev" onclick="plusSlides(-1)">
 +
        ❮
 +
        </a>
 +
        <a class="next" onclick="plusSlides(1)">
 +
        ❯
 +
         </a>
 
       </div>
 
       </div>
 
       </div>
 
       </div>
 
     </div>
 
     </div>
     <div class="collab-main-container">
+
     <div class="collab-main-container" id="survey">
       <div class="safety-main-left">
+
       <div class="collab-main-left">
 
       </div>
 
       </div>
 
       <div class="collab-main-mid">
 
       <div class="collab-main-mid">
Line 294: Line 566:
 
         </li>
 
         </li>
 
       </ul>
 
       </ul>
      </div>
 
      <div class="vertical-text-container-outer">
 
      <div class="vertical-text-container">
 
        <p class="vertical-text">
 
        </p>
 
      </div>
 
 
       </div>
 
       </div>
 
     </div>
 
     </div>
 +
    <script>
 +
      function displayFunction(clicked_id) {
 +
    var x = document.getElementById(clicked_id+"extension");
 +
    if (x.style.display === "none") {
 +
        x.style.display = "flex";
 +
        document.getElementById(clicked_id+"text").innerHTML = "&#9660;&ensp; Click here to hide the full collaboration";
 +
    } else {
 +
        x.style.display = "none";
 +
        document.getElementById(clicked_id+"text").innerHTML = "&#9654;&ensp; Click here to display the full collaboration";
 +
    }
 +
}
 +
    </script>
 +
    <script>
 +
      var slideIndex = 1;
 +
showSlides(slideIndex);
 +
 +
function plusSlides(n) {
 +
  showSlides(slideIndex += n);
 +
}
 +
 +
function currentSlide(n) {
 +
  showSlides(slideIndex = n);
 +
}
 +
 +
function showSlides(n) {
 +
  var i;
 +
  var slides = document.getElementsByClassName("image-slideshow");
 +
  if (n > slides.length) {slideIndex = 1}   
 +
  if (n < 1) {slideIndex = slides.length}
 +
  for (i = 0; i < slides.length; i++) {
 +
      slides[i].style.display = "none"; 
 +
  }
 +
  slides[slideIndex-1].style.display = "block"; 
 +
}
 +
    </script>
 
     </div>
 
     </div>
 
     <div class="footer">
 
     <div class="footer">
Line 355: Line 656:
 
     </div>
 
     </div>
 
     <div class="footer-col-right">
 
     <div class="footer-col-right">
       <a href="https://2017.igem.org/Team:Amsterdam/test/max/igem17.ams@gmail" target="_top">
+
       <a href="mailto:igem17.ams@gmail.com" target="_top">
       <img height="50px" src="https://static.igem.org/mediawiki/2017/a/a0/Email_logo.jpg">
+
       <img class="footer-sponsor-img" src="https://static.igem.org/mediawiki/2017/a/a0/Email_logo.jpg">
 
       </img>
 
       </img>
 
       </a>
 
       </a>
 
       <a href="https://www.facebook.com/igem2017amsterdam/" target="_blank">
 
       <a href="https://www.facebook.com/igem2017amsterdam/" target="_blank">
       <img height="50px" src="https://static.igem.org/mediawiki/2017/0/07/Facebook_logo.png">
+
       <img class="footer-sponsor-img" src="https://static.igem.org/mediawiki/2017/0/07/Facebook_logo.png">
 
       </img>
 
       </img>
 
       </a>
 
       </a>

Latest revision as of 22:23, 1 November 2017

Collaboration

Nobody can do science on their own, so collaborating is a necessity. We had a lot of contact with the other Dutch iGEM teams, via e-mail and at the different meet-ups we attended. Our biggest collaboration is with the team from the University of Nebraska-Lincoln, with whom we had a lot of contact in the past months. Furthermore we attended three international meet-ups, in Delft, Wageningen and Leuven, where we had a lot of good conversations about science, iGEM and life.

Collaborate

University of Nebraska-Lincoln

After the UNL iGEM sent around there iGEM survey, The Amsterdam team and the UNL iGEM team got into contact about combining their knowledge and explore the possibilities of a combined future application of their projects. In this collaboration, the UNL iGEM team and the Amsterdam iGEM team joined forces to come up with a way to reduce methane emissions. Methane emissions have a huge impact on climate change. iGEM team UNL and iGEM team Amsterdam explored the possibilities of feeding fumarate to cattle, in order to reduce methane emissions. We can conclude that fumarate seems a promising molecule for this application. However, since the literature about the possible effect of fumarate is not consistent, the physiology of cattle opposes some challenges and the maximum fumarate yields in certain organisms under our specific conditions are not yet defined. Actual empirical research must show if this promising route can lead to lower methane emissions and a more sustainable world!

Skyping with the University of Lund

TThe first non-dutch iGEM contact we made was with the team from Lund, Sweden. Their university participated for the first time. We arranged a Skype meeting and shared to them our approach on different subjects. They had a lot of questions for us and we brainstormed with them about things like funding and time management. Thanks team Lund!

TU Delft

In our early iGEM days we made contact with the iGEM team from Delft. They helped us out with questions we had about our wiki and in return we helped them out with some questions they had on bioinformatics. We have had a lot of contact with team Delft after this and would like to thank them for the pleasant collaboration.

Meet-up Wageningen

The Wageningen iGEM team organised a Benelux iGEM meet-up, here we had the opportunity to present our project to other teams for the first time. It was a nice initiator to think about how to present our project and to meet the other teams and learn about their projects. Thanks iGEM Wageningen!

Meet-up Delft

The iGEM team from the TUDelft hosted a European iGEM meet-up, in which we participated. During this conference three speakers talked about synthetic biology in their field of work. After that every team presented their posters to all the other teams. We enjoyed the day and learned a lot of the poster presentation, therefore we want to thank the TUDelft iGEM team!

Meet-up Leuven

A month before the Giant Jamboree the team from KU Leuven organized a practice jamboree. During this event we got to practice our presentation and received feedback from the other teams. There were also some very inspiring speakers, that talked about being a scientist and the industrialization of products. It was a very informative afternoon and we are very grateful that the Leuven team set up this meeting!

Survey iGEM teams

We did a lot of surveys to help as much iGEM teams with their research, most of them we found on the collaboration page of iGEM and we recieved the others via mail or Facebook:

  • Boston University Hardware
  • INSA UPS Toulouse France
  • University of Nebraska-Lincoln
  • City of London School UK
  • Pasteur Paris
  • Amazonas Brazil
  • Cardiff Whales
  • Ionis Paris
  • UNBC-Canada
  • Greece
  • BNU-China
  • University of Freiburg
  • Heidelberg University