|
|
| Line 3: |
Line 3: |
| | | | |
| | <h2> Project Description </h2> | | <h2> Project Description </h2> |
| − |
| |
| − | <p> <a href="https://2015.igem.org/wiki/index.php?title=Team:UMaryland/Description&action=edit"> Click here to edit this page! </a></p>
| |
| − |
| |
| − | <p>Tell us about your project, describe what moves you and why this is something important for your team.</p>
| |
| − | <br />
| |
| − |
| |
| − | <h5>What should this page contain?</h5>
| |
| − | <ul>
| |
| − | <li> A clear and concise description of your project.</li>
| |
| − | <li>A detailed explanation of why your team chose to work on this particular project.</li>
| |
| − | <li>References and sources to document your research.</li>
| |
| − | <li>Use illustrations and other visual resources to explain your project.</li>
| |
| − | </ul>
| |
| − |
| |
| − |
| |
| − | <br />
| |
| − | <h4>Advice on writing your Project Description</h4>
| |
| | | | |
| | <p> | | <p> |
| − | We encourage you to put up a lot of information and content on your wiki, but we also encourage you to include summaries as much as possible. If you think of the sections in your project description as the sections in a publication, you should try to be consist, accurate and unambiguous in your achievements.
| |
| − | </p>
| |
| − |
| |
| − | <p>
| |
| − | Judges like to read your wiki and know exactly what you have achieved. This is how you should think about these sections; from the point of view of the judge evaluating you at the end of the year.
| |
| − | </p>
| |
| − |
| |
| − |
| |
| − | <br />
| |
| − | <h4>References</h4>
| |
| − | <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>
| |
| − |
| |
| − |
| |
| − |
| |
| − | <h4>Inspiration</h4>
| |
| − | <p>See how other teams have described and presented their projects: </p>
| |
| | | | |
| − | <ul>
| + | Lutein is a dietary supplement used as both a treatment and preventative measure for Age-Related Macular Degeneration. Our primary research focus is to combat AMD through lutein production. Lutein is currently extracted from the petals of marigolds, but we hope to create a more cost-effective and efficient way of synthesizing this carotenoid via bacterial pathways. Our goal is to optimize the production of lutein through the careful manipulation of promoters for various enzymes, not native to E. Coli, in the lutein pathway. This pathway begins with lycopene, which is then converted to alpha-carotene with the addition of epsilon- and then beta-cyclase. Alpha-carotene is then converted to lutein through epsilon- and beta-hydroxylase. In order to ensure that we are producing alpha carotene instead of beta carotene, we will be manipulating the regulation of epsilon and beta cyclase by testing various promoter pairings. We will then use this data to help model the synthetic pathway and hopefully create a user friendly tool to help iGEM teams in the future model synthetic projects. |
| − | <li><a href="https://2014.igem.org/Team:Imperial/Project"> Imperial</a></li>
| + | |
| − | <li><a href="https://2014.igem.org/Team:UC_Davis/Project_Overview"> UC Davis</a></li>
| + | |
| − | <li><a href="https://2014.igem.org/Team:SYSU-Software/Overview">SYSU Software</a></li>
| + | |
| − | </ul>
| + | |
| | | | |
| | + | </p> |
| | + | </div> |
| | + | </div> |
| | + | </div> |
| | </div> | | </div> |
| | </html> | | </html> |
