Difference between revisions of "Team:Hannover/Achievements"
| Line 47: | Line 47: | ||
<div class="panel-body"> | <div class="panel-body"> | ||
<ul> | <ul> | ||
| − | <li>We officially registered for the iGEM competition and worked hard on our project. We got to meet new people from all over the word and are looking forward to the Jamboree. <span class="glyphicon glyphicon- | + | <li>We officially registered for the iGEM competition and worked hard on our project. We got to meet new people from all over the word and are looking forward to the Jamboree. <span class="glyphicon glyphicon-check"></span></li> |
| − | <li>We met all conditions on the requirement page. <span class="glyphicon glyphicon- | + | <li>We met all conditions on the requirement page. <span class="glyphicon glyphicon-check"></span></li> |
| − | <li>To distinguish <a href="https://2016.igem.org/Team:Hannover/Team">our work</a> from work done by others, we created <a href="https://2016.igem.org/Team:Hannover/Attributions">contributors page</a> on our team wiki. <span class="glyphicon glyphicon- | + | <li>To distinguish <a href="https://2016.igem.org/Team:Hannover/Team">our work</a> from work done by others, we created <a href="https://2016.igem.org/Team:Hannover/Attributions">contributors page</a> on our team wiki. <span class="glyphicon glyphicon-check"></span></li> |
| − | <li>We documented the new <a href="http://parts.igem.org/Part:BBa_K2075004">standard BioBrick</a> that we used for our project and then submitted it to the iGEM Registry. <span class="glyphicon glyphicon- | + | <li>We documented the new <a href="http://parts.igem.org/Part:BBa_K2075004">standard BioBrick</a> that we used for our project and then submitted it to the iGEM Registry. <span class="glyphicon glyphicon-check"></span></li> |
</ul> | </ul> | ||
</div> | </div> | ||
| Line 63: | Line 63: | ||
<div class="panel-body"> | <div class="panel-body"> | ||
<ul> | <ul> | ||
| − | <li>We experimentally confirmed that our <a href="https://2016.igem.org/Team:Hannover/Description">TALebot</a> is not only more stable when compared to a linear TAL-effector, but also fully functional and therefore a huge step in providing scientists with a TAL-effector that works in vitro. <span class="glyphicon glyphicon- | + | <li>We experimentally confirmed that our <a href="https://2016.igem.org/Team:Hannover/Description">TALebot</a> is not only more stable when compared to a linear TAL-effector, but also fully functional and therefore a huge step in providing scientists with a TAL-effector that works in vitro. <span class="glyphicon glyphicon-check"></span></li> |
| − | <li>We tried to <a href="https://2016.igem.org/Team:Hannover/Collaborations">help other iGEM teams</a> by providing them with our Phabricator-platform and designed other software tools to improve lab work and participation in the competition. <span class="glyphicon glyphicon- | + | <li>We tried to <a href="https://2016.igem.org/Team:Hannover/Collaborations">help other iGEM teams</a> by providing them with our Phabricator-platform and designed other software tools to improve lab work and participation in the competition. <span class="glyphicon glyphicon-check"></span></li> |
| − | <li>To inform students about our lab work, the ideas behind it and discuss ethical questions in the field of synthetic biology, we visited schools and lectures in the University. <span class="glyphicon glyphicon- | + | <li>To inform students about our lab work, the ideas behind it and discuss ethical questions in the field of synthetic biology, we visited schools and lectures in the University. <span class="glyphicon glyphicon-check"></span></li> |
</ul> | </ul> | ||
</div> | </div> | ||
| Line 78: | Line 78: | ||
<div class="panel-body"> | <div class="panel-body"> | ||
<ul> | <ul> | ||
| − | <li>After conducting a <a href="https://2016.igem.org/Team:Hannover/HP/Gold">survey</a> about TALEs and synthetic biology, we integrated the results into our project and tried to simplify the use of TALEs. We stabilized them and storage of TALEs is now easy and cheap.<span class="glyphicon glyphicon- | + | <li>After conducting a <a href="https://2016.igem.org/Team:Hannover/HP/Gold">survey</a> about TALEs and synthetic biology, we integrated the results into our project and tried to simplify the use of TALEs. We stabilized them and storage of TALEs is now easy and cheap.<span class="glyphicon glyphicon-check"></span></li> |
| − | <li>Using existing knowledge from the team in Heidelberg in 2014 and their project <a href="">"Ring of Fire"</a>, we developed the experiments for our TALebots and optimized their vector to use it in the lab. <span class="glyphicon glyphicon- | + | <li>Using existing knowledge from the team in Heidelberg in 2014 and their project <a href="">"Ring of Fire"</a>, we developed the experiments for our TALebots and optimized their vector to use it in the lab. <span class="glyphicon glyphicon-check"></span></li> |
| − | <li>By conducting stability tests, we tried to demonstrate <a href="https://2016.igem.org/Team:Hannover/Demonstrate">functional proof</a> of our project "TALebots". <span class="glyphicon glyphicon- | + | <li>By conducting stability tests, we tried to demonstrate <a href="https://2016.igem.org/Team:Hannover/Demonstrate">functional proof</a> of our project "TALebots". <span class="glyphicon glyphicon-check"></span></li> |
| − | <li>We tried showing that TALebots work under real world conditions by designing <a href="https://2016.igem.org/Team:Hannover/Proof">microarrays</a> and binding our TALEs to GFP. You can find out detailed information about this special part of our project on our project page.<span class="glyphicon glyphicon- | + | <li>We tried showing that TALebots work under real world conditions by designing <a href="https://2016.igem.org/Team:Hannover/Proof">microarrays</a> and binding our TALEs to GFP. You can find out detailed information about this special part of our project on our project page.<span class="glyphicon glyphicon-check"></span></li> |
</ul> | </ul> | ||
</div> | </div> | ||
Revision as of 05:10, 19 October 2016
Achievements
- We officially registered for the iGEM competition and worked hard on our project. We got to meet new people from all over the word and are looking forward to the Jamboree.
- We met all conditions on the requirement page.
- To distinguish our work from work done by others, we created contributors page on our team wiki.
- We documented the new standard BioBrick that we used for our project and then submitted it to the iGEM Registry.
- We experimentally confirmed that our TALebot is not only more stable when compared to a linear TAL-effector, but also fully functional and therefore a huge step in providing scientists with a TAL-effector that works in vitro.
- We tried to help other iGEM teams by providing them with our Phabricator-platform and designed other software tools to improve lab work and participation in the competition.
- To inform students about our lab work, the ideas behind it and discuss ethical questions in the field of synthetic biology, we visited schools and lectures in the University.
- After conducting a survey about TALEs and synthetic biology, we integrated the results into our project and tried to simplify the use of TALEs. We stabilized them and storage of TALEs is now easy and cheap.
- Using existing knowledge from the team in Heidelberg in 2014 and their project "Ring of Fire", we developed the experiments for our TALebots and optimized their vector to use it in the lab.
- By conducting stability tests, we tried to demonstrate functional proof of our project "TALebots".
- We tried showing that TALebots work under real world conditions by designing microarrays and binding our TALEs to GFP. You can find out detailed information about this special part of our project on our project page.
