"
Team:HFUT CHINA/Medal.html
From 2014.igem.org
(Difference between revisions)
| (15 intermediate revisions not shown) | |||
| Line 39: | Line 39: | ||
<li><a href="https://2014.igem.org/Team:HFUT_CHINA/Overview.html">Overview</a></li> | <li><a href="https://2014.igem.org/Team:HFUT_CHINA/Overview.html">Overview</a></li> | ||
| - | <li><a href="https://2014.igem.org/Team:HFUT_CHINA/Examples.html"> | + | <li><a href="https://2014.igem.org/Team:HFUT_CHINA/Examples.html">Results</a></li> |
<li><a href="https://2014.igem.org/Team:HFUT_CHINA/Future_Work.html">Future Work</a></li> | <li><a href="https://2014.igem.org/Team:HFUT_CHINA/Future_Work.html">Future Work</a></li> | ||
| - | <li><a href="https:// | + | <li><a href="https://github.com/igemsoftware/HFUT_CHINA_2014">Download</a></li> |
</ul> | </ul> | ||
| Line 49: | Line 49: | ||
<ul> | <ul> | ||
<li><a href="https://2014.igem.org/Team:HFUT_CHINA/Devblogs.html">Devblogs</a></li> | <li><a href="https://2014.igem.org/Team:HFUT_CHINA/Devblogs.html">Devblogs</a></li> | ||
| - | <li><a href="https://2014.igem.org/Team:HFUT_CHINA/Database&Algorithm.html"> | + | <li><a href="https://2014.igem.org/Team:HFUT_CHINA/Database&Algorithm.html">Algorithm</a></li> |
| - | <li><a href="https://2014.igem.org/Team:HFUT_CHINA/ | + | <li><a href="https://2014.igem.org/Team:HFUT_CHINA/user_guide.html">Tutorial</a></li> |
| Line 121: | Line 121: | ||
<div> | <div> | ||
<div align="left"></div> | <div align="left"></div> | ||
| - | <table border="1" cellspacing="0" cellpadding="0" width="1106" style=" margin-right: auto; margin-left: auto;"> | + | <table border="1" cellspacing="0" cellpadding="0" width="1106" style=" margin-right: auto; margin-left: auto;background-color:#eee"> |
<tr> | <tr> | ||
<td width="184" valign="top"><p align="center"><strong> Bronze Medal:</strong> </p></td> | <td width="184" valign="top"><p align="center"><strong> Bronze Medal:</strong> </p></td> | ||
| Line 145: | Line 145: | ||
<td width="916"><p align="justify">Develop and make available via The Registry of Software Tools, an open source software tool that supports Synthetic Biology based on Standard Parts.</p> | <td width="916"><p align="justify">Develop and make available via The Registry of Software Tools, an open source software tool that supports Synthetic Biology based on Standard Parts.</p> | ||
<br> | <br> | ||
| - | <p><a href="https://igem.org/ | + | <p><a href="https://2014.igem.org/Team:HFUT_CHINA/readme">read more</a></p> |
<p align="justify"> </p></td> | <p align="justify"> </p></td> | ||
| Line 157: | Line 157: | ||
<td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td> | <td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td> | ||
<td width="916"><p align="justify">Demonstrate the relevance of your development for Synthetic Biology based on standard Parts. </p> | <td width="916"><p align="justify">Demonstrate the relevance of your development for Synthetic Biology based on standard Parts. </p> | ||
| + | <p><a href="https://2014.igem.org/Team:HFUT_CHINA/Judging_Form.html#a">read more</a></p> | ||
| + | |||
<p align="justify"> </p> </td> | <p align="justify"> </p> </td> | ||
</tr> | </tr> | ||
| Line 162: | Line 164: | ||
<td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td> | <td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td> | ||
<td width="916"><p align="justify">Provide a comprehensive and well-designed User Guide. (Be creative! An instructional video may work as well.)</p> | <td width="916"><p align="justify">Provide a comprehensive and well-designed User Guide. (Be creative! An instructional video may work as well.)</p> | ||
| + | <p><a href="https://2014.igem.org/Team:HFUT_CHINA/user_guide.html">read more</a></p> | ||
<p align="justify"> </p></td> | <p align="justify"> </p></td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td> | <td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td> | ||
| - | <td width="916"><p align="justify">Provide detailed API documentation, preferably, automatically built from source code documentation (use tools like doxygen, yard, rdoc, naturaldocs, etc).</p> | + | <td width="916"><p align="justify">Provide detailed API documentation, preferably, automatically built from source code documentation (use tools like doxygen, yard, rdoc, naturaldocs, etc).</p><a name="1"></a> |
| + | The detailed API documents could be downloaded from <a href="https://static.igem.org/mediawiki/2014/6/6f/HFUTFFUTAPI.zip | ||
| + | ">here.</a> | ||
<p align="justify"> </p></td> | <p align="justify"> </p></td> | ||
</tr> | </tr> | ||
| Line 173: | Line 178: | ||
<td width="916"><p align="justify">Demonstrate that you followed best practises in software development so that other developers can modify, use and reuse your code. Provide more than one realistic test case. Examples of best practices are automated unit testing and documentation of test coverage, bug tracking facilities, documentation of releases and changes between releases.</p> | <td width="916"><p align="justify">Demonstrate that you followed best practises in software development so that other developers can modify, use and reuse your code. Provide more than one realistic test case. Examples of best practices are automated unit testing and documentation of test coverage, bug tracking facilities, documentation of releases and changes between releases.</p> | ||
<br> | <br> | ||
| - | <p><a href="https://igem.org/ | + | <p><a href="https://2014.igem.org/Team:HFUT_CHINA/Unit_Test_Result.html">read more</a></p> </td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 183: | Line 188: | ||
<td width="184" valign="top"><div align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></div></td> | <td width="184" valign="top"><div align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></div></td> | ||
<td width="916"><p align="justify">Provide a convincing validation, testing the performance of the development -- experimentally (can be outsourced) or by other teams and users. Note, even if the algorithm or tool turns out not to work that well, the Gold requirement is fulfilled if the test is good and the analysis convincing. Validation may include: preferably experiments, informatics analysis (complexity, run time) of an algorithm, or user studies.</p> | <td width="916"><p align="justify">Provide a convincing validation, testing the performance of the development -- experimentally (can be outsourced) or by other teams and users. Note, even if the algorithm or tool turns out not to work that well, the Gold requirement is fulfilled if the test is good and the analysis convincing. Validation may include: preferably experiments, informatics analysis (complexity, run time) of an algorithm, or user studies.</p> | ||
| + | <p><a href="https://2014.igem.org/Team:HFUT_CHINA/Examples.html">read more</a></p> | ||
<p align="justify"> </p></td> | <p align="justify"> </p></td> | ||
</tr> | </tr> | ||
| Line 188: | Line 194: | ||
<td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td> | <td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td> | ||
<td width="916"><p align="justify">Make your software interact / interface with the Registry.</p> | <td width="916"><p align="justify">Make your software interact / interface with the Registry.</p> | ||
| + | <p><a href="https://2014.igem.org/Team:HFUT_CHINA/Judging_Form.html#c">read more</a></p> | ||
<p align="justify"> </p></td> | <p align="justify"> </p></td> | ||
</tr> | </tr> | ||
| Line 198: | Line 205: | ||
<td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td> | <td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td> | ||
<td width="916"><p align="justify">Develop a well documented library or API for other developers (rather than only a stand-alone app for end users.)</p> | <td width="916"><p align="justify">Develop a well documented library or API for other developers (rather than only a stand-alone app for end users.)</p> | ||
| + | <p><a href="https://2014.igem.org/Team:HFUT_CHINA/API.html">read more | ||
| + | </a>The detailed API documents could be downloaded from<a href="https://static.igem.org/mediawiki/2014/6/6f/HFUTFFUTAPI.zip "> here. | ||
| + | </a></p> | ||
<p align="justify"> </p></td> | <p align="justify"> </p></td> | ||
</tr> | </tr> | ||
| Line 203: | Line 213: | ||
<td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td> | <td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td> | ||
<td width="916"><p align="justify">Support and use the SBOL and / or SBOLv standard.</p> | <td width="916"><p align="justify">Support and use the SBOL and / or SBOLv standard.</p> | ||
| - | + | <p align="justify"> </p> | |
| + | <p align="justify"> > Since we need to visualize the device chains, we use SBOLv symbols to represent different types of biobricks. | ||
| + | </p> | ||
| + | <p align="justify"> </p> | ||
| + | <p align="justify"> </p> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 209: | Line 223: | ||
<td width="916"><p align="justify">iGEM projects involve important questions beyond the bench, for example relating to (but not limited to) ethics, sustainability, social justice, safety, security, or intellectual property rights. Describe an approach that your team used to address at least one of these questions. Evaluate your approach, including whether it allowed you to answer your question(s), how it influenced the team's scientific project, and how it might be adapted for others to use (within and beyond iGEM). We encourage thoughtful and creative approaches, and those that draw on past Policy & Practice (formerly Human Practices) activities.</p> | <td width="916"><p align="justify">iGEM projects involve important questions beyond the bench, for example relating to (but not limited to) ethics, sustainability, social justice, safety, security, or intellectual property rights. Describe an approach that your team used to address at least one of these questions. Evaluate your approach, including whether it allowed you to answer your question(s), how it influenced the team's scientific project, and how it might be adapted for others to use (within and beyond iGEM). We encourage thoughtful and creative approaches, and those that draw on past Policy & Practice (formerly Human Practices) activities.</p> | ||
<br> | <br> | ||
| - | <p><a href="https://igem.org/ | + | <p><a href="https://2014.igem.org/Team:HFUT_CHINA/Judging_Form.html#b">read more</a></p> |
| + | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
Latest revision as of 03:50, 18 October 2014
Medal
Bronze Medal: |
|
|
Register the team, have a great summer, and have fun attending the Giant Jamboree.
|
|
Create and share a description of the team's project via the iGEM wiki.
|
|
Present a Poster and Talk at the Giant Jamboree.
|
|
Develop and make available via The Registry of Software Tools, an open source software tool that supports Synthetic Biology based on Standard Parts.
|
Silver Medal:
|
|
|
Demonstrate the relevance of your development for Synthetic Biology based on standard Parts.
|
|
Provide a comprehensive and well-designed User Guide. (Be creative! An instructional video may work as well.)
|
|
Provide detailed API documentation, preferably, automatically built from source code documentation (use tools like doxygen, yard, rdoc, naturaldocs, etc). The detailed API documents could be downloaded from here.
|
|
Demonstrate that you followed best practises in software development so that other developers can modify, use and reuse your code. Provide more than one realistic test case. Examples of best practices are automated unit testing and documentation of test coverage, bug tracking facilities, documentation of releases and changes between releases. |
Gold Medal:
|
|
 |
Provide a convincing validation, testing the performance of the development -- experimentally (can be outsourced) or by other teams and users. Note, even if the algorithm or tool turns out not to work that well, the Gold requirement is fulfilled if the test is good and the analysis convincing. Validation may include: preferably experiments, informatics analysis (complexity, run time) of an algorithm, or user studies.
|
|
Make your software interact / interface with the Registry.
|
|
Re-use and further develop previous iGEM software projects (or parts thereof) or use and/or improvement of existing synthetic biology tools or frameworks.
|
|
Develop a well documented library or API for other developers (rather than only a stand-alone app for end users.) read more The detailed API documents could be downloaded from here.
|
|
Support and use the SBOL and / or SBOLv standard.
> Since we need to visualize the device chains, we use SBOLv symbols to represent different types of biobricks.
|
|
iGEM projects involve important questions beyond the bench, for example relating to (but not limited to) ethics, sustainability, social justice, safety, security, or intellectual property rights. Describe an approach that your team used to address at least one of these questions. Evaluate your approach, including whether it allowed you to answer your question(s), how it influenced the team's scientific project, and how it might be adapted for others to use (within and beyond iGEM). We encourage thoughtful and creative approaches, and those that draw on past Policy & Practice (formerly Human Practices) activities. |
