Difference between revisions of "Team:Arizona State/Collaborations"

 
(15 intermediate revisions by 3 users not shown)
Line 3: Line 3:
 
<div class="container">
 
<div class="container">
 
<h1>Collaboration</h1>
 
<h1>Collaboration</h1>
−
<h4>Throughout the year, we contacted several iGEM teams to collaborate on our projects. We reached out to high school teams, which may not have the resources to sequence plasmids or parts. The two teams that we collaborated with were the Urban Tundra team from Edmonton and Broad Run Northern VA from Baltimore.</h4>
+
<p>Throughout the year, we contacted several iGEM teams to collaborate on our projects. We reached out to high school teams, which may not have the resources to sequence plasmids or parts. The two teams that we collaborated with were the Urban Tundra team from Edmonton and Broad Run Northern VA from Baltimore. We helped characterize their parts by sequencing plasmids and aligning them with predicted sequences.</p>
 +
 
 +
<div class = "container">
 
<h2>Urban Tundra</h2>
 
<h2>Urban Tundra</h2>
−
<p>We collaborated with the Urban Tundra iGEM team from Edmonton, Canada. The team was unable to sequence the plasmid that they designed, so the ASU team offered to sequence their plasmid via the Core Laboratory at ASU. The information was collected and sent back to the Urban Tundra team. </p>
+
<p>We collaborated with the Urban Tundra iGEM team from Edmonton, Canada. The team was unable to sequence the plasmid that they designed, so the ASU team offered to sequence their plasmid via the Core Laboratory at ASU. The sequence information was collected, aligned using Benchling.com, and then the Urban Tundra team was sent instructions on how to view the shared data. </p>
−
<h2>Broad Run Northern VA</h2>
+
      <center><img src="https://static.igem.org/mediawiki/2016/archive/a/a1/20161009090812%21T--UrbanTundra_Edmonton--sliderTeam.jpg" height=400px></center><br>
−
<p>We also collaborated with the Broad Run Northern VA team from Baltimore, MD. Their team was also unable to sequence two of the plasmids that they constructed. The ASU team helped sequence those two plasmids via the Core Laboratory at ASU. Both sequences were collected and sent back to the Baltimore team. </p>
+
<p>The following plasmids were generated, one with malE SP gene (SP+) and one without (SP-). The aim of this project was to cleanse toxins from Martian soil through the bioreaction of between Chlorite Dismutase and chlorite ions. Sequencing helped them to identify a mutation in one of their constructs! </p>
 +
<div class="row">
 +
            <div class="col-sm-6 center">
 +
<h4>CPB38(Cld SP+)</h4>
 +
<img height="300px" src="https://static.igem.org/mediawiki/2016/f/f3/T--Arizona_State--collabposplasmid.png">
 
</div>
 
</div>
−
 
+
            <div class="col-sm-6 center">
−
 
+
<h4>CPB38(Cld SP-)</h4>
−
 
+
<img height="300px" src="https://static.igem.org/mediawiki/2016/e/e5/T--Arizona_State--collabnegplasmid.png">
−
 
+
−
 
+
−
<div class="column full_size">
+
−
 
+
−
 
+
−
<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.
+
−
</p>
+
 
</div>
 
</div>
−
 
−
<div class="column half_size">
 
−
 
−
<h4> Which other teams can we work with? </h4>
 
−
<p>
 
−
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 iGEM team collaboration silver medal criterion.
 
−
</p>
 
−
 
−
<p>
 
−
In order to meet the silver medal criteria on helping another team, you must complete this page and detail the nature of your collaboration with another iGEM team.
 
−
</p>
 
−
 
 
</div>
 
</div>
−
 
+
<hr>
−
 
+
</hr>
−
 
+
−
<div class="column half_size">
+
−
<p>
+
−
Here are some suggestions for projects you could work on with other teams:
+
−
</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>
−
 
+
<h3>SP+ Plasmid Sequence</h3>
−
 
+
      <center><img src="https://static.igem.org/mediawiki/2016/d/d0/T--Arizona_State--collabpossequence.png" height=500px></center><br>
 +
<h3>SP- Plasmid Sequence</h3>
 +
      <center><img src="https://static.igem.org/mediawiki/2016/a/a2/T--Arizona_State--collabnegsequence.png" height=500px></center><br>
 
</html>
 
</html>
 
{{Arizona_State_Footer}}
 
{{Arizona_State_Footer}}

Latest revision as of 17:51, 19 October 2016

Collaboration

Throughout the year, we contacted several iGEM teams to collaborate on our projects. We reached out to high school teams, which may not have the resources to sequence plasmids or parts. The two teams that we collaborated with were the Urban Tundra team from Edmonton and Broad Run Northern VA from Baltimore. We helped characterize their parts by sequencing plasmids and aligning them with predicted sequences.

Urban Tundra

We collaborated with the Urban Tundra iGEM team from Edmonton, Canada. The team was unable to sequence the plasmid that they designed, so the ASU team offered to sequence their plasmid via the Core Laboratory at ASU. The sequence information was collected, aligned using Benchling.com, and then the Urban Tundra team was sent instructions on how to view the shared data.


The following plasmids were generated, one with malE SP gene (SP+) and one without (SP-). The aim of this project was to cleanse toxins from Martian soil through the bioreaction of between Chlorite Dismutase and chlorite ions. Sequencing helped them to identify a mutation in one of their constructs!

CPB38(Cld SP+)

CPB38(Cld SP-)

SP+ Plasmid Sequence


SP- Plasmid Sequence


twitter wordpress
© 2016 ASU iGEM