Team:Wisconsin-Madison/whatisigem

From 2011.igem.org

(Difference between revisions)
 
(5 intermediate revisions not shown)
Line 157: Line 157:
<a href="https://2011.igem.org/Team:Wisconsin-Madison">Main</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison">Main</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison/whatisigem">What is iGEM?</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison/whatisigem">What is iGEM?</a>
 +
<a href="https://2011.igem.org/Team:Wisconsin-Madison/ca">Contributions & Attributions</a>
</div>
</div>
</li>
</li>
Line 166: Line 167:
                 <a href="https://2011.igem.org/Team:Wisconsin-Madison/directedevolution">Directed Evolution</a>
                 <a href="https://2011.igem.org/Team:Wisconsin-Madison/directedevolution">Directed Evolution</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison/bmc">Microcompartment</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison/bmc">Microcompartment</a>
 +
                <a href="https://2011.igem.org/Team:Wisconsin-Madison/parts">Parts</a>
</div>
</div>
</li>
</li>
Line 179: Line 181:
<div id="m4" onmouseover="mcancelclosetime()" onmouseout="mclosetime()">
<div id="m4" onmouseover="mcancelclosetime()" onmouseout="mclosetime()">
<a href="https://2011.igem.org/Team:Wisconsin-Madison/protocols">Protocols</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison/protocols">Protocols</a>
-
<a href="https://2011.igem.org/Team:Wisconsin-Madison/calender">Calender</a>
+
<a href="https://2011.igem.org/Team:Wisconsin-Madison/calender">Calendar</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison/references">References</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison/references">References</a>
</div>
</div>
Line 188: Line 190:
<a href="https://2011.igem.org/Team:Wisconsin-Madison/reuposterSession">REU Poster Session</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison/reuposterSession">REU Poster Session</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison/socialmedia">Social Media</a>
<a href="https://2011.igem.org/Team:Wisconsin-Madison/socialmedia">Social Media</a>
-
<a href="https://2011.igem.org/Team:Wisconsin-Madison/presentations">Presentations</a>
 
</div>
</div>
</li>
</li>
<li><a href="https://2011.igem.org/Team:Wisconsin-Madison/safety" onmouseover="mopen('m6')" onmouseout="mclosetime()">Safety</a>
<li><a href="https://2011.igem.org/Team:Wisconsin-Madison/safety" onmouseover="mopen('m6')" onmouseout="mclosetime()">Safety</a>
 +
<div id="m6" onmouseover="mcancelclosetime()" onmouseout="mclosetime()">
 +
<a href="https://2011.igem.org/Team:Wisconsin-Madison/humanpractice">Human Practice</a>
 +
</div>
</li>
</li>
</ul>
</ul>
</center>
</center>
-
 
+
<center>
<center>
     <img src="https://static.igem.org/mediawiki/2011/a/aa/Logo_v2.2.jpg"; style="position:absolute; left:-10px; top:-10px"/>
     <img src="https://static.igem.org/mediawiki/2011/a/aa/Logo_v2.2.jpg"; style="position:absolute; left:-10px; top:-10px"/>
</center>
</center>
 +
Line 211: Line 216:
<strong><font size="3">
<strong><font size="3">
What is iGEM?
What is iGEM?
-
</font></strong><p><br>
+
</font></strong><br>
iGEM is a <a href="https://2011.igem.org/Team:Wisconsin-Madison/syntheticbiology">synthetic biology</a> competition and stands for Internationally Genetically Engineered Machines. It began as a friendly competition between 10 MIT teams in 2004, and has since grown to over <a href="https://igem.org/Team_List?year=2011">130 teams</a> in 2010 from all different countries around the globe. This year even more teams are anticipated, and there will be regional competitions held before the annual international jamboree held at MIT in the fall.
iGEM is a <a href="https://2011.igem.org/Team:Wisconsin-Madison/syntheticbiology">synthetic biology</a> competition and stands for Internationally Genetically Engineered Machines. It began as a friendly competition between 10 MIT teams in 2004, and has since grown to over <a href="https://igem.org/Team_List?year=2011">130 teams</a> in 2010 from all different countries around the globe. This year even more teams are anticipated, and there will be regional competitions held before the annual international jamboree held at MIT in the fall.
<br><br>
<br><br>
-
iGEM revolves around two main ideas: the use of <a href="https://2011.igem.org/Team:Wisconsin-Madison/biobricks">BioBricks</a> and the <a href="https://2011.igem.org/Team:Wisconsin-Madison/registry">registry</a>. Biobricks are pieces of DNA that have been given a similar structure and that code for something useful. They can be big or small and may contain one or many individual pieces of useful information all packaged into one coherent piece. These biobricks all contain the <a href="https://2011.igem.org/Team:Wisconsin-Madison/cutsites">same interface</a> and thus can be copied and pasted into new DNA with ease.
+
iGEM revolves around two main ideas: the use of <a href="https://2011.igem.org/Team:Wisconsin-Madison/biobricks">BioBricks</a> and the <a href="http://partsregistry.org/Main_Page">registry</a>. Biobricks are pieces of DNA that have been given a similar structure and that code for something useful. They can be big or small and may contain one or many individual pieces of useful information all packaged into one coherent piece. These biobricks all contain the same interface and thus can be copied and pasted into new DNA with ease.
<br><br>
<br><br>
Each new part, once confirmed, is sent to MIT and physically stored there in the registry. Any other iGEM team can order any Biobrick from the Registry for use in their project, and get physical copies that are easily cultured and can be quickly used, without having to be manufactured by the teams. This open source structure speeds up the research progress significantly and makes great strides in the future of synthetic biology.
Each new part, once confirmed, is sent to MIT and physically stored there in the registry. Any other iGEM team can order any Biobrick from the Registry for use in their project, and get physical copies that are easily cultured and can be quickly used, without having to be manufactured by the teams. This open source structure speeds up the research progress significantly and makes great strides in the future of synthetic biology.
<p><br>
<p><br>
-
Read more about iGEM at the official site <a href="https://igem.org/Main_Page">here</a>
+
Read more about iGEM at the official site <a href="https://igem.org/Main_Page">here</a>.

Latest revision as of 22:58, 28 September 2011









What is iGEM?
iGEM is a synthetic biology competition and stands for Internationally Genetically Engineered Machines. It began as a friendly competition between 10 MIT teams in 2004, and has since grown to over 130 teams in 2010 from all different countries around the globe. This year even more teams are anticipated, and there will be regional competitions held before the annual international jamboree held at MIT in the fall.

iGEM revolves around two main ideas: the use of BioBricks and the registry. Biobricks are pieces of DNA that have been given a similar structure and that code for something useful. They can be big or small and may contain one or many individual pieces of useful information all packaged into one coherent piece. These biobricks all contain the same interface and thus can be copied and pasted into new DNA with ease.

Each new part, once confirmed, is sent to MIT and physically stored there in the registry. Any other iGEM team can order any Biobrick from the Registry for use in their project, and get physical copies that are easily cultured and can be quickly used, without having to be manufactured by the teams. This open source structure speeds up the research progress significantly and makes great strides in the future of synthetic biology.


Read more about iGEM at the official site here.