Difference between revisions of "Team:Groningen/Collaborations"

 
(219 intermediate revisions by 8 users not shown)
Line 2: Line 2:
 
<html>
 
<html>
  
<style>
+
<body onscroll="stickyfunc()">
#single-col{width: 800px; padding-left: 2px; padding-right: 2px; margin:0 auto;}
+
  <div class="marginsnav">
#place-holder{width: 100px; height:100px; background-color:white;}
+
    <div class="main-col scrollcol">
  
</style>
+
<nav id="myScrollspy">
 +
  <ul class="nav">
 +
    <li class="active"><a href="#snavsciecol">Scientific collaborations</a></li>
 +
    <li><a href="#snavhp">Human practices</a></li>
 +
    <li><a href="#snavcolout">Outreach</a></li>
 +
    <li><a href="#snavcoloth">Others</a></li>
 +
  </ul>
 +
</nav>
  
<body>
+
<script>
 +
var scnavbar = document.getElementById("myScrollspy");
 +
var offsetsticky = scnavbar.offsetTop;
  
<div id="main-col">
+
function stickyfunc() {
<div id="single-col">
+
  if (window.pageYOffset >= 372 ) {
 +
    scnavbar.classList.add("sticky")
 +
  } else {
 +
    scnavbar.classList.remove("sticky");
 +
  }
 +
}
 +
 
 +
if (versionshitie != false) {
 +
  scnavbar.classList.add("sticky")
 +
}
 +
</script>
  
<h1 style="text-align:center;">Collaborations</h1>
+
<h1 style="text-align:left;">Collaborations</h1>
<iframe src="https://www.google.com/maps/d/u/2/embed?mid=1QOc6F8I6pHvY2SnqGvZv3fcWWz4" width="640" height="480"></iframe>
+
  
 
<p class="left">
 
<p class="left">
Science is rarely a one (wo)man job and usually requires people with different backgrounds to work together to solve the challenges encountered. iGEM is no different. To encompass this spirit the iGEM 2017 Groningen team strives to work together with multiple teams on different aspect of our project and hopefully further strengthen connections.
+
Science is rarely a one (wo)man job and usually requires people with different backgrounds to work together to solve the challenges encountered. iGEM is no different. To encompass this spirit the iGEM 2017 Groningen team strives to work together with multiple teams on different aspect of our project and hopefully further strengthen connections within the iGEM community.
 
</p>
 
</p>
  
<button onclick="accordion('acc1')" class="w3-button w3-block"><h3>Scientific collaborations</h3></button>
+
<br/>
<div id="acc1" class="w3-hide" style="text-align:left;">
+
<ol>
+
<li>
+
To further develop and establish Lactococcus lactis as a chassis in iGEM we collaborated with the IGEM team of Sao Paulo. We  sent them protocols since we have a lot of in house experience with working on lactis.
+
</li>
+
<li>
+
To help the Nottingham team we tested their E.coi RFP fluorescence in our lab to provide an external control.
+
</li>
+
<li>
+
NAWI-Graz: Our friends from Austria are developing a bioelectronic interface controlled by bacterial GFP-expression. They have developed a software to validate part of their experiments. iGEM Groningen has worked together with them to design mazes and therefore improve the functionality and identify flaws in the design.
+
</li>
+
</ol>
+
</div>
+
 
<hr class="small">
 
<hr class="small">
 +
<h5 id="snavsciecol">Scientific collaborations</h5>
 +
  <img class="imglabh" style="width: 15%; display:inline-block; margin-left:25px; float:right; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/thumb/6/64/Unott.jpg/337px-Unott.jpg" alt="Packages from the Nottingham team">
  
 +
<ul style="list-style: none;">
 +
  <li>
 +
  <img class="imglabh" style="width:5%; margin-top:-15px;" src="https://static.igem.org/mediawiki/2017/c/c0/Rsz_sao_paulo.jpg" alt="Boston collaboration">To further develop and establish <i>L. lactis</i> as a chassis in iGEM we collaborated with the IGEM team of Sao Paulo. We  sent them protocols since we have a lot of in house experience with working on lactis.
 +
  </li>
 +
  <li>
 +
    <br><img class="imglabh" style="width:5%; margin-top:-15px;" src="https://static.igem.org/mediawiki/2017/4/47/Rsz_nottingham.jpg" alt="Nottingham collaboration">To help the Nottingham team we tested their <i>E.coli</i> RFP fluorescence in our lab to provide an external control. They sent us a <a href="https://2017.igem.org/File:Nottinham_protocol.docx">protocol</a> along with their cells, and we did the testing and sent them our <a href="https://2017.igem.org/File:Nottingham_collaboration_results.xlsx">results.</a>
 +
  </li>
 +
  <li style="margin-bottom:30px;">
 +
    <br><img class="imglabh" style="width:5%; margin-top:-15px;" src="https://static.igem.org/mediawiki/2017/0/08/Rsz_graz.jpg" alt="Nawi Graz collaboration">NAWI-Graz: Our friends from Austria are developing a bioelectronic interface controlled by bacterial GFP-expression. They have developed a software to validate part of their experiments. iGEM Groningen has worked together with them to design mazes and therefore improve the functionality and identify flaws in the design.
 +
  </li>
 +
</ul>
 +
 
 +
<img class="imglabh" style="width: 45%; display:inline-block; margin-left:25px; margin-top:10px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/4/4b/Nawi-_Graz_collaboration_maze_game_2.png" alt="Nawi_graz collaboration">
 +
<img class="imglabh" style="width: 45%; display:inline-block; margin-left:10px; margin-top:10px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/5/50/Nawi_graz_collaboration_maze_game_1.png " alt="Nawi_graz collaboration">
  
<button onclick="accordion('acc2')" class="w3-button w3-block"><h3>Human practices</h3></button>
+
<br/>
<div id="acc2" class="w3-hide" style="text-align:left;">
+
<hr class="small">
<ol>
+
<li>
+
Virtual meet up Vilnius-Lithuania, Abu Dhabi (with follow up discussion)
+
We presented our project designs to each other and critically debated their feasibility as well as implementation of the final product. This helped us gain insight into possible experimental flaws. Abu Dhabi is also working on designing a cartridge, so their engineering advice was appreciated and contributed to improving our cartridge. We held a follow-up discussion to update on the progress achieved and get advice on the challenges met. We had a few issues with cloning and got some help that enabled us to get our construct from team Vilnius. We hoped our input also improved on their design.
+
</li>
+
<li>
+
Virtual meet up – ethics, Oslo, Graz, Zurich, Lund, Upsala. Team Uppsala moderated a discussion together with Oslo, Graz, Zurich, and Lund about the ethical implications of our projects. We tried to respond to the following questions:
+
  
<ol>
+
<h5 id="snavhp">Human practices</h5>
<li>
+
<ul style="list-style: none;">
Uncontrolled Release. Can we anticipate how our Genetically Engineered Machine (GEM) would behave if released? What would be ideal conditions to grow and could they potentially be met? Can we anticipate any interactions with any form of wildlife? What would be ideal conditions to grow and could they potentially be met?
+
  <img class="imglabh" style="width:30%; float:right; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/3/3b/Abu_dhabi_vilnius_lithuania_collaboration_.png" alt="Vilnius-Lithuania and Abu Dhabi collaboration.">
</li>
+
  <img class="imglabh" style="width:5%; margin-top:-15px;" src="https://static.igem.org/mediawiki/2017/3/3c/Rsz_vilnius.jpg" alt="Vilinius collaboration">
<li>
+
  <img class="imglabh" style="width:5%; margin-top:-15px;" src="https://static.igem.org/mediawiki/2017/3/3d/Rsz_abu_dhabi.jpg" alt="Abu Dhabi collaboration">Virtual meet up Vilnius-Lithuania, Abu Dhabi (with follow up discussion)
Misuse. Can we think some steps ahead and imagine a potentially harmful usage with our open-source GEM?
+
We presented our project designs to each other and critically debated their feasibility as well as implementation of the final product. This helped us gain insight into possible experimental flaws. Abu Dhabi is also working on designing a cartridge, so their engineering advice was appreciated and contributed to improving our cartridge. We held a follow-up discussion to update on the progress achieved and get advice on the challenges met. We had a few issues with cloning and got some help that enabled us to get our construct from team Vilnius. We hoped our input also improved on their design.  </li>
</li>
+
  <p>
</ol>
+
<img class="imglabh" style="width:5%; margin-top:-15px;" src="https://static.igem.org/mediawiki/2017/b/bd/Rsz_oslo.jpg" alt="Oslo collaboration">
The whole conversation was live streamed and can be found <a href="https://www.youtube.com/watch?v=TOuFtJZxDf0">here</a>
+
<img class="imglabh" style="width:5%; margin-top:-15px;" src="https://static.igem.org/mediawiki/2017/0/08/Rsz_graz.jpg" alt="Graz collaboration">
</li>
+
<img class="imglabh" style="width:5%; margin-top:-15px;" src="https://static.igem.org/mediawiki/2017/d/d6/Rsz_zurich.jpg" alt="Zurich collaboration">
<li>
+
<img class="imglabh" style="width:5%; margin-top:-15px;" src="https://static.igem.org/mediawiki/2017/f/f9/Rsz_lund.jpg" alt="Lund collaboration">
BENELUX meetup
+
<img class="imglabh" style="width:5%; margin-top:-15px;" src="https://static.igem.org/mediawiki/2017/0/09/Rsz_upsalla.jpg" alt="Upsalla collaboration">
<ol>
+
Virtual meet up – ethics, Oslo, Graz, Zurich, Lund, Uppsala. Team Uppsala moderated a discussion together with Oslo, Graz, Zurich, and Lund about the ethical implications of our projects. The whole conversation was live streamed and can be found <a href="http://www.youtube.com/watch?v=TOuFtJZxDf0">here</a>. We tried to respond to the following questions:
<li>
+
    <ol>
The BENELUX teams were invited to meet and present their ideas and receive critical feedback from other teams, experts in the field and an iGEM HQ representative. Teams also participated in workshops to immerse ourselves in the shareholders perspectives and debate safety issues. The meeting was hosted by the <a href="https://www.facebook.com/pg/iGEMWageningen/photos/?tab=album&album_id=1418519451527561">Wageningen team</a>.
+
      <li> Uncontrolled Release. Can we anticipate how our Genetically Engineered Machine (GEM) would behave if released? What would be ideal conditions to grow and could they potentially be met? Can we anticipate any interactions with any form of wildlife? What would be ideal conditions to grow and could they potentially be met?
</li>
+
      </li>
</ol>
+
      <li> Misuse. Can we think some steps ahead and imagine a potentially harmful usage with our open-source GEM?
</li>
+
      </li>
<li>
+
    </ol>
EUROPEAN meetup
+
  </li>
The European iGEM meet up for the Netherlands was held in Delft this year. The meet up started with a talk by Cees Dekker, a well known physicist. It was quite interesting to hear about the common ground between physics and biology in his talk.
+
  <li><img class="imglabh" style="width:5%; margin-right:7px;" src="https://static.igem.org/mediawiki/2017/7/74/Rsz_benelux.png" alt="Official Benelux flag.">Benelux meetup  
After the break we had the talk from Denis Murphy, he is highly involved in palm oil. Palm oil is used a lot for cosmetics in richer countries, and for sustenance in poorer countries. He expanded on a specific application for genetic engineering for making sustainable palm oil plantations.
+
<p>The Benelux teams were invited to meet and present their ideas at the <a href="https://www.facebook.com/pg/iGEMWageningen/photos/?tab=album&album_id=1418519451527561">Benelux meetup</a> and receive critical feedback from other teams, experts in the field and an iGEM HQ representative. Teams also participated in workshops to immerse ourselves in the shareholders perspectives and debate safety issues. The meeting was hosted by the Wageningen team.
The main event of the day was of course the poster presentations of all the iGEM teams themselves. We walked around a lot, talking to pretty much every team at least once. It was very nice to see all the Dutch teams again here after we had met them during the Dutch iGEM meet up in Wageningen. During all this we handed out our 3D printed phages to the teams too.
+
</p>
The last part of the day was a BBQ with some drinks. We left together with some of the other teams and talked more about how our respective projects were going.
+
<img class="imglabh" style="width: 15%; display:inline-block; margin-left:25px; margin-top:10px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/thumb/d/d6/Benelux.jpeg/459px-Benelux.jpeg" alt="Benelux meetup in Wageningen">
</li>
+
<img class="imglabh" style="width: 12%; display:inline-block; margin-left:10px; margin-top:10px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/thumb/d/db/Wageningen1.jpg/337px-Wageningen1.jpg" alt="Benelux meetup in Wageningen">
<li>
+
<img class="imglabh" style="width: 12%; display:inline-block; margin-left:10px; margin-top:10px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/thumb/a/a8/Reizen.jpg/338px-Reizen.jpg" alt="Benelux meetup in Wageningen">
Tolerance Photo Challenge Technion Israel
+
<img class="imglabh" style="width: 18%; display:inline-block; margin-left:10px; margin-top:10px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/thumb/7/7e/Reizen2.jpg/539px-Reizen2.jpg" alt="Benelux meetup in Wageningen">
To highlight the diversity and tolerance in our team we participated in the Tolerance photo challenge in conjunction with Technion, Isreal (photo)
+
<img class="imglabh" style="width: 30%; display:inline-block; margin-left:10px; margin-top:10px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/thumb/5/5a/Benelux_meetup.jpg/800px-Benelux_meetup.jpg" alt="photo: team Wageningen">
</li>
+
  </li>
<li>
+
  <li>
Little snazzy man (Flat Stanly) – Caroll High school Caroll High school got inspired for their collaboration by the book “Flat Stanley by Jeff Brown. A bulletin board falls on Stanley, he survives but is now flat. His altered form comes with some perks though, such as being able to slip under doors or being mailed to California to meet his friends. Caroll HS also made a flat Stanley and mailed it to us, this time being a microbe. We welcomed it to our lab and made it an honorary team member.
+
<img class="imglabh" style="width:5%; margin-right:7px;" src="https://static.igem.org/mediawiki/2017/d/d8/Rsz_eu_flag.jpg" alt="EU flag.">European meetup
</li>
+
 
<li>
+
<img class="imglabh" style="width: 20%; float:right; display:inline-block; margin-top:50px; margin-right:10px;" src="https://static.igem.org/mediawiki/2017/thumb/6/6d/Eumeetup.jpeg/429px-Eumeetup.jpeg" alt="Listening to the talk at the European meetup in Delft.">
Online meet-up about fermentation factories – SCUT-FSE- China
+
 
</li>
+
<img class="imglabh" style="width: 30%; float:right; display:inline-block; margin:10px; margin-top:50px;" src="https://static.igem.org/mediawiki/2017/thumb/e/eb/WhatsApp_Image_2017-10-26_at_18.13.41.jpeg/800px-WhatsApp_Image_2017-10-26_at_18.13.41.jpeg" alt="iGEM Groningen enjoying lunch and the sun at the European meetup.">
</ol>
+
 
</div>
+
<p>The European iGEM meetup was held in Delft this year. The meet up started with a talk by Cees Dekker, a well-known physicist. It was quite interesting to hear about the common ground between physics and biology.
 +
After the break a lecture was given by Denis Murphy, he is involved in palm oil research. Palm oil is used a lot for cosmetics in richer countries, and for sustenance in poorer countries. He expanded on a specific application for genetic engineering for making sustainable palm oil plantations.
 +
The main event of the day was, of course, the poster presentations of all the iGEM teams. We walked around a lot, talking to pretty much every team at least once. It was very pleasant to see all the Dutch teams again here after we had previously met them during the Dutch iGEM meet up in Wageningen. During the entire event we "infected" other teams with our 3D printed bacteriophages. The last part of the day consisted of a BBQ with some drinks. We left together with some of the other teams and talked more about how our respective projects were progressing.</p>
 +
 
 +
 
 +
<video src="https://static.igem.org/mediawiki/2017/8/8d/European_iGEM_Meetup_2017_-_Aftermovie_-720p-.mp4#t=1" controls preload="metadata" style="width:560px; height:auto; margin-left:11%"></video>
 +
 
 +
<!--<iframe width="560" height="315" src="https://www.youtube.com/embed/0o2q27tK-JE?rel=0" style="margin-left:22%;" frameborder="0" allowfullscreen></iframe>-->
 +
  </li>
 +
</ul>
 +
<br>
 +
 
 +
<ul style="list-style: none;">
 +
 
 +
  <li><img class="imglabh" style="width:5%;" src="https://static.igem.org/mediawiki/2017/a/ae/Rsz_technion.jpg" alt="Technion collaboration">Tolerance Photo Challenge - Technion Israel
 +
  <p>To highlight the diversity and tolerance in our team we participated in the Tolerance photo challenge in conjunction with Technion, Isreal.
 +
  <img class="imglabh" style="width:30%; margin:10px; display:block; float:right;" src="https://static.igem.org/mediawiki/2017/7/73/K-20170921-WA0006.jpg" alt="Tolerance collaboration"></p>
 +
  </li>
 +
 
 +
  <li><img class="imglabh" style="width:5%;" src="https://static.igem.org/mediawiki/2017/7/74/Rsz_1caroll_hs.jpg" alt="Caroll collaboration">Little snazzy man (Flat Stanly)–Caroll High school
 +
  <p>Caroll High school got inspired for their collaboration by the book “Flat Stanley by Jeff Brown. A bulletin board falls on Stanley, he survives but is now flat. His altered form comes with some perks though, such as being able to slip under doors or being able to be mailed to California to meet his friends. Caroll HS also made a flat Stanley and mailed it to us, this time being a microbe. We welcomed it to our lab and made it an honorary team member.
 +
  <img class="imglabh" style="width:30%; margin:10px; display:block; float:right;" src="https://static.igem.org/mediawiki/2017/7/7c/K-20170921-WA0007.jpg" alt="Little Snazzy Man"></p>
 +
  </li>
 +
  <li><img class="imglabh" style="width:5%;" src="https://static.igem.org/mediawiki/2017/b/b9/Rsz_scut_fse_china.jpg" alt="China collaboration">Online meet-up about fermentation factories – SCUT-FSE- China
 +
<p>We skyped with the team of the South China University of Technology about our respective projects. They are working to improve fermentation processes as well, using CRISPR in <i>E.coli</i> to defend against bacteriophages. We shared some insights about mutual problems we might encounter and the potential CRISPR offers to fermentation industries affected by phage infections.</p>
 +
  </li>
 +
</ul>
 +
 
 +
<br/>
 
<hr class="small">
 
<hr class="small">
  
 +
<h5 id="snavcolout">Outreach</h5>
  
<button onclick="accordion('acc3')" class="w3-button w3-block"><h3>Outreach</h3></button>
+
<ul style="list-style: none;">
<div id="acc3" class="w3-hide" style="text-align:left;">
+
<li>
<ol>
+
    <img class="imglabh" style="width:5%; margin-top:-15px;" src="https://static.igem.org/mediawiki/2017/c/cc/Rsz_franconia.jpg" alt="Franconia collaboration">We developed our own card game and shared it with Team Franconia & in return also evaluated their card game. Their input helped us improve our design so that the game is a bit more fun and engaging. We hope our input also contributed to improving their game balance.</li>
<li>
+
<li>
We developed our own card game and will shared it with Team Franconia & in return also evaluated their card game. We will also assist them with the QR stand game. (58., 15.)
+
    <br><img class="imglabh" style="width:5%; margin-top:-15px;" src="https://static.igem.org/mediawiki/2017/3/32/Rsz_mit.jpg" alt="MIT collaboration">We were curious about the history of IGEM and have collaborated with the MIT team to visualize the development of tracks, teams, topics etc. MIT has provided us with a file stating these and Groningen has <a href="https://2017.igem.org/Team:Groningen/carlosinsert" target="_blank">analyzed and visualized the content</a>. This provides insight into how the competition has changed over the years, information about shifting interests and emerging trends and technologies. <li>
 +
<li>
 +
    <br><img class="imglabh" style="width:5%; margin-top:-15px;" src="https://static.igem.org/mediawiki/2017/1/10/Rsz_dusseldorf.jpg" alt="Dusseldorf collaboration">To further strengthen the bond between different IGEM teams we also send & received post cards from different teams initiated by team Düsseldorf. The postcards should quickly highlight the main idea of the respective projects. We received a vast variety of post card designs and had a lot of fun reading through the other teams’ projects and designs.
 
</li>
 
</li>
<li>
+
<img class="imglabh" style="width:45%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/8/87/Postcardscollab.jpg" alt="iGEM postcards">
We were curious about the history of IGEM and have collaborated with the MIT team to visualize the development of tracks, teams, topics etc. MIT has provided us with a file stating these and Groningen has <a href="file:///C:/Users/fmeie/OneDrive/Documents/IGEM/Collaborations/Igem%20history.html">analyzed and visualized the content</a>. This provides insight into how the competition has changed over the years, information about shifting interests and emerging trends and technologies.
+
 
  
 
</li>
 
</li>
<li>
+
</ul>
To further strengthen the bond between different IGEM teams we also send & received post cards from different teams initiated by team Düsseldorf. The postcards should quickly highlight the main idea of the respective projects. We received a vast variety of post card designs and had a lot of fun reading through the other teams’ projects and designs. (1.)
+
 
</li>
+
 
</ol>
+
<br/>
</div>
+
 
<hr class="small">
 
<hr class="small">
  
<button onclick="accordion('acc4')" class="w3-button w3-block"><h3>Others</h3></button>
+
<h5 id="snavcoloth">Others</h5>
<div id="acc4" class="w3-hide" style="text-align:left;">
+
 
We also participated in the surveys of the following teams to help them gather some data on their projects problems:
 
We also participated in the surveys of the following teams to help them gather some data on their projects problems:
  
<ol>
+
<ul style="list-style: none;">
<li>Microfluidics survey – Boston university</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/8/89/Boston.jpg" alt="Boston collaboration"> Microfluidics survey – Boston university</li>
<li>Survey about Cholera – INSA-UPS France</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/7/73/Unsa_ups.jpg" alt="Insa UPS collaboration"> Survey about Cholera – INSA-UPS France</li>
<li>Methane production -  Nebraska- Lincoln</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/2/2f/Lincoln.jpg" alt="Nebraska collaboration"> Methane production -  Nebraska- Lincoln</li>
<li>Air pollution – Pasteur Paris</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/1/1b/Pasteur_Paris.jpg" alt="iGEM postcards"> Air pollution – Pasteur Paris</li>
<li>Biological Material transport survey – Team Amazonas, Brazil</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/1/11/Amazonas.jpg" alt="Amazonas collaboration"> Biological Material transport survey – Team Amazonas, Brazil</li>
<li>Health care & liver cancer – Team Brit</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/a/ae/Groningen-Brit_collab.jpg" alt="Brit collaboration "> Health care & liver cancer – Team Brit</li>
<li>Genetic engineering & medicine – Team Cardiff</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/f/f5/Cardiff.jpg" alt="Cardiff collaboration"> Genetic engineering & medicine – Team Cardiff</li>
<li>Tell us about your chassis</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/7/79/Rsz_madras.jpg" alt="iGEM madras collaboration"> Tell us about your chassis– Team IIT Madras</li>
<li>Insulin accessibility – Syndney Australia</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/6/67/Sydney.jpg" alt="Sydney collaboration"> Insulin accessibility – Syndney Australia</li>
<li>GMO perception study - Sup’Biotech, Paris, France</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/0/09/Rsz_sup_biotech_paris.jpg" alt="iGEM postcards"> GMO perception study - Sup’Biotech, Paris, France</li>
<li>Heavy metal toxicity – DEI Agra, India</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/0/09/DEI_Agra.jpg" alt="Dei Agra collaboration"> Heavy metal toxicity – DEI Agra, India</li>
<li>Antibiotically resistant bacteria - UNBC- Canada</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/c/c7/UNBC.jpg" alt="UNBC collaboration"> Antibiotically resistant bacteria - UNBC- Canada</li>
<li>Diabetics & Psicose - Evry, France</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/7/7f/Ervy.jpg" alt="Evry collaboration"> Diabetics & Psicose - Evry, France</li>
<li>Perspectives on Treatments for Illnesses Survey -Columbia University</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/c/c0/Columbia.jpg" alt="Columbia collaboration"> Perspectives on Treatments for Illnesses Survey -Columbia University</li>
<li>Lead Contamination in YOUR Drinking Water? - Team WPI Worcester</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/4/4e/Worcester.jpg" alt="Worcester collaboration"> Lead Contamination in YOUR Drinking Water? - Team WPI Worcester</li>
<li>Survey on Colorectal Cancer - Team Worldshaper-Wuhan</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/5/57/Wuhan.jpg" alt="Wuhan collaboration"> Survey on Colorectal Cancer - Team Worldshaper-Wuhan</li>
<li>CRISPR along the iGEM - Team Amazonas Brazil</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/1/11/Amazonas.jpg" alt="Amazonas collaboration"> CRISPR along the iGEM - Team Amazonas Brazil</li>
<li>Directed Evolution and Artificial Intelligence Survey - Team Heidelberg</li>
+
<li><img class="imglabh" style="width:5%; margin-left:13px; margin-top:5px; margin-bottom:10px;" src="https://static.igem.org/mediawiki/2017/6/6a/Heidelberg.jpg" alt="Wuhan collaboration"><style="margin-bottom:10px;">Directed Evolution and Artificial Intelligence Survey - Team Heidelberg</li>
</ol>
+
</ul>
</div>
+
<hr>
<hr class="small">
+
<br>
  
 +
<center>
 +
<a class="button" style="text-decoration: none; color:white; margin-bottom:30px;" href="https://2017.igem.org/Team:Groningen/Team">Next: Team</a>
 +
</center>
  
</div></div> <!-- -col -->
+
</div> <!-- main-col -->
 +
</div> <!-- marginsnav -->
  
 
<div class="footer">
 
<div class="footer">
<img style="width: 100%;" src="https://static.igem.org/mediawiki/2017/b/b5/Banner.jpg" alt="Sponsors">
+
<img id="bannerimg" usemap="#imagemap_sponsors" style="width: 100%;" src="https://static.igem.org/mediawiki/2017/b/b5/Banner.jpg" alt="Sponsors">
 
</div>
 
</div>
 +
 +
  
 
</body>
 
</body>
Line 150: Line 199:
 
     }
 
     }
 
}
 
}
 +
//modal trigger
 +
var modal = document.getElementById('myModal');
 +
var images = document.getElementsByClassName("imglab");
 +
for(var i = 0; i < images.length; i++){
 +
    var img = images[i];
 +
    var modalImg = document.getElementById("img01");
 +
    var captionText = document.getElementById("caption");
 +
    img.onclick = function(){
 +
        modal.style.display = "block";
 +
        modalImg.src = this.src;
 +
        modalImg.alt = this.alt;
 +
        captionText.innerHTML = this.alt;
 +
    }
 +
}
 +
//Get click and close
 +
modal.addEventListener('click',function(){
 +
this.style.display="none";
 +
})
 +
//modal trigger
 +
var modalh = document.getElementById('myModalh');
 +
var imagesh = document.getElementsByClassName("imglabh");
 +
for(var i = 0; i < imagesh.length; i++){
 +
    var imgh = imagesh[i];
 +
    var modalImgh = document.getElementById("img01h");
 +
    var captionTexth = document.getElementById("captionh");
 +
    imgh.onclick = function(){
 +
        modalh.style.display = "block";
 +
        modalImgh.src = this.src;
 +
        modalImgh.alt = this.alt;
 +
        captionTexth.innerHTML = this.alt;
 +
    }
 +
}
 +
//Get click and close
 +
modalh.addEventListener('click',function(){
 +
this.style.display="none";
 +
})
 
</script>
 
</script>
 
 
</html>
 
</html>
iGEM term analysis: Seeing the big figure
 
Carlos Urzua, in colaboration with the iGEM team Groningen and iGEM team MIT
 
 
September 27, 2017
 
 
INTRODUCTION
 
The iGEM competition brings into contact many student groups that worked on a research project for one year. Because this competition started over 10 years ago it would be interesting to investigate the changes in research ideas or lab equipment that have taken place since then. Fortunately, one of the requirements for the competition is to upload to the web a description of the project (also called the wiki). The links to each wiki are neatly organized on the official iGEM page they are a word frequency analysis feasible. Also useful visualization of the results of the analysis would allow more people to get an idea of the evolution of iGEM projects. This idea was concieved by the MIT team and was proposed as a collaboration in the official iGEM page (Colaboration number #26). We, at the Groningen team decided to collaborate with the MIT team by doing this analysis.
 
 
METHODS
 
 
Web Scraping
 
 
To conduct a word frequencty analysis, the text of each iGEM team web description must be easily accessible and organized on a table. To achive this, the iGEM team of MIT web scraped the text of each team using the official archive of wikis available in the iGEM web page (<>). They structured this data into a CSV file where the team name, supervisor name, project title, year of the project and wiki text were columns of the data table.
 
 
Data Cleaning
 
 
The original csv file could not be read from file due to some conficts in the interpretation of quoted text. The problem is that some regions of text are interpreted as part of the csv structure and commas in this region are interpreted as field separators. This problematic text belonged to the descriptions of the wiki that were the object of this analysis. We removed all lines of text that did not have 6 comma separated fields and then all that did not have an url on the team url field (Team_Info_Page). This may have removed a lot of information from some teams wikis.
 
 
Word frequency analysis
 
 
To find out how the iGEM projects have evolved over the years we first conducted a word frequency analysis per year (2008-2015) using VOSvisualizer (<>). VOSvisualizer is a software tool designed in Leiden University to visualize bibliometric networks. One of the modes of analysis is word co-ocurrence which can be done on any kind of text. We downloaded VOSviewer 1.6.5 and conducted the analysis using the command line call:
 
 
java -jar /path/to/VOSviewer.jar -corpus 2008_abstracts.txt -counting_method 2 -min_n_occurrences 2
 
 
This call makes VOS viewer do a word co-ocurrence analysis with full counting of ocurrences (counting_method), for all words that are repeated at least twice. The corpus used was a file that had all abstracts for that specific year. VOSviewer generates a co-ocurrence network based on the frequencies of the single words or larger strings (terms) that are found repeated in the corpus. VOSviewer also generates a tab-delimited “map” file that specifies the link strength, number of links and number of ocurrences for each node (terms) in this network.
 
 
Word frequency interpretation
 
 
We consolidated all map files into one table (map table) and specified in a new column the year of each entry. Therefore if a term was captured in the analysis on more than one year it would have more than one entry in the map table. We subseted from the table words that had 3 or more entries (were important on more thatn 3 years). Because the popularity of the iGEM competition is increasing, recent years have more teams than older years. Therefore, a term that ocurrs for example, 3 times per abstract may appear to increase in ocurrence if the number of ocurrences is not corrected by the number of teams per year. There fore we preformed a correction were the each ocurrence was divided by the number of abstracts of that year. After this normalization we calculated a score for each term.
 
 
Score = O_first - O_last
 
 
Where O_last, O_first is the number of nomalized ocurrences in the last or first year available for that term respectively. This score aims to capture the terms that are more frequently used in recent times (positive) and the terms that are falling in use in recent times (negative)
 
 
We manually labeled the terms with the most negative and most positive scores based on their likely origin; if they represented a part of the lab equimpent or lab techniques (lab_equipment), or an idea behind the project (idea) or if they had unspecific meaning (term). Some terms did not originate from the description but from the references section (reference) or were found in the headers, titles and subtitles (header). Some terms were frequent because they are part of the default text instructions for the wiki and they were labeled as (artifacts).
 
 
## Loading required package: RColorBrewer
 
RESULTS
 
 
Using web-scraping, we obtained the text of the wikis of iGEM teams that participated during the periof between 2008-2015. Some wikis scraped text showed a warning that stated “no text in this page”.
 
 
##    year Percent_of_accessible_wikis
 
## 1: 2008                  0.9333333
 
## 2: 2009                  0.9361702
 
## 3: 2010                  0.9367089
 
## 4: 2011                  0.8924731
 
## 5: 2012                  0.7127660
 
## 6: 2013                  0.7606178
 
## 7: 2014                  0.7828746
 
## 8: 2015                  0.9966102
 
 
 
Barplots of teams per year and average word lenght of each wiki per year after removing wikis that were not usable as described below.
 
 
The majority of the wikis have a menu which is usually the only part of the text that was captured (low word count). because most wikis have this format, this restricts the ability of this analysis to detect representative co-ocurrence word trends. We defined as usable wiki texts that did not contain the template text or provided a warning of no text. This was done so that the analysis could at least detect changes in the short descriptions that sometimes appear in this section and of the headers that are used in the teams across the years.
 
 
## `stat_bin()` using `bins = 30`. Pick better value with `binwidth`.
 
 
 
Histogram of word counts per wiki, wikis with no content as described above are the ones that were removed from analysis. These wikis have the template text or are otherwise not accessible. Note that still a lot of wikis have few words, this is because they contain a menu bar with a short description of the project which is the only text that was scraped for them.
 
 
Using VOSviewer we conducted a word co-ocurrence analysis for the usable wiki texts. We consolidated the results of these analysis in one table and created a score to allow the comparison of the per-year analysis results. Using these scores we estimated which terms appear more frequently on recent years and which terms have fallen in use. We manually classified these terms into distict categories for description.
 
 
General Terms:
 
 
Wordcloud of terms that have not a particular meaning. In red terms that are falling in use and in green terms that are increasing in use. Color intensity is proportional to the magnitude of increase in ocurrence.
 
 
plot_term(ranked_table, "term")
 
 
 
##                  label          V1 type
 
##  1:            picture -0.103482587 term
 
##  2:            chimera -0.077935727 term
 
##  3:                core -0.074642464 term
 
##  4:        instruction -0.072160149 term
 
##  5:            identity -0.066180827 term
 
##  6:            comment -0.057370737 term
 
##  7:              suffix -0.052004582 term
 
##  8:            effector -0.044196151 term
 
##  9:              class -0.041309131 term
 
## 10:              server -0.035285430 term
 
## 11:            channel -0.029767828 term
 
## 12:          preference  0.009507446 term
 
## 13:    promoter region  0.023331618 term
 
## 14:        target gene  0.023331618 term
 
## 15:            building  0.023995734 term
 
## 16:              child  0.027341439 term
 
## 17:    room temperature  0.027887789 term
 
## 18:              trend  0.030126002 term
 
## 19: signal transduction  0.032716882 term
 
## 20:      essential gene  0.032877416 term
 
## 21:                note  0.033281867 term
 
## 22:                name  0.034879725 term
 
## 23:      identification  0.039199255 term
 
## 24:    positive control  0.050434513 term
 
## 25:        supernatant  0.063455386 term
 
## 26:            student  0.065406644 term
 
## 27:            template  0.065856063 term
 
## 28:              liquid  0.071983561 term
 
## 29:                fig  0.099595454 term
 
## 30:        cooperation  0.100620732 term
 
## 31:            dilution  0.105257969 term
 
## 32:          absorption  0.155942978 term
 
## 33:            choosing  0.176512651 term
 
## 34:              member  0.221177118 term
 
## 35:                min  0.229298572 term
 
## 36:              please  0.282752902 term
 
## 37:                fig2  0.352017381 term
 
##                  label          V1 type
 
In these wordclouds we can observe that images on the wiki were called “picture” in the past and are now called (“fig” and “fig2”). The word “identity” is now used instead in athe form “identification”. We also see that words like (“core” and “effector”) have fallen in use, which may reflect that the engineered systems do not revolve around a single switch and are now composed of many parts.
 
 
We see that in more recent wikis the description of the steps has increased because of the increase in use of terms like (“min”, “absorption”,“diluton”,“supernatant”,“positive control”). We also see that the team nature of the project is now more evident on the description due to the increase in terms like (“member”,“student”,“cooperation”). Of note, not all ocurrences of “member” refer people, but sometimes to molecules. The word “class” is used where today we would use “type”, strangely we did not observe a corresponding increase in the use of this last word.
 
 
Headers:
 
 
Wordcloud of terms found on headers. In red terms that are falling in use and in green terms that are increasing in use. Color intensity is proportional to the magnitude of increase in ocurrence.
 
 
plot_term(ranked_table, "header")
 
 
 
## Warning in wordcloud(words = table$label, freq = table$V1, min.freq = 0, :
 
## project description could not be fit on page. It will not be plotted.
 
 
 
##                  label          V1  type
 
##  1:            abstract -0.04674724 header
 
##  2:        lab notebook -0.03098511 header
 
##  3:            wet lab -0.02992061 header
 
##  4:        presentation  0.02799503 header
 
##  5:              video  0.05037244 header
 
##  6:          background  0.06541059 header
 
##  7:      human practice  0.10108820 header
 
##  8:          motivation  0.11092917 header
 
##  9:              safety  0.13195630 header
 
## 10:            overview  0.25757294 header
 
## 11:            summary  0.26840472 header
 
## 12:        achievement  0.44037758 header
 
## 13:          conclusion  0.54873998 header
 
## 14:        attribution  0.61334210 header
 
## 15:      collaboration  0.64255121 header
 
## 16:            notebook  0.81083178 header
 
## 17: project description  0.93870267 header
 
## 18:                team  1.04760679 header
 
## 19:          reference  1.05142768 header
 
In this explaratory analysis we could also observe that in the past Wikis were composed mainly of different sections than today. We observed a descrease in the use of the headers (“abstract”,“lab notebook”, “wet lab”). This may be because iGEM standardized the structure of the Wikis at some point during this period. Now, wikis contain sections like (“summary”,“overview”,“notebook”,“collaboration”), that belong tot his new structure. Of note because of this changes, we observed a lot of new terms appear because of the presence of references in the wikis.
 
 
Lab materials
 
 
Wordcloud of terms that describe materials and lab techniques. In red terms that are falling in use and in green terms that are increasing in use. Color intensity is proportional to the magnitude of increase in ocurrence.
 
 
plot_term(ranked_table, "lab_material")
 
 
 
##              label          V1        type
 
##  1:            tube -0.09696846 lab_material
 
##  2:            cfp -0.06369999 lab_material
 
##  3:        ethanol -0.04845361 lab_material
 
##  4:            ptet -0.03882682 lab_material
 
##  5:    nitric oxide  0.02458822 lab_material
 
##  6:            srna  0.03134258 lab_material
 
##  7:        agarose  0.03319848 lab_material
 
##  8:  photoreceptor  0.03358163 lab_material
 
##  9:        miniprep  0.03361266 lab_material
 
## 10:    dna fragment  0.03366501 lab_material
 
## 11:            egg  0.03851462 lab_material
 
## 12:      well plate  0.03862454 lab_material
 
## 13:            ompr  0.03905397 lab_material
 
## 14:      water bath  0.03916822 lab_material
 
## 15:        alcohol  0.04478585 lab_material
 
## 16:        plastic  0.04833906 lab_material
 
## 17:        sds page  0.05034140 lab_material
 
## 18:      red light  0.05203520 lab_material
 
## 19:          insert  0.05429553 lab_material
 
## 20: electrophoresis  0.06556030 lab_material
 
## 21:            heme  0.06722533 lab_material
 
## 22:            psti  0.09506518 lab_material
 
## 23:          ecori  0.11747362 lab_material
 
## 24:            ice  0.12801002 lab_material
 
## 25:          mirna  0.13877752 lab_material
 
## 26:          buffer  0.17349472 lab_material
 
## 27:          flask  0.20145872 lab_material
 
## 28:          column  0.26294227 lab_material
 
##              label          V1        type
 
Terms reflecting the lab materials show the evident switch of iGEM teams to genome engineering. We can see a clear increase in the use of restriction enzymes, electrophoresis and DNA purification columns, miRNA and sRNA. This change may also explain why “tube” is now less used. Another explanation is that a “tube” has been replaced by more high throughput containers like “well plate”. We also observe that “ethanol” is now mentioned as “alcohol”. We also observe an increase in use of fluerescence techniques (“red ligth”). Surprisingly we did not pick up an increase in the use of RFP.
 
 
References
 
 
Wordcloud of terms that originate from the reference section. In green terms that have increased in use. Color intensity is proportional to the magnitude of increase in ocurrence.
 
 
plot_wordcloud(ranked_table[type=="references"], "Greens")
 
 
 
ranked_table[type=="references"]
 
##                    label        V1      type
 
##  1:        microbiology 0.03401614 references
 
##  2:              august 0.03916822 references
 
##  3:                chem 0.03935444 references
 
##  4:                chen 0.04405060 references
 
##  5:              science 0.04405941 references
 
##  6:              america 0.04421113 references
 
##  7:                  liu 0.04979773 references
 
##  8:    national academy 0.04979773 references
 
##  9:                wang 0.04995826 references
 
## 10: biological chemistry 0.05592800 references
 
## 11:                zhang 0.05841031 references
 
## 12:                  web 0.06615182 references
 
## 13:                  vol 0.06753569 references
 
## 14:                june 0.07268777 references
 
## 15:        biochemistry 0.07855369 references
 
## 16:              journal 0.08951890 references
 
## 17:              center 0.16769088 references
 
Terms that are found in the references reflect the origin of the research literature of iGEM teams as can be observed in the terms like (“biochemistry”,“microbiology”,“biological chemistry”,“chem”) that originate from article titles and journal names. The most common journals are also recognizable (“science”, “national academy”). Unexpectedly, because atuomatic bibliographic tools record the date of citation we can observe that most teams conduct the research for the wiki during June and August.
 
 
LIMITATIONS
 
 
The limitations of this analysis is the filters that VOSviewer may have that prevent some words like “type” from being considered relevant. Also this analysis can pick up only words that are consistently used in the same way. This is because we did not use a dictionary of synonyms for the analysis with VOSviewer which can increase the resolution of the results. This may explain why we do not pick up commonly used fluorescence proteins like RFP but we do pick up restriction enzymes like ecoRI.
 
 
Another limitation is that the web scraping could not access the text of wikies that were hidden behind a network of links or that were not stored as plain text. Because most of the wikies have this format this severely restricts the analysis. In a future analysis can improve on this step.
 

Latest revision as of 03:04, 2 November 2017


Collaborations

Science is rarely a one (wo)man job and usually requires people with different backgrounds to work together to solve the challenges encountered. iGEM is no different. To encompass this spirit the iGEM 2017 Groningen team strives to work together with multiple teams on different aspect of our project and hopefully further strengthen connections within the iGEM community.



Scientific collaborations
Packages from the Nottingham team
  • Boston collaborationTo further develop and establish L. lactis as a chassis in iGEM we collaborated with the IGEM team of Sao Paulo. We sent them protocols since we have a lot of in house experience with working on lactis.

  • Nottingham collaborationTo help the Nottingham team we tested their E.coli RFP fluorescence in our lab to provide an external control. They sent us a protocol along with their cells, and we did the testing and sent them our results.

  • Nawi Graz collaborationNAWI-Graz: Our friends from Austria are developing a bioelectronic interface controlled by bacterial GFP-expression. They have developed a software to validate part of their experiments. iGEM Groningen has worked together with them to design mazes and therefore improve the functionality and identify flaws in the design.
Nawi_graz collaboration Nawi_graz collaboration

Human practices
    Vilnius-Lithuania and Abu Dhabi collaboration. Vilinius collaboration Abu Dhabi collaborationVirtual meet up Vilnius-Lithuania, Abu Dhabi (with follow up discussion) We presented our project designs to each other and critically debated their feasibility as well as implementation of the final product. This helped us gain insight into possible experimental flaws. Abu Dhabi is also working on designing a cartridge, so their engineering advice was appreciated and contributed to improving our cartridge. We held a follow-up discussion to update on the progress achieved and get advice on the challenges met. We had a few issues with cloning and got some help that enabled us to get our construct from team Vilnius. We hoped our input also improved on their design.

    Oslo collaboration Graz collaboration Zurich collaboration Lund collaboration Upsalla collaboration Virtual meet up – ethics, Oslo, Graz, Zurich, Lund, Uppsala. Team Uppsala moderated a discussion together with Oslo, Graz, Zurich, and Lund about the ethical implications of our projects. The whole conversation was live streamed and can be found here. We tried to respond to the following questions:

    1. Uncontrolled Release. Can we anticipate how our Genetically Engineered Machine (GEM) would behave if released? What would be ideal conditions to grow and could they potentially be met? Can we anticipate any interactions with any form of wildlife? What would be ideal conditions to grow and could they potentially be met?
    2. Misuse. Can we think some steps ahead and imagine a potentially harmful usage with our open-source GEM?
  • Official Benelux flag.Benelux meetup

    The Benelux teams were invited to meet and present their ideas at the Benelux meetup and receive critical feedback from other teams, experts in the field and an iGEM HQ representative. Teams also participated in workshops to immerse ourselves in the shareholders perspectives and debate safety issues. The meeting was hosted by the Wageningen team.

    Benelux meetup in Wageningen Benelux meetup in Wageningen Benelux meetup in Wageningen Benelux meetup in Wageningen photo: team Wageningen
  • EU flag.European meetup Listening to the talk at the European meetup in Delft. iGEM Groningen enjoying lunch and the sun at the European meetup.

    The European iGEM meetup was held in Delft this year. The meet up started with a talk by Cees Dekker, a well-known physicist. It was quite interesting to hear about the common ground between physics and biology. After the break a lecture was given by Denis Murphy, he is involved in palm oil research. Palm oil is used a lot for cosmetics in richer countries, and for sustenance in poorer countries. He expanded on a specific application for genetic engineering for making sustainable palm oil plantations. The main event of the day was, of course, the poster presentations of all the iGEM teams. We walked around a lot, talking to pretty much every team at least once. It was very pleasant to see all the Dutch teams again here after we had previously met them during the Dutch iGEM meet up in Wageningen. During the entire event we "infected" other teams with our 3D printed bacteriophages. The last part of the day consisted of a BBQ with some drinks. We left together with some of the other teams and talked more about how our respective projects were progressing.


  • Technion collaborationTolerance Photo Challenge - Technion Israel

    To highlight the diversity and tolerance in our team we participated in the Tolerance photo challenge in conjunction with Technion, Isreal. Tolerance collaboration

  • Caroll collaborationLittle snazzy man (Flat Stanly)–Caroll High school

    Caroll High school got inspired for their collaboration by the book “Flat Stanley by Jeff Brown. A bulletin board falls on Stanley, he survives but is now flat. His altered form comes with some perks though, such as being able to slip under doors or being able to be mailed to California to meet his friends. Caroll HS also made a flat Stanley and mailed it to us, this time being a microbe. We welcomed it to our lab and made it an honorary team member. Little Snazzy Man

  • China collaborationOnline meet-up about fermentation factories – SCUT-FSE- China

    We skyped with the team of the South China University of Technology about our respective projects. They are working to improve fermentation processes as well, using CRISPR in E.coli to defend against bacteriophages. We shared some insights about mutual problems we might encounter and the potential CRISPR offers to fermentation industries affected by phage infections.



Outreach
  • Franconia collaborationWe developed our own card game and shared it with Team Franconia & in return also evaluated their card game. Their input helped us improve our design so that the game is a bit more fun and engaging. We hope our input also contributed to improving their game balance.

  • MIT collaborationWe were curious about the history of IGEM and have collaborated with the MIT team to visualize the development of tracks, teams, topics etc. MIT has provided us with a file stating these and Groningen has analyzed and visualized the content. This provides insight into how the competition has changed over the years, information about shifting interests and emerging trends and technologies.

  • Dusseldorf collaborationTo further strengthen the bond between different IGEM teams we also send & received post cards from different teams initiated by team Düsseldorf. The postcards should quickly highlight the main idea of the respective projects. We received a vast variety of post card designs and had a lot of fun reading through the other teams’ projects and designs.
  • iGEM postcards


Others
We also participated in the surveys of the following teams to help them gather some data on their projects problems:
  • Boston collaboration Microfluidics survey – Boston university
  • Insa UPS collaboration Survey about Cholera – INSA-UPS France
  • Nebraska collaboration Methane production - Nebraska- Lincoln
  • iGEM postcards Air pollution – Pasteur Paris
  • Amazonas collaboration Biological Material transport survey – Team Amazonas, Brazil
  • Brit collaboration Health care & liver cancer – Team Brit
  • Cardiff collaboration Genetic engineering & medicine – Team Cardiff
  • iGEM madras collaboration Tell us about your chassis– Team IIT Madras
  • Sydney collaboration Insulin accessibility – Syndney Australia
  • iGEM postcards GMO perception study - Sup’Biotech, Paris, France
  • Dei Agra collaboration Heavy metal toxicity – DEI Agra, India
  • UNBC collaboration Antibiotically resistant bacteria - UNBC- Canada
  • Evry collaboration Diabetics & Psicose - Evry, France
  • Columbia collaboration Perspectives on Treatments for Illnesses Survey -Columbia University
  • Worcester collaboration Lead Contamination in YOUR Drinking Water? - Team WPI Worcester
  • Wuhan collaboration Survey on Colorectal Cancer - Team Worldshaper-Wuhan
  • Amazonas collaboration CRISPR along the iGEM - Team Amazonas Brazil
  • Wuhan collaborationDirected Evolution and Artificial Intelligence Survey - Team Heidelberg


Next: Team