(Prototype team page) |
|||
Line 7: | Line 7: | ||
<h1>Description</h1> | <h1>Description</h1> | ||
− | <p> | + | <p>We aim to develop a local biological system alignment software.</p> |
+ | <p>When we are studying sequences, we always want to look for similar sequences to help us learn more about the target sequence. </p> | ||
+ | <p>Similarly, when we are studying biological system, we can also start with looking for similar systems. Thus, we want to develop a software like BLAST, but its target is biological system instead of sequences. </p> | ||
</div> | </div> |
Revision as of 02:21, 30 June 2018
Description
We aim to develop a local biological system alignment software.
When we are studying sequences, we always want to look for similar sequences to help us learn more about the target sequence.
Similarly, when we are studying biological system, we can also start with looking for similar systems. Thus, we want to develop a software like BLAST, but its target is biological system instead of sequences.
What should this page contain?
- A clear and concise description of your project.
- A detailed explanation of why your team chose to work on this particular project.
- References and sources to document your research.
- Use illustrations and other visual resources to explain your project.
Inspiration
See how other teams have described and presented their projects:
Advice on writing your Project Description
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 concise, accurate, and unambiguous in your achievements.
References
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 thought about your project and what works inspired you.