|
|
| (2 intermediate revisions by one other user not shown) |
| Line 1: |
Line 1: |
| − | {{METU_HS_Ankara}}
| |
| | <html> | | <html> |
| − | | + | <iframe src="http://www.metuhsigem15.com/#!project-description/x7kn5" width="100%" height="900" style="border:none"></iframe> |
| − | <h2> Project Description </h2>
| + | |
| − | <h2> Varroacula </h2>
| + | |
| − | | + | |
| − | <p>Our Project Varroacula, is about a parasitic disease called Varroasis. Varroasis is caused by Varroa destructor which is an external mite that attacks the honey bees Apis cerana and Apis mellifera.
| + | |
| − | This cause weight loss, deformities, diseases and reduction of life span. Hive collapses and/or colony loses are also major consequences of this disease. Beekeepers use variety of chemicals to battle with varroas. Those chemicals also effect the bee and decreases the quality of honey.
| + | |
| − | | + | |
| − | Our aim is to save the larvas from varroas.
| + | |
| − | By the usage of synthetic biology, our designe can repelle Varroa destructor out of the hive by using essential oils.. Essential oils contain mixtures of mostly volatile and odorous terpenoid constituents, they are more safer and have unfavorable effects on the environment. We hope that, with our designed prototype that contains modified E. Coli varroas will repel from hive just before their attack time.
| + | |
| − | .</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>
| + | |
| − | 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>
| + | |
| − | <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>
| + | |
| − | | + | |
| − | </div> | + | |
| | </html> | | </html> |