Team:DTU Denmark/USERprogramoutputformat
From 2009.igem.org
(16 intermediate revisions not shown) | |||
Line 165: | Line 165: | ||
<tr> | <tr> | ||
<td width="163px" height="100%" valign="top"> | <td width="163px" height="100%" valign="top"> | ||
- | + | <p> | |
+ | <font color="#990000" face="arial" size="3"> | ||
<br> | <br> | ||
- | The redoxilator | + | The redoxilator<br> |
</font> | </font> | ||
+ | </p> | ||
<font color="" face="arial" size="2"> | <font color="" face="arial" size="2"> | ||
- | <a href="https://2009.igem.org/Team:DTU_Denmark/ | + | <a href="https://2009.igem.org/Team:DTU_Denmark/genetic_design" CLASS=leftbar>- Genetic design</a><br> |
- | <a href="https://2009.igem.org/Team:DTU_Denmark/ | + | <a href="https://2009.igem.org/Team:DTU_Denmark/applications" CLASS=leftbar>- Applications and perspectives</a><br> |
- | <a href="https://2009.igem.org/Team:DTU_Denmark/ | + | <a href="https://2009.igem.org/Team:DTU_Denmark/safety" CLASS=leftbar>- Safety considerations</a><br> |
</font> | </font> | ||
+ | <p> | ||
<font color="#990000" face="arial" size="3"> | <font color="#990000" face="arial" size="3"> | ||
- | <br>The USER | + | <br>The USER assembly standard<br> |
</font> | </font> | ||
+ | </p> | ||
<font face="arial" size="2"> | <font face="arial" size="2"> | ||
- | <a href="https://2009.igem.org/Team:DTU_Denmark/USERprinciple" CLASS=leftbar>- | + | <a href="https://2009.igem.org/Team:DTU_Denmark/USERprinciple" CLASS=leftbar>- USER fusion of biobricks</a><br> |
- | + | ||
- | + | ||
</font> | </font> | ||
+ | <p> | ||
<font color="#990000" face="arial" size="3"> | <font color="#990000" face="arial" size="3"> | ||
- | <br>USER | + | <br>USER fusion primer design software<br> |
</font> | </font> | ||
+ | </p> | ||
<font face="arial" size="2"> | <font face="arial" size="2"> | ||
<a href="https://2009.igem.org/Team:DTU_Denmark/USERprogram" CLASS=leftbar>- Abstract</a><br> | <a href="https://2009.igem.org/Team:DTU_Denmark/USERprogram" CLASS=leftbar>- Abstract</a><br> | ||
<a href="https://2009.igem.org/Team:DTU_Denmark/USERprograminstructions" CLASS=leftbar>- Instructions</a><br> | <a href="https://2009.igem.org/Team:DTU_Denmark/USERprograminstructions" CLASS=leftbar>- Instructions</a><br> | ||
<a href="https://2009.igem.org/Team:DTU_Denmark/USERprogramoutputformat" CLASS=leftbar>- Output format</a><br> | <a href="https://2009.igem.org/Team:DTU_Denmark/USERprogramoutputformat" CLASS=leftbar>- Output format</a><br> | ||
+ | </font> | ||
+ | <p> | ||
+ | <font color="#990000" face="arial" size="3"> | ||
+ | <br>Experimental results<br> | ||
+ | </font> | ||
+ | </p> | ||
+ | <font face="arial" size="2"> | ||
+ | <a href="https://2009.igem.org/Team:DTU_Denmark/results" CLASS=leftbar>- Results and discussion</a><br> | ||
</font> | </font> | ||
</td> | </td> | ||
Line 194: | Line 206: | ||
<font color="#990000" face="arial" size="5"> | <font color="#990000" face="arial" size="5"> | ||
<br> | <br> | ||
- | <b>The project</b | + | <b>The project</b><br><br> |
</font> | </font> | ||
<font color="#333333" face="arial" size="2.5"> | <font color="#333333" face="arial" size="2.5"> | ||
Line 202: | Line 214: | ||
- | <font size="4"><b>USER fusion primer design software</b></font><br><br> | + | <font size="4"><b>The USER fusion primer design software: PHUSER<br>(<u>P</u>rimer <u>H</u>elp for <u>USER</u>)</b></font><br><br> |
- | <font size="3"><b> | + | <font size="3"><b>PHUSER output format</b></font><br> |
- | <p align="justify"> | + | <p align="justify">Like the input options, the output from PHUSER is kept simple. First an overview of all needed primers is shown. The output is fairly self-explanatory, although it should be noted that primer consist of a fusion tail (ft) and a binding region (br), easily distinguished from one another by the occurence of the essential uracil. For example:</p><br> |
- | < | + | <font face="Lucida Console" size="2.5"> |
+ | |--ft--| |-------br-------|<br> | ||
+ | GGGTTAAU CAAATTATAGCCATACAG | ||
+ | </font><br><br> | ||
- | <p align="justify">< | + | <p align="justify"><b>IMPORTANT: Note that the entire sequence constitutes the primer. The space is simply added for illustrative purposes, and should be omitted when synthesizing the primers</b><br><br> |
+ | Just below is the grafic overview of biobricks and primers. The first block illustrates the forward primer for biobrick 1, i.e. binding region to biobrick 1, and fusion tail to the selected USER cassette. The following blocks (the number depends on how many biobricks were entered), illustrate the region at which biobrick 1 is fused to biobrick 2 and so forth. The last 40 bases of biobrick 1 and the first 40 bases of biobrick 2 are displayed, along with the positioning of the fusion tails and binding regions for both reverse and forward primers. The last block of the graphic overview illustrated the last biobrick and its binding region to the selected cassette, diplayed in a similar fashion as described for the first block.<br><br> | ||
+ | |||
+ | Lastly, the primers are displayed again, only this time with more detailed information, such as T<sub>M</sub> and GC ratio. More parameters are to be added to the output.<br><br> | ||
+ | |||
+ | |||
+ | <b>Design your primers with PHUSER <a href="http://igem.grafiki.org/" CLASS=leftbar target="blank">here</a></b><br><br> | ||
</font> | </font> | ||
Line 218: | Line 239: | ||
<td width="182px" height="100%" valign="top" bgcolor=DDDDDD class="greybox"> | <td width="182px" height="100%" valign="top" bgcolor=DDDDDD class="greybox"> | ||
<font face="arial" size="2"> | <font face="arial" size="2"> | ||
- | |||
Line 224: | Line 244: | ||
- | <p | + | <p> |
- | + | <strong>Achievements</strong><br> | |
- | < | + | <br> |
+ | <strong>Redox sensing device</strong><br> | ||
+ | Two novel genes have been designed and synthesized each comprised of 5 genetic elements. Together they function as a device termed the Redoxilator that can sense the internal redox state of a yeast cell, and output a reporter signal. Extensive mathematical modelling was performed to simulate how the construct would operate <i>in vivo</i>.<br> | ||
+ | <br> | ||
+ | <strong>Biobricks</strong><br> | ||
+ | DNA of several new biobricks have been designed and submitted including a yeast optimized GFP reporter protein, a protein degradation sequence and a fast degradable yeast GFP. (Bronze medal)<br> | ||
+ | <br> | ||
+ | We have demonstrated that our USER fusion biobrick works as expected and documented it (silver medal)<br> | ||
+ | <br> | ||
+ | <strong>USER fusion Assembly standard</strong><br> | ||
+ | A new biobrick assembly standard that allows the rapid construction of multi-part devices have been developed and documented. The assembly standard offers many benefits: All restriction sites are allowed, multiple biobricks can be joined in one step, the result is scar-free making it ideal for protein fusions and more. (Gold medal)<br> | ||
+ | <br> | ||
+ | <strong>USER-fusion primer design software</strong><br> | ||
+ | A novel and very useful software tool have been developed that can automatically design the optimal primers for USER fusion assembly of 2-9 biobricks, taking several parameters into account. | ||
+ | </p> | ||
- | |||
</font> | </font> |
Latest revision as of 03:17, 22 October 2009
Home | The Team | The Project | Parts submitted | Modelling | Notebook |
- Applications and perspectives - Safety considerations
- Instructions - Output format
|
The project The USER fusion primer design software: PHUSER (Primer Help for USER) PHUSER output format Like the input options, the output from PHUSER is kept simple. First an overview of all needed primers is shown. The output is fairly self-explanatory, although it should be noted that primer consist of a fusion tail (ft) and a binding region (br), easily distinguished from one another by the occurence of the essential uracil. For example: |--ft--| |-------br-------| GGGTTAAU CAAATTATAGCCATACAG IMPORTANT: Note that the entire sequence constitutes the primer. The space is simply added for illustrative purposes, and should be omitted when synthesizing the primers |
Achievements |
Comments or questions to the team? Please Email us -- Comments of questions to webmaster? Please Email us |