Team:Gifu/Project
From 2014.igem.org
(30 intermediate revisions not shown) | |||
Line 2: | Line 2: | ||
- | {{CSS/ | + | {{:CSS/gifu/main}} |
+ | {{:CSS/gifu/project}} | ||
+ | {{:gifu/head}} | ||
Line 11: | Line 13: | ||
- | < | + | <style type="text/css"> |
- | + | <!-- | |
- | + | ||
- | < | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | #main | |
- | + | { | |
- | + | margin-left:auto; | |
+ | margin-right:auto; | ||
+ | text-align:left; | ||
+ | width:70%; | ||
+ | background-color:#f0f8ff; | ||
- | + | ||
- | + | } | |
- | + | .abc | |
- | + | { | |
- | + | font-size:large; | |
+ | font-family:Calibri; | ||
+ | background-color:#f0f8ff | ||
+ | } | ||
+ | --> | ||
+ | </style> | ||
- | |||
- | |||
- | < | + | <!--Comic Sans MS --> |
- | + | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
+ | <!--end navigation menu --> | ||
+ | |||
+ | <br><br><br><br><br><br><br><br> | ||
<!--Project content --> | <!--Project content --> | ||
- | < | + | <div id="main"> |
- | < | + | <h3 style="font-family:Comic Sans MS;font-size:x-large"> Project Description </h3> |
- | + | <p class="abc">Tell us more about your project. Give us background. Use this as the abstract of your project. Be descriptive but concise (1-2 paragraphs) </p> | |
- | + | ||
+ | |||
+ | |||
- | < | + | <h3 style="font-family:Comic Sans MS;font-size:x-large">References </h3> |
- | + | <p class="abc"> | |
- | + | ||
- | + | ||
- | + | ||
- | <p> | + | |
iGEM teams are encouraged to record references you use during the course of your research. They should be posted somewhere on your wiki so that judges and other visitors can see how you though about your project and what works inspired you. </p> | iGEM teams are encouraged to record references you use during the course of your research. They should be posted somewhere on your wiki so that judges and other visitors can see how you though about your project and what works inspired you. </p> | ||
- | |||
- | |||
- | |||
- | |||
- | <ol> | + | <h3 style="font-family:Comic Sans MS;font-size:x-large"> Content</h3> |
+ | <p class="abc"> You can use these subtopics to further explain your project</p> | ||
+ | |||
+ | <ol class="abc"> | ||
<li><a href="#summary">Overall project summary</a></li> | <li><a href="#summary">Overall project summary</a></li> | ||
<li><a href="#details">Project Details</a></li> | <li><a href="#details">Project Details</a></li> | ||
Line 106: | Line 83: | ||
</ol> | </ol> | ||
- | <p> | + | <p class="abc"> |
It's important for teams to describe all the creativity that goes into an iGEM project, along with all the great ideas your team will come up with over the course of your work. | It's important for teams to describe all the creativity that goes into an iGEM project, along with all the great ideas your team will come up with over the course of your work. | ||
</p> | </p> | ||
- | <p> | + | <p class="abc"> |
It's also important to clearly describe your achievements so that judges will know what you tried to do and where you succeeded. Please write your project page such that what you achieved is easy to distinguish from what you attempted. | It's also important to clearly describe your achievements so that judges will know what you tried to do and where you succeeded. Please write your project page such that what you achieved is easy to distinguish from what you attempted. | ||
</p> | </p> | ||
- | |||
- | |||
- | + | <h1 style="font-family:Comic Sans MS;font-size:x-large"><a name="summary"><font color="black">Overall project summary</font></a></h1> | |
- | <h1><a name="summary">Overall project summary</a></h1> | + | |
<p></p> | <p></p> | ||
- | <h1><a name="details">Project Details</a></h1> | + | <h1 style="font-family:Comic Sans MS;font-size:x-large" ><a name="details"><font color="black">Project Details</font></a></h1> |
<p></p> | <p></p> | ||
- | <h1><a name="progress">Progress</a></h1> | + | <h1 style="font-family:Comic Sans MS;font-size:x-large" ><a name="progress"><font color="black">Progress</font></a></h1> |
<p></p> | <p></p> | ||
- | <h1><a name="M&M">Materials and Methods</a></h1> | + | <h1 style="font-family:Comic Sans MS;font-size:x-large" ><a name="M&M"><font color="black">Materials and Methods</font></a></h1> |
<p></p> | <p></p> | ||
- | <h1><a name="experiments">The Experiments</a></h1> | + | <h1 style="font-family:Comic Sans MS;font-size:x-large" ><a name="experiments"><font color="black">The Experiments</font></a></h1> |
<p></p> | <p></p> | ||
- | <h1><a name="results">Results</a></h1> | + | <h1 style="font-family:Comic Sans MS;font-size:x-large"><a name="results"><font color="black">Results</font></a></h1> |
<p></p> | <p></p> | ||
- | <h1><a name="analysis">Data analysis</a></h1> | + | <h1 style="font-family:Comic Sans MS;font-size:x-large"><a name="analysis"><font color="black">Data analysis</font></a></h1> |
<p></p> | <p></p> | ||
- | <h1><a name="conclusions">Conclusions</a></h1> | + | <h1 style="font-family:Comic Sans MS;font-size:x-large"><a name="conclusions"><font color="black">Conclusions</font></a></h1> |
<p></p> | <p></p> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | <h2 style="font-family:Comic Sans MS;font-size:x-large">Theme of our project</h2> | ||
+ | |||
+ | <ol type="1" class="abc"> | ||
+ | <li> | ||
+ | <p class="abc">Transform new year's card to rice cake | ||
+ | (make cellulose resolve and reconstruct it to synthesize amylopectin) | ||
+ | </p> | ||
+ | </li> | ||
+ | <li> | ||
+ | <p class="abc">RNA shaped like a ring / ring-shaped RNA | ||
+ | (mass-produce protein by ring-shaped RNA) | ||
+ | </p> | ||
+ | </li> | ||
+ | </ol> | ||
+ | |||
+ | |||
+ | |||
+ | <h2 style="font-family:Comic Sans MS;font-size:x-large">Description</h2> | ||
+ | |||
+ | |||
+ | <ol type="1" class"abc"> | ||
+ | <li class="abc"> | ||
+ | <p class="abc">In vivo, proteins are synthesized in transcription and translation. | ||
+ | Generally, mRNA is single-strand RNA, starting translation by binding ribosome on initiation codon, and ending by separating ribosome from mRNA. | ||
+ | In this study, we aim to build the method of synthesizing long-chain, massive proteins and to improve translation efficiency. | ||
+ | That is, allowing ribosomes to have a semi-permanent translation mechanism by producing circular mRNA and causing a defect of termination codon. | ||
+ | To cyclize mRNA, we can use a splicing mechanism of T4 phage. | ||
+ | Splicing is a mechanism removing circular introns which don't code for proteins and joining in exons which code for ones. | ||
+ | It occurs after transcription. | ||
+ | Splicing is catalyzed by several base sequences of the ends of introns as a ribozyme, being subjected to nucleophilic attack from introns to exons. | ||
+ | So we will introduce the plasmids which place the sequence of the end of introns as a splicing ribozyme on the end of a gene coding for proteins into E.coli, and cyclize mRNA for | ||
+ | synthesis of long-chain, massive proteins. | ||
+ | </p> | ||
+ | </li> | ||
+ | </ol> | ||
+ | |||
+ | </div> | ||
+ | </body> | ||
+ | |||
</html> | </html> |
Latest revision as of 08:11, 29 August 2014