Difference between revisions of "Team:Tuebingen/Collaborations"

Line 2: Line 2:
  
 
<html>
 
<html>
−
 
+
<br>
−
<h2> Collaborations</h2>
+
−
<h4> Our collaboration with Freiburg </h4>
+
−
<p> Content is coming soon! </p>
+
 
<p>
 
<p>
−
Sharing and collaboration are core values of iGEM. We encourage you to reach out and work with other teams on difficult problems that you can more easily solve together.
+
On Mai 2nd, we invited the iGEM Team Freiburg to visit our institute, introduce their project DiaChip (See http://freigem.org/en/our-project) and talk about our project “Crellumination”. We were highly exicted to listen to their project, which could provide a powerful tool for clinical diagnostics. We are happy to contribute to their project by providing them with our Spy-Tag, which they will use to bind pathogen-specific antigens to the surface of their diagnostic chip.
 
</p>
 
</p>
−
 
+
<p>
−
<div class="highlightBox">
+
On August 11th, Team Darmstadt joined our laboratory to talk about our projects and exchange some thoughts and ideas in line with their Labsurfing project. We are glad we were a part of their big journey across different iGEM labs in Europe!
−
 
+
</p>
−
<h4> Which other teams can we work with? </h4>
+
<p>
−
<p>  
+
Moreover, we attended at the iGEM Meetup Germany in Marburg to get insights into a huge number of other iGEM projects.
−
You can work with any other team in the competition, including software, hardware, high school and other tracks. You can also work with non-iGEM research groups, but they do not count towards the <a hreef="https://2015.igem.org/Judging/Awards#Medals">iGEM team collaboration gold medal criterion</a>.
+
</p>
 +
<p>
 +
Our most important collaboration was the one with the iGEM Team Valencia, as we both work with the Dronpa protein in the iGEM competition 2015. This collaboration was very profitable for both teams as we were able to improve each others projects.
 +
</p>
 +
<p>
 +
When we first got in touch, the iGEM Team Valencia had not yet been able to activate and deactivate Dronpa. We had previously stumbled upon the same problem and managed to solve it using higher intensity lasers. We recommended them to use similar contraptions.
 
</p>
 
</p>
−
 
 
<p>
 
<p>
−
In order to meet the gold medal criteria on helping another team, you must complete this page and detail the nature of your collaboration with another iGEM team.
+
Since both teams had little experience with the modelling of biological systems we discussed our ideas and thoughts regarding the modelling of the Dronpa activation with Team Valencia.
 +
Team Valencia attempted to implement the systems equations of their biological circuit with ‘pure/vanilla’ matlab. Our own project however required probabilistic elements due to the discrete nature of the population encoded sensor information. From our discussion with Team Valencia, we concluded that SimBiology was not the optimal tool for our task however team Valencia might profit from it. We profited insofar as our understanding of certain modelling elements was improved as well as mutually reviewed our implementations.
 
</p>
 
</p>
−
</div>
 
−
 
 
<p>
 
<p>
−
Here are some suggestions for projects you could work on with other teams:
+
This exchange of ideas particularly improved the mathematical formulations, because the peer review process provided a necessary sanity check, and we could train how we should present the theoretic part to people that are unfamiliar with our projects.
 
</p>
 
</p>
−
 
−
<ul>
 
−
<li> Improve the function of another team's BioBrick Part or Device</li>
 
−
<li> Characterize another team's part </li>
 
−
<li> Debug a construct </li>
 
−
<li> Model or simulating another team's system </li>
 
−
<li> Test another team's software</li>
 
−
<li> Help build and test another team's hardware project</li>
 
−
<li> Mentor a high-school team</li>
 
−
</ul>
 
−
 
−
 
  
 
</div>
 
</div>
 
</html>
 
</html>

Revision as of 18:10, 18 September 2015

<
>


On Mai 2nd, we invited the iGEM Team Freiburg to visit our institute, introduce their project DiaChip (See http://freigem.org/en/our-project) and talk about our project “Crellumination”. We were highly exicted to listen to their project, which could provide a powerful tool for clinical diagnostics. We are happy to contribute to their project by providing them with our Spy-Tag, which they will use to bind pathogen-specific antigens to the surface of their diagnostic chip.

On August 11th, Team Darmstadt joined our laboratory to talk about our projects and exchange some thoughts and ideas in line with their Labsurfing project. We are glad we were a part of their big journey across different iGEM labs in Europe!

Moreover, we attended at the iGEM Meetup Germany in Marburg to get insights into a huge number of other iGEM projects.

Our most important collaboration was the one with the iGEM Team Valencia, as we both work with the Dronpa protein in the iGEM competition 2015. This collaboration was very profitable for both teams as we were able to improve each others projects.

When we first got in touch, the iGEM Team Valencia had not yet been able to activate and deactivate Dronpa. We had previously stumbled upon the same problem and managed to solve it using higher intensity lasers. We recommended them to use similar contraptions.

Since both teams had little experience with the modelling of biological systems we discussed our ideas and thoughts regarding the modelling of the Dronpa activation with Team Valencia. Team Valencia attempted to implement the systems equations of their biological circuit with ‘pure/vanilla’ matlab. Our own project however required probabilistic elements due to the discrete nature of the population encoded sensor information. From our discussion with Team Valencia, we concluded that SimBiology was not the optimal tool for our task however team Valencia might profit from it. We profited insofar as our understanding of certain modelling elements was improved as well as mutually reviewed our implementations.

This exchange of ideas particularly improved the mathematical formulations, because the peer review process provided a necessary sanity check, and we could train how we should present the theoretic part to people that are unfamiliar with our projects.