Team:HUST-Innovators

From 2014.igem.org

(Difference between revisions)
Line 235: Line 235:
     }
     }
     function clean(type) {
     function clean(type) {
 +
        document.getElementById("0").style.display = "none";
         document.getElementById("1").style.display = "none";
         document.getElementById("1").style.display = "none";
         document.getElementById("2").style.display = "none";
         document.getElementById("2").style.display = "none";
Line 240: Line 241:
         document.getElementById("4").style.display = "none";
         document.getElementById("4").style.display = "none";
         document.getElementById("5").style.display = "none";
         document.getElementById("5").style.display = "none";
 +
        document.getElementById("6").style.display = "none";
         // document.getElementById(type).style.display = "block";
         // document.getElementById(type).style.display = "block";
 +
    }
 +
    function change(Name) {
 +
        document.getElementById("detail_home").style.display = "none";
 +
        document.getElementById("SeqevolutionforSB").style.display = "none";
 +
        document.getElementById("3rd").style.display = "none";
 +
        document.getElementById("3rdWhat").style.display = "none";
 +
        document.getElementById("3rdWhy").style.display = "none";
 +
        document.getElementById("OurProj").style.display = "none";
 +
        document.getElementById("NewModel").style.display = "none";
 +
        document.getElementById("DHAProduc").style.display = "none";
 +
        document.getElementById("Software").style.display = "none";
 +
        document.getElementById("PastSub").style.display = "none";
 +
        document.getElementById("Modeling").style.display = "none";
 +
        document.getElementById("Intro").style.display = "none";
 +
        document.getElementById("WhatWeDid").style.display = "none";
 +
        document.getElementById(Name).style.display = "block";
     }
     }
</script>
</script>
Line 264: Line 282:
</td>
</td>
</tr>
</tr>
 +
</thead>
</thead>
<tbody id="bar">
<tbody id="bar">
Line 277: Line 296:
<li>   
<li>   
-
<a href="https://2014.igem.org/Team:HUST-Innovators" style="color:#000000">Home </a> </li>
+
<a id="Home" onclick="change('detail_home')" style="color:#000000">Home </a> </li>
-
<li id="introduction" onmouseover="list(1)" onmouseout="clean(1)">  
+
<li id="Background" onmouseover="list(1)" onmouseout="clean(1)">  
-
<a href="https://2014.igem.org/Team:HUST-Innovators/Team" style="color:#000000"> Introduction </a> </li>
+
<a href="https://2014.igem.org/Team:HUST-Innovators/Team" style="color:#000000"> Background </a> </li>
-
<li id="modeling" onmouseover="list(2)" onmouseout="clean(2)">  
+
<li id="Project" onmouseover="list(0)" onmouseout="clean(0)">
 +
<a href="https://2014.igem.org/Team:HUST-Innovators/Team" style="color:#000000"> Project </a> </li>
 +
 
 +
<li id="model_bar" onmouseover="list(2)" onmouseout="clean(2)">  
<a href="https://igem.org/Team.cgi?year=2014&amp;team_name=HUST-Innovators" style="color:#000000"> Modeling </a></li>
<a href="https://igem.org/Team.cgi?year=2014&amp;team_name=HUST-Innovators" style="color:#000000"> Modeling </a></li>
Line 303: Line 325:
-
<ul id="1" style="left: 110px; top: 50px;" onmouseover="list(1)" onmouseout="mouseOut(1)"; >
+
<ul id="1" style="left: 104px; top: 50px;" onmouseover="list(1)" onmouseout="mouseOut(1)"; >
-
<li><a href="https://2012.igem.org/Team:HUST-China/Project/Abstract">Abstract</a></li>
+
<li style="width: 100px;"><a onclick="change('SeqevolutionforSB')">Seq.evolution for Synthe.Bio.</a></li>
-
                                <li onmouseover="list(6)" onmouseout="clean(6)"><a href="https://2012.igem.org/Team:HUST-China/Project/LCD/Background">Lignocellulose Decomposer</a></li>
+
        <li style="width: 100px;" onmouseover="list(6)" onmouseout="clean(6)"><a onclick="change('3rd')">3rd Generation Sequencing</a></li>
-
<li onmouseover="list(7)" onmouseout="clean(7)"><a href="https://2012.igem.org/Team:HUST-China/Project/MFC/Mechanism">Microbial Fuel Cell</a></li>
+
-
<li><a href="https://2012.igem.org/Team:HUST-China/Project/FD">Future Directions</a></li>
+
-
<li><a href="https://2012.igem.org/Team:HUST-China/Project/Protocols">Protocols</a></li>
+
</ul>
</ul>
 +
    <ul id="0" style="left: 230px; top: 50px;" onmouseover="list(0)" onmouseout="mouseOut(0)"; >
 +
<li style="width: 80px;"><a onclick="change('OurProj')">Our Project</a></li>
 +
</ul>
-
<ul id="2" style="left: 240px; top: 50px;" onmouseover="list(2)" onmouseout="mouseOut(2)"; >
+
<ul id="2" style="left: 325px; top: 50px;" onmouseover="list(2)" onmouseout="mouseOut(2)"; >
-
<li><a href="https://2012.igem.org/Team:HUST-China/Modeling/Abstract">Abstract</a></li>
+
<li><a onclick="change('NewModel')">New Model</a></li>
-
<li><a href="https://2012.igem.org/Team:HUST-China/Modeling/CAL">Celluar Automaton</a></li>
+
<li><a onclick="change('DHAProduc')">DHA Production</a></li>
-
<li><a href="https://2012.igem.org/Team:HUST-China/Modeling/GM">Generator Model</a></li>
+
</ul>
</ul>
-
 
+
<ul id="3" style="left: 448px; top: 50px;" onmouseover="list(3)" onmouseout="mouseOut(3)"; >
-
<ul id="3" style="left: 361px; top: 50px;" onmouseover="list(3)" onmouseout="mouseOut(3)"; >
+
        <li style="width: 110px;"><a onclick="change('Software')">Software</a></li>
-
<li style="width: 110px;"><a href="https://2012.igem.org/Team:HUST-China/Parts">Parts Submitted</a></li>
+
<li style="width: 110px;"><a onclick="change('PastSub')">Parts Submitted</a></li>
-
<li style="width: 110px;"><a href="https://2012.igem.org/Team:HUST-China/Achievements/Modeling">Modeling</a></li>
+
<li style="width: 110px;"><a onclick="change('Modeling')">Modeling</a></li>
     </ul>
     </ul>
-
     <ul id="4" style="left: 500px; top: 50px;" onmouseover="list(4)" onmouseout="mouseOut(4)"; >
+
     <ul id="4" style="left: 594px; top: 50px;" onmouseover="list(4)" onmouseout="mouseOut(4)"; >
-
<li><a href="https://2012.igem.org/Team:HUST-China/Team">Our Team</a></li>
+
<li style="width: 50px;"><a onclick="change('Intro')">Intro.</a></li>
-
<li><a href="https://2012.igem.org/Team:HUST-China/Attribution">Attribution</a></li>
+
-
<li><font size="1"><a href="https://2012.igem.org/Team:HUST-China/Acknowledgement">Acknowledgement</a></font></li>
+
</ul>
</ul>
-
<ul id="5" style="left: 580px; top: 50px;" onmouseover="list(5)" onmouseout="mouseOut(5)"; >
+
<ul id="5" style="left: 680px; top: 50px;" onmouseover="list(5)" onmouseout="mouseOut(5)"; >
-
<li style="width: 148px;"><a href="https://2012.igem.org/Team:HUST-China/Safety">Safety</a></li>
+
<li style="width: 120px;"><a onclick="change('WhatWeDid')">What we did</a></li>
-
<li style="width: 148px;"><a href="https://2012.igem.org/Team:HUST-China/HumanPractice">Survey &amp; Outreach</a></li>
+
</ul>
</ul>
<div id="third">
<div id="third">
-
<ul id="6" style="left: 220px; top: 110px;" onmouseover="list(6)" onmouseout="mouseOut(6)"; >
+
<ul id="6" style="left: 225px; top: 130px;" onmouseover="list(6)" onmouseout="mouseOut(6)"; >
-
<li onmouseover="list(1)" onmouseout="mouseOut(1)"><a href="https://2012.igem.org/Team:HUST-China/Project/LCD/Background">Background</a></li>
+
<li onmouseover="list(1)" onmouseout="mouseOut(1)"><a onclick="change('3rdWhat')">What is SMRT</a></li>
-
<li onmouseover="list(1)" onmouseout="mouseOut(1)"><a href="https://2012.igem.org/Team:HUST-China/Project/LCD/Method">Method</a></li>
+
<li onmouseover="list(1)" onmouseout="mouseOut(1)"><a onclick="change('3rdWhy')">Why use SMRT</a></li>
-
<li onmouseover="list(1)" onmouseout="mouseOut(1)"><a href="https://2012.igem.org/Team:HUST-China/Project/LCD/Result">Result</a></li>
+
-
                                                <li onmouseover="list(1)" onmouseout="mouseOut(1)"><a href="https://2012.igem.org/Team:HUST-China/Project/LCD/Notebook">Notebook</a></li>
+
-
</ul>
+
-
<ul id="7" style="left: 220px; top: 166px;" onmouseover="list(7)" onmouseout="mouseOut(7)"; >
+
-
                                                <li onmouseover="list(1)" onmouseout="mouseOut(1)"><a href="https://2012.igem.org/Team:HUST-China/Project/MFC/Introduction">Introduction</a></li>
+
-
<li onmouseover="list(1)" onmouseout="mouseOut(1)"><a href="https://2012.igem.org/Team:HUST-China/Project/MFC/Mechanism">Mechanism</a></li>
+
-
<li onmouseover="list(1)" onmouseout="mouseOut(1)"><a href="https://2012.igem.org/Team:HUST-China/Project/MFC/Result">Result</a></li>
+
-
                <li onmouseover="list(1)" onmouseout="mouseOut(1)"><a href="https://2012.igem.org/Team:HUST-China/Project/MFC/Notebook">Notebook</a></li>
+
</ul>
</ul>
</div>
</div>
Line 368: Line 378:
 +
<!--home--------------------------------------------------------------------------------------->
 +
<tbody id="detail_home">
 +
<!--requirements section -->
 +
 +
<!--tips  -->
 +
<tr><td colspan="3"> <h2> Home  </h2></td></tr>
 +
 +
<tr>
 +
<td width="45%" valign="top">
 +
<p>We are currently working on providing teams with some easy to use design templates.
 +
<br> In the meantime you can also view other team wikis for inspiration! Here are some very good examples</p>
 +
 +
<ul>
 +
<li> <a href="https://2013.igem.org/Team:SDU-Denmark/"> 2013 SDU Denmark </a> </li>
 +
<li> <a href="https://2013.igem.org/Team:SYSU-China">2013 SYSU China</a> </li>
 +
<li> <a href="https://2013.igem.org/Team:Shenzhen_BGIC_ATCG"> 2013 Shenxhen BGIG ATCG </a></li>
 +
<li> <a href="https://2013.igem.org/Team:Colombia_Uniandes">2013 Colombia Unianades </a></li>
 +
<li> <a href="https://2013.igem.org/Team:Lethbridge">2013 Lethbridge</a></li>
 +
</ul>
 +
 +
<p>For a full wiki list, you can visit <a href="https://igem.org/Team_Wikis?year=2013">iGEM 2013 web sites </a> and <a href="https://igem.org/Team_Wikis?year=2012">iGEM 2012 web sites</a>  lists. </p>
 +
</td>
 +
 +
<td> </td>
 +
<td width="45%">
 +
 +
<p>This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started: </p>
 +
 +
<ul>
 +
<li>State your accomplishments! Tell people what you have achieved from the start. </li>
 +
<li>Be clear about what you are doing and what you plan to do.</li>
 +
<li>You have a global audience! Consider the different backgrounds that your users come from.</li>
 +
<li>Make sure information is easy to find; nothing should be more than 3 clicks away.  </li>
 +
<li>Avoid using very small fonts and low contrast colors; information should be easy to read.  </li>
 +
<li>Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the <a href="">iGEM 2013 calendar</a> </li>
 +
<li>Have lots of fun! </li>
 +
</ul>
 +
<br>
 +
</td>
 +
</tr>
</tbody>
</tbody>
 +
<!--Seq.evolution for S.B---------------------------------------------------------------------->
 +
<tbody id="SeqevolutionforSB" style="display: none;">
 +
<!--requirements section-->
 +
<!--tips  -->
 +
<tr><td colspan="3"> <h2> Evolution of Synthetic Biology  </h2></td></tr>
 +
 +
<tr>
 +
 +
<td>
 +
<h3>Overture(IGS and Bioinformatics)</h3>
 +
<img src="https://static.igem.org/mediawiki/2012/2/2e/Part1.png" >
 +
<p>
 +
In 1977 Sanger and colleagues introduced the "dideoxy" chain-termination method for sequencing DNA molecules, also known as the "Sanger method".This was a major breakthrough and allowed long stretches of DNA to be rapidly and accurately sequenced. It earned him his second Nobel prize in Chemistry in 1980, which he shared with Walter Gilbert and Paul Berg.The new method was used by Sanger and colleagues to sequence human mitochondrial DNA (16,569 base pairs) and bacteriophage λ (48,502 base pairs).The dideoxy method was eventually used to sequence the entire human genome.
 +
</p>
 +
<img src="https://static.igem.org/mediawiki/2012/2/2e/Part1.png" >
 +
<p>
 +
As the accumulation of sequence data, databases formed, which announced the birth of the bioinformatics.
 +
</p>
 +
<br/>
 +
<img src="https://static.igem.org/mediawiki/2012/2/2e/Part1.png" >
 +
<h3>Sonata(NGS and Synthetic Biology)</h3>
 +
<img src="https://static.igem.org/mediawiki/2012/2/2e/Part1.png" >
 +
<p>
 +
In short, the First GS has some fatal drawbacks such as high cost and low throughput. This is why it was replaced by NGS, such as 454, Solexa, Hiseq, etc.  The NGS has distinct effects on cost-reduction and time-saving with high accuracy. For instance, it took only one week to finish the human genome project by NGS, while the time using by First GS is 3 years.
 +
</p>
 +
<img src="https://static.igem.org/mediawiki/2012/2/2e/Part1.png" >
 +
<p>
 +
As more and more species were sequenced, the size of genomic data is enlarged. As is known, the sequence of species is the major prerequisite of the SB. So the conclusion is drawn that the emergence of the NGS indicated the naissance of SB.
 +
</p>
 +
 +
</td>
 +
</tr>
 +
 +
</tbody>
 +
 +
<!--3rd Generation Sequencing--------------------------------------------------------------------->
 +
<tbody id="3rd" style="display: none;">
 +
<!--requirements section -->
 +
 +
<!--tips  -->
 +
<tr><td colspan="3"> <h2> Tips  </h2></td></tr>
 +
 +
<tr>
 +
<td width="45%" valign="top">
 +
<p>We are currently working on providing teams with some easy to use design templates.
 +
<br> In the meantime you can also view other team wikis for inspiration! Here are some very good examples</p>
 +
 +
<ul>
 +
<li> <a href="https://2013.igem.org/Team:SDU-Denmark/"> 2013 SDU Denmark </a> </li>
 +
<li> <a href="https://2013.igem.org/Team:SYSU-China">2013 SYSU China</a> </li>
 +
<li> <a href="https://2013.igem.org/Team:Shenzhen_BGIC_ATCG"> 2013 Shenxhen BGIG ATCG </a></li>
 +
<li> <a href="https://2013.igem.org/Team:Colombia_Uniandes">2013 Colombia Unianades </a></li>
 +
<li> <a href="https://2013.igem.org/Team:Lethbridge">2013 Lethbridge</a></li>
 +
</ul>
 +
 +
<p>For a full wiki list, you can visit <a href="https://igem.org/Team_Wikis?year=2013">iGEM 2013 web sites </a> and <a href="https://igem.org/Team_Wikis?year=2012">iGEM 2012 web sites</a>  lists. </p>
 +
</td>
 +
 +
<td> </td>
 +
<td width="45%">
 +
 +
<p>This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started: </p>
 +
 +
<ul>
 +
<li>State your accomplishments! Tell people what you have achieved from the start. </li>
 +
<li>Be clear about what you are doing and what you plan to do.</li>
 +
<li>You have a global audience! Consider the different backgrounds that your users come from.</li>
 +
<li>Make sure information is easy to find; nothing should be more than 3 clicks away.  </li>
 +
<li>Avoid using very small fonts and low contrast colors; information should be easy to read.  </li>
 +
<li>Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the <a href="">iGEM 2013 calendar</a> </li>
 +
<li>Have lots of fun! </li>
 +
</ul>
 +
<br>
 +
</td>
 +
</tr>
 +
 +
</tbody>
 +
 +
<!--3rd What--------------------------------------------------------------------->
 +
<tbody id="3rdWhat" style="display: none;">
 +
<!--requirements section-->
 +
 +
<!--tips  -->
 +
<tr><td colspan="3"> <h2> What is SMRT </h2></td></tr>
 +
 +
<tr>
 +
 +
<td>
 +
<img src="https://static.igem.org/mediawiki/2012/2/2e/Part1.png" >
 +
<p>
 +
Single molecule real time sequencing (also known as SMRT) is a parallelized single molecule DNA sequencing by synthesis technology developed by Pacific Biosciences. Single molecule real time sequencing utilizes the zero-mode waveguide (ZMW), developed in the laboratories of Harold G. Craighead and Watt W. Webb[1] at Cornell University. A single DNA polymerase enzyme is affixed at the bottom of a ZMW with a single molecule of DNA as a template. The ZMW is a structure that creates an illuminated observation volume that is small enough to observe only a single nucleotide of DNA (also known as a base) being incorporated by DNA polymerase. Each of the four DNA bases is attached to one of four different fluorescent dyes. When a nucleotide is incorporated by the DNA polymerase, the fluorescent tag is cleaved off and diffuses out of the observation area of the ZMW where its fluorescence is no longer observable. A detector detects the fluorescent signal of the nucleotide incorporation, and the base call is made according to the corresponding fluorescence of the dye.
 +
</p>
 +
<img src="https://static.igem.org/mediawiki/2012/2/2e/Part1.png" >
 +
<p>
 +
The DNA sequencing is done on a chip that contains many ZMWs. Inside each ZMW, a single active DNA polymerase with a single molecule of single stranded DNA template is immobilized to the bottom through which light can penetrate and create a visualization chamber that allows monitoring of the activity of the DNA polymerase at a single molecule level. The signal from a phospho-linked nucleotide incorporated by the DNA polymerase is detected as the DNA synthesis proceeds which results in the DNA sequencing in real time.
 +
</p>
 +
<h3>Phospholinked nucleotide</h3>
 +
<p>
 +
For each of the nucleotide bases, there are four corresponding fluorescent dye molecules that enable the detector to identify the base being incorporated by the DNA polymerase as it performs the DNA synthesis. The fluorescent dye molecule is attached to the phosphate chain of the nucleotide. When the nucleotide is incorporated by the DNA polymerase, the fluorescent dye is cleaved off with the phosphate chain as a part of a natural DNA synthesis process during which a phosphodiester bond is created to elongate the DNA chain. The cleaved fluorescent dye molecule then diffuses out of the detection volume so that the fluorescent signal is no longer detected.
 +
</p>
 +
<h3>Zero-mode waveguide</h3>
 +
<img src="https://static.igem.org/mediawiki/2012/2/2e/Part1.png" >
 +
<p>
 +
The zero-mode waveguide (ZMW) is a nanophotonic confinement structure that consists of a circular hole in an aluminum cladding film deposited on a clear silica substrate.[3] The ZMW holes are ~70 nm in diameter and ~100 nm in depth. Due to the behavior of light when it travels through a small aperture, the optical field decays exponentially inside the chamber.[4] The observation volume within an illuminated ZMW is ~20 zeptoliters (20 X 10−21 liters). Within this volume, the activity of DNA polymerase incorporating a single nucleotide can be readily detected.
 +
</p>
 +
 +
</td>
 +
</tr>
 +
 +
</tbody>
 +
 +
 +
<!--3rd Why--------------------------------------------------------------------->
 +
<tbody id="3rdWhy" style="display: none;">
 +
<!--requirements section-->
 +
 +
<!--tips  -->
 +
<tr><td colspan="3"> <h2> Why is SMRT(The merits compared to the NGS) </h2></td></tr>
 +
 +
<tr>
 +
 +
<td>
 +
<h3>Relative Terminologies</h3>
 +
<img src="https://static.igem.org/mediawiki/2012/2/2e/Part1.png" >
 +
<h4>Contigs</h4>
 +
<p>
 +
A sequence contig is a contiguous, overlapping sequence read resulting from the reassembly of the small DNA fragments generated by bottom-up sequencing strategies. This meaning of contig is consistent with the original definition by Rodger Staden (1979). The bottom-up DNA sequencing strategy involves shearing genomic DNA into many small fragments ("bottom"), sequencing these fragments, reassembling them back into contigs and eventually the entire genome ("up"). Because current technology allows for the direct sequencing of only relatively short DNA fragments (300–1000 nucleotides), genomic DNA must be fragmented into small pieces prior to sequencing. In bottom-up sequencing projects, amplified DNA is sheared randomly into fragments appropriately sized for sequencing. The subsequent sequence reads, which are the data that contains the sequence of each fragment, are assembled into contigs, which are finally connected by sequencing the gaps between them resulting in a sequenced genome. The ability to assemble contigs depends on the overlap of reads. Because shearing is random and performed on multiple copies of DNA, each portion of the genome should be represented multiple times in different fragment frames. In other words, the sequences of the fragments (and thus the reads) should overlap. After sequencing, the overlapping reads are assembled into contigs by assembly software.
 +
</p>
 +
<h4>Scaffold</h4>
 +
<p>
 +
Scaffolds consist of overlapping contigs separated by gaps of known length. The new constraints placed on the orientation of the contigs allows for the placement of highly repeated sequences in the genome. If one end read has a repetitive sequence, as long as its mate pair is located within a contig, its placement is known. The remaining gaps between the contigs in the scaffolds can then be sequenced by a variety of methods, including PCR amplification followed by sequencing (for smaller gaps) and BAC cloning methods followed by sequencing for larger gaps.
 +
</p>
 +
 +
<h3>Advancement from NGS</h3>
 +
<h4>Extremely Long Reads</h4>
 +
 +
<p>
 +
The NGS sequencing Technology requires prohibitive storage space and operation time for the sake of relatively short digital crumbs( In fact, the average length of NGS reads is far longer than the Sanger, the first GS reads). Clearly, the shortage of NGS is their assembly, like puzzle games. The shorter the reads are, the more barriers we will meet in the concatenation process. Unfortunately, this problem is fundamental data property, even if we have more proper modeling and more efficient algorithms. Until now we have found no chance to compensate this demerit.
 +
</p>
 +
<p>
 +
Comparatively speaking, the SMRT sequencing operating on PacBio RS II
 +
</p>
 +
 +
<p>
 +
1. incredibly long read length: the average read length is between 5,000 to 8,000 bases per read( the average length of NGS read ranges from 150 to 400 bp). The maximum read length can reach 20,000 bp.
 +
<br>
 +
For instance, the USDA had intended to sequence the microbes in goats. Compared to the least 18 contigs produced by the NGS, which means the project is uncompleted, the SMRT can get the ultimate contig—a successful sequencing.
 +
</p>
 +
<img src="https://static.igem.org/mediawiki/2012/2/2e/Part1.png" >
 +
<p>
 +
2.High accuracy:In short, the accuracy of sequencing can reach 99.999%.
 +
</p>
 +
<img src="https://static.igem.org/mediawiki/2012/2/2e/Part1.png" >
 +
<p>
 +
3.GC Problem:For the NGS, areas with high GC concentration mean low coverage. Only insufficient info can be dug out for assembly. This is why many gaps between DNA sequences emerge in the result.
 +
<br>
 +
In SMRT, the coverage do not fluctuate as the GC content varies. So the Problem can be avoided.
 +
</p>
 +
 +
</td>
 +
</tr>
 +
 +
</tbody>
 +
 +
 +
<!--Our Projiect---------------------------------------------------------------------->
 +
<tbody id="OurProj" style="display: none;">
 +
<!--requirements section -->
 +
 +
<!--tips  -->
 +
<tr><td colspan="3"> <h2> Our Project </h2></td></tr>
 +
 +
<tr>
 +
<td >
 +
<h3>Sequencing</h3>
 +
<p>First, we decided to sequence the unknown Thraustochytrium roseum. As we read the thesis on Velvet, SSpace, GRASS and so on, we finally made a determination to use the struture of the GRASS to do the scaffolding process after finishing getting contigs. As the data is sequenced from the 3rd Generation Sequencing Method, we had changed some lines of the code in order to fix the characteristics of the data.
 +
<br>GRASS has some progresses: Sort, Bundle, Extract, RemoveAmbiguous, Erode  IsolateContigsThink. Those are not needed while we are using the SMRT sequencing data. So we deleted code about them.
 +
<br>Think about the NGS Assembly, nearly all the softwares use pair-end reads to link the contigs through the scaffolding process. Knowing that the reads from the Pacbio machines are extremely,after self-overlapping, we let the Pacbio sequence replace the contigs in GRASS to do the scaffolding.
 +
<br>Here is a part of result:
 +
</p>
 +
<img src="https://static.igem.org/mediawiki/2012/2/2e/Part1.png" >
 +
<p>
 +
Then, with the help of Nextomics, we finished the annotation and found that the scaffold shown above is the required one.
 +
</p>
 +
<br>
 +
</td>
 +
</tr>
 +
 +
</tbody>
 +
 +
<!--New Modle---------------------------------------------------------------------->
 +
<tbody id="NewModel" style="display: none;">
 +
<!--requirements section -->
 +
 +
<!--tips  -->
 +
<tr><td colspan="3"> <h2> Tips  </h2></td></tr>
 +
 +
<tr>
 +
<td width="45%" valign="top">
 +
<p>We are currently working on providing teams with some easy to use design templates.
 +
<br> In the meantime you can also view other team wikis for inspiration! Here are some very good examples</p>
 +
 +
<ul>
 +
<li> <a href="https://2013.igem.org/Team:SDU-Denmark/"> 2013 SDU Denmark </a> </li>
 +
<li> <a href="https://2013.igem.org/Team:SYSU-China">2013 SYSU China</a> </li>
 +
<li> <a href="https://2013.igem.org/Team:Shenzhen_BGIC_ATCG"> 2013 Shenxhen BGIG ATCG </a></li>
 +
<li> <a href="https://2013.igem.org/Team:Colombia_Uniandes">2013 Colombia Unianades </a></li>
 +
<li> <a href="https://2013.igem.org/Team:Lethbridge">2013 Lethbridge</a></li>
 +
</ul>
 +
 +
<p>For a full wiki list, you can visit <a href="https://igem.org/Team_Wikis?year=2013">iGEM 2013 web sites </a> and <a href="https://igem.org/Team_Wikis?year=2012">iGEM 2012 web sites</a>  lists. </p>
 +
</td>
 +
 +
<td> </td>
 +
<td width="45%">
 +
 +
<p>This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started: </p>
 +
 +
<ul>
 +
<li>State your accomplishments! Tell people what you have achieved from the start. </li>
 +
<li>Be clear about what you are doing and what you plan to do.</li>
 +
<li>You have a global audience! Consider the different backgrounds that your users come from.</li>
 +
<li>Make sure information is easy to find; nothing should be more than 3 clicks away.  </li>
 +
<li>Avoid using very small fonts and low contrast colors; information should be easy to read.  </li>
 +
<li>Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the <a href="">iGEM 2013 calendar</a> </li>
 +
<li>Have lots of fun! </li>
 +
</ul>
 +
<br>
 +
</td>
 +
</tr>
 +
 +
</tbody>
 +
 +
<!--DHA Production---------------------------------------------------------------------->
 +
<tbody id="DHAProduc" style="display: none;">
 +
<!--requirements section -->
 +
 +
<!--tips  -->
 +
<tr><td colspan="3"> <h2> Tips  </h2></td></tr>
 +
 +
<tr>
 +
<td width="45%" valign="top">
 +
<p>We are currently working on providing teams with some easy to use design templates.
 +
<br> In the meantime you can also view other team wikis for inspiration! Here are some very good examples</p>
 +
 +
<ul>
 +
<li> <a href="https://2013.igem.org/Team:SDU-Denmark/"> 2013 SDU Denmark </a> </li>
 +
<li> <a href="https://2013.igem.org/Team:SYSU-China">2013 SYSU China</a> </li>
 +
<li> <a href="https://2013.igem.org/Team:Shenzhen_BGIC_ATCG"> 2013 Shenxhen BGIG ATCG </a></li>
 +
<li> <a href="https://2013.igem.org/Team:Colombia_Uniandes">2013 Colombia Unianades </a></li>
 +
<li> <a href="https://2013.igem.org/Team:Lethbridge">2013 Lethbridge</a></li>
 +
</ul>
 +
 +
<p>For a full wiki list, you can visit <a href="https://igem.org/Team_Wikis?year=2013">iGEM 2013 web sites </a> and <a href="https://igem.org/Team_Wikis?year=2012">iGEM 2012 web sites</a>  lists. </p>
 +
</td>
 +
 +
<td> </td>
 +
<td width="45%">
 +
 +
<p>This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started: </p>
 +
 +
<ul>
 +
<li>State your accomplishments! Tell people what you have achieved from the start. </li>
 +
<li>Be clear about what you are doing and what you plan to do.</li>
 +
<li>You have a global audience! Consider the different backgrounds that your users come from.</li>
 +
<li>Make sure information is easy to find; nothing should be more than 3 clicks away.  </li>
 +
<li>Avoid using very small fonts and low contrast colors; information should be easy to read.  </li>
 +
<li>Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the <a href="">iGEM 2013 calendar</a> </li>
 +
<li>Have lots of fun! </li>
 +
</ul>
 +
<br>
 +
</td>
 +
</tr>
 +
 +
</tbody>
 +
 +
<!--Software---------------------------------------------------------------------->
 +
<tbody id="Software" style="display: none;" >
 +
<!--requirements section -->
 +
 +
<!--tips  -->
 +
<tr><td colspan="3"> <h2> Tips  </h2></td></tr>
 +
 +
<tr>
 +
<td width="45%" valign="top">
 +
<p>We are currently working on providing teams with some easy to use design templates.
 +
<br> In the meantime you can also view other team wikis for inspiration! Here are some very good examples</p>
 +
 +
<ul>
 +
<li> <a href="https://2013.igem.org/Team:SDU-Denmark/"> 2013 SDU Denmark </a> </li>
 +
<li> <a href="https://2013.igem.org/Team:SYSU-China">2013 SYSU China</a> </li>
 +
<li> <a href="https://2013.igem.org/Team:Shenzhen_BGIC_ATCG"> 2013 Shenxhen BGIG ATCG </a></li>
 +
<li> <a href="https://2013.igem.org/Team:Colombia_Uniandes">2013 Colombia Unianades </a></li>
 +
<li> <a href="https://2013.igem.org/Team:Lethbridge">2013 Lethbridge</a></li>
 +
</ul>
 +
 +
<p>For a full wiki list, you can visit <a href="https://igem.org/Team_Wikis?year=2013">iGEM 2013 web sites </a> and <a href="https://igem.org/Team_Wikis?year=2012">iGEM 2012 web sites</a>  lists. </p>
 +
</td>
 +
 +
<td> </td>
 +
<td width="45%">
 +
 +
<p>This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started: </p>
 +
 +
<ul>
 +
<li>State your accomplishments! Tell people what you have achieved from the start. </li>
 +
<li>Be clear about what you are doing and what you plan to do.</li>
 +
<li>You have a global audience! Consider the different backgrounds that your users come from.</li>
 +
<li>Make sure information is easy to find; nothing should be more than 3 clicks away.  </li>
 +
<li>Avoid using very small fonts and low contrast colors; information should be easy to read.  </li>
 +
<li>Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the <a href="">iGEM 2013 calendar</a> </li>
 +
<li>Have lots of fun! </li>
 +
</ul>
 +
<br>
 +
</td>
 +
</tr>
 +
 +
</tbody>
 +
 +
<!--Past Submmited---------------------------------------------------------------------->
 +
<tbody id="PastSub" style="display: none;" >
 +
<!--requirements section -->
 +
 +
<!--tips  -->
 +
<tr><td colspan="3"> <h2> Part Submitted </h2></td></tr>
 +
<tr>
 +
<td>Tube</td>
 +
<td>Part</td>
 +
<td>Plasmid Backbone</td>
 +
<td>Resistance Status</td>
 +
<td>Notes</td>
 +
</tr>
 +
<tr>
 +
<td>1</td>
 +
<td>BBa_K1551000</td>
 +
<td>pSB1C3</td>
 +
<td>Accepted</td>
 +
<td>User sequenced</td>
 +
</tr>
 +
 +
</tbody>
 +
 +
<!--Modeling---------------------------------------------------------------------->
 +
<tbody id="Modeling" style="display: none;">
 +
<!--requirements section -->
 +
 +
<!--tips  -->
 +
<tr><td colspan="3"> <h2> Tips  </h2></td></tr>
 +
 +
<tr>
 +
<td width="45%" valign="top">
 +
<p>We are currently working on providing teams with some easy to use design templates.
 +
<br> In the meantime you can also view other team wikis for inspiration! Here are some very good examples</p>
 +
 +
<ul>
 +
<li> <a href="https://2013.igem.org/Team:SDU-Denmark/"> 2013 SDU Denmark </a> </li>
 +
<li> <a href="https://2013.igem.org/Team:SYSU-China">2013 SYSU China</a> </li>
 +
<li> <a href="https://2013.igem.org/Team:Shenzhen_BGIC_ATCG"> 2013 Shenxhen BGIG ATCG </a></li>
 +
<li> <a href="https://2013.igem.org/Team:Colombia_Uniandes">2013 Colombia Unianades </a></li>
 +
<li> <a href="https://2013.igem.org/Team:Lethbridge">2013 Lethbridge</a></li>
 +
</ul>
 +
 +
<p>For a full wiki list, you can visit <a href="https://igem.org/Team_Wikis?year=2013">iGEM 2013 web sites </a> and <a href="https://igem.org/Team_Wikis?year=2012">iGEM 2012 web sites</a>  lists. </p>
 +
</td>
 +
 +
<td> </td>
 +
<td width="45%">
 +
 +
<p>This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started: </p>
 +
 +
<ul>
 +
<li>State your accomplishments! Tell people what you have achieved from the start. </li>
 +
<li>Be clear about what you are doing and what you plan to do.</li>
 +
<li>You have a global audience! Consider the different backgrounds that your users come from.</li>
 +
<li>Make sure information is easy to find; nothing should be more than 3 clicks away.  </li>
 +
<li>Avoid using very small fonts and low contrast colors; information should be easy to read.  </li>
 +
<li>Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the <a href="">iGEM 2013 calendar</a> </li>
 +
<li>Have lots of fun! </li>
 +
</ul>
 +
<br>
 +
</td>
 +
</tr>
 +
 +
</tbody>
 +
 +
<!--Intro---------------------------------------------------------------------->
 +
<tbody id="Intro" style="display: none;">
 +
<!--requirements section -->
 +
 +
<!--tips  -->
 +
<tr><td colspan="3"> <h2> Tips  </h2></td></tr>
 +
 +
<tr>
 +
<td width="45%" valign="top">
 +
<p>We are currently working on providing teams with some easy to use design templates.
 +
<br> In the meantime you can also view other team wikis for inspiration! Here are some very good examples</p>
 +
 +
<ul>
 +
<li> <a href="https://2013.igem.org/Team:SDU-Denmark/"> 2013 SDU Denmark </a> </li>
 +
<li> <a href="https://2013.igem.org/Team:SYSU-China">2013 SYSU China</a> </li>
 +
<li> <a href="https://2013.igem.org/Team:Shenzhen_BGIC_ATCG"> 2013 Shenxhen BGIG ATCG </a></li>
 +
<li> <a href="https://2013.igem.org/Team:Colombia_Uniandes">2013 Colombia Unianades </a></li>
 +
<li> <a href="https://2013.igem.org/Team:Lethbridge">2013 Lethbridge</a></li>
 +
</ul>
 +
 +
<p>For a full wiki list, you can visit <a href="https://igem.org/Team_Wikis?year=2013">iGEM 2013 web sites </a> and <a href="https://igem.org/Team_Wikis?year=2012">iGEM 2012 web sites</a>  lists. </p>
 +
</td>
 +
 +
<td> </td>
 +
<td width="45%">
 +
 +
<p>This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started: </p>
 +
 +
<ul>
 +
<li>State your accomplishments! Tell people what you have achieved from the start. </li>
 +
<li>Be clear about what you are doing and what you plan to do.</li>
 +
<li>You have a global audience! Consider the different backgrounds that your users come from.</li>
 +
<li>Make sure information is easy to find; nothing should be more than 3 clicks away.  </li>
 +
<li>Avoid using very small fonts and low contrast colors; information should be easy to read.  </li>
 +
<li>Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the <a href="">iGEM 2013 calendar</a> </li>
 +
<li>Have lots of fun! </li>
 +
</ul>
 +
<br>
 +
</td>
 +
</tr>
 +
 +
</tbody>
 +
 +
<!--What we did---------------------------------------------------------------------->
 +
<tbody id="WhatWeDid" style="display: none;">
 +
<!--requirements section -->
 +
 +
<!--tips  -->
 +
<tr><td colspan="3"> <h2> Tips  </h2></td></tr>
 +
 +
<tr>
 +
<td width="45%" valign="top">
 +
<p>We are currently working on providing teams with some easy to use design templates.
 +
<br> In the meantime you can also view other team wikis for inspiration! Here are some very good examples</p>
 +
 +
<ul>
 +
<li> <a href="https://2013.igem.org/Team:SDU-Denmark/"> 2013 SDU Denmark </a> </li>
 +
<li> <a href="https://2013.igem.org/Team:SYSU-China">2013 SYSU China</a> </li>
 +
<li> <a href="https://2013.igem.org/Team:Shenzhen_BGIC_ATCG"> 2013 Shenxhen BGIG ATCG </a></li>
 +
<li> <a href="https://2013.igem.org/Team:Colombia_Uniandes">2013 Colombia Unianades </a></li>
 +
<li> <a href="https://2013.igem.org/Team:Lethbridge">2013 Lethbridge</a></li>
 +
</ul>
 +
 +
<p>For a full wiki list, you can visit <a href="https://igem.org/Team_Wikis?year=2013">iGEM 2013 web sites </a> and <a href="https://igem.org/Team_Wikis?year=2012">iGEM 2012 web sites</a>  lists. </p>
 +
</td>
 +
 +
<td> </td>
 +
<td width="45%">
 +
 +
<p>This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started: </p>
 +
 +
<ul>
 +
<li>State your accomplishments! Tell people what you have achieved from the start. </li>
 +
<li>Be clear about what you are doing and what you plan to do.</li>
 +
<li>You have a global audience! Consider the different backgrounds that your users come from.</li>
 +
<li>Make sure information is easy to find; nothing should be more than 3 clicks away.  </li>
 +
<li>Avoid using very small fonts and low contrast colors; information should be easy to read.  </li>
 +
<li>Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the <a href="">iGEM 2013 calendar</a> </li>
 +
<li>Have lots of fun! </li>
 +
</ul>
 +
<br>
 +
</td>
 +
</tr>
 +
 +
</tbody>
</table>
</table>
</body></html>
</body></html>

Revision as of 12:51, 15 October 2014

WELCOME TO iGEM 2014!

Your team has been approved and you are ready to start the iGEM season!
On this page you can document your project, introduce your team members, document your progress
and share your iGEM experience with the rest of the world!

Click here to edit this page!

Home

We are currently working on providing teams with some easy to use design templates.
In the meantime you can also view other team wikis for inspiration! Here are some very good examples

For a full wiki list, you can visit iGEM 2013 web sites and iGEM 2012 web sites lists.

This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started:

  • State your accomplishments! Tell people what you have achieved from the start.
  • Be clear about what you are doing and what you plan to do.
  • You have a global audience! Consider the different backgrounds that your users come from.
  • Make sure information is easy to find; nothing should be more than 3 clicks away.
  • Avoid using very small fonts and low contrast colors; information should be easy to read.
  • Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the iGEM 2013 calendar
  • Have lots of fun!