Team:UESTC-Software/Medal.html
From 2014.igem.org
Tangying0608 (Talk | contribs) (Created page with "{{CSS/Main}} <html> <head> <title>UESTC-Software</title> <meta http-equiv=Content-Type content="text/html;charset=utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge,c...") |
Tangying0608 (Talk | contribs) |
||
(12 intermediate revisions not shown) | |||
Line 13: | Line 13: | ||
<div class="midBoard" style="padding-bottom:80px;"> | <div class="midBoard" style="padding-bottom:80px;"> | ||
<div class="parts gold medal" style="padding: 20px 50px 20px 100px;background-color: #FFFBD3;"> | <div class="parts gold medal" style="padding: 20px 50px 20px 100px;background-color: #FFFBD3;"> | ||
- | <h1 style="color: #8fc41f;">Gold Medal</h1><img src="https://static.igem.org/mediawiki/2014/2/2d/2014-iGEM-UESTC-SoftwareGold.png"> | + | <h1 style="color: #8fc41f !important;">Gold Medal</h1><img src="https://static.igem.org/mediawiki/2014/2/2d/2014-iGEM-UESTC-SoftwareGold.png"> |
+ | <p class="no-indent no-bg"> In addition to the Bronze and Silver Medal requirements, two additional goals must be achieved:</p> | ||
<p class="no-indent">1.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 class="no-indent">1.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> We have provided a convincing validation in the validation of our wiki.<a href="https://2014.igem.org/Team:UESTC-Software/Validation.html">https://2014.igem.org/Team:UESTC-Software/Validation.html</a></p> | <p> We have provided a convincing validation in the validation of our wiki.<a href="https://2014.igem.org/Team:UESTC-Software/Validation.html">https://2014.igem.org/Team:UESTC-Software/Validation.html</a></p> | ||
</div> | </div> | ||
<div class="parts gold medal" style="padding: 20px 50px 20px 100px;overflow:hidden;background-color: #FFFBD3;"> | <div class="parts gold medal" style="padding: 20px 50px 20px 100px;overflow:hidden;background-color: #FFFBD3;"> | ||
- | <p class="no-indent"> | + | <p class="no-indent no-bg">And the second goal can be any one of the following:</p> |
- | + | <p class="no-indent no-bg">1.Make your software interact / interface with the Registry.</p> | |
- | + | <p class="no-indent no-bg">2.Re-use and further develop previous iGEM software projects (or parts thereof) or use and/or improvement of existing synthetic biology tools or frameworks.</p> | |
- | + | ||
<p class="no-indent">3.Develop a well documented library or API for other developers (rather than “only” a stand-alone app for end users.)</p> | <p class="no-indent">3.Develop a well documented library or API for other developers (rather than “only” a stand-alone app for end users.)</p> | ||
- | + | <p> Please visit <a href="https://2014.igem.org/Team:UESTC-Software/API.html">https://2014.igem.org/Team:UESTC-Software/API.html</a>.</p> | |
- | + | ||
<p class="no-indent">4.Support and use the SBOL and / or SBOLv standard. </p> | <p class="no-indent">4.Support and use the SBOL and / or SBOLv standard. </p> | ||
+ | <p class="no-indent no-bg">5.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> | ||
</div> | </div> | ||
- | + | ||
- | + | ||
- | + | ||
<div class="parts silver medal" style="padding: 20px 50px 20px 100px;overflow:hidden;"> | <div class="parts silver medal" style="padding: 20px 50px 20px 100px;overflow:hidden;"> | ||
- | <h1 style="color: #81C7E2;">Silver Medal</h1><img src="https://static.igem.org/mediawiki/2014/2/2e/2014-iGEM-UESTC-Software-Silver.png"> | + | <h1 style="color: #81C7E2 !important;">Silver Medal</h1><img src="https://static.igem.org/mediawiki/2014/2/2e/2014-iGEM-UESTC-Software-Silver.png"> |
<p class="no-indent">1.Demonstrate the relevance of your development for Synthetic Biology based on standard Parts. </p> | <p class="no-indent">1.Demonstrate the relevance of your development for Synthetic Biology based on standard Parts. </p> | ||
<p>We have demonstrated the relevance of our development for Synthetic Biology based on standard Parts in the overview of our wiki. Please visit <a href="https://2014.igem.org/Team:UESTC-Software/Overview.html">https://2014.igem.org/Team:UESTC-Software/Overview.html</a>.</p> | <p>We have demonstrated the relevance of our development for Synthetic Biology based on standard Parts in the overview of our wiki. Please visit <a href="https://2014.igem.org/Team:UESTC-Software/Overview.html">https://2014.igem.org/Team:UESTC-Software/Overview.html</a>.</p> | ||
Line 45: | Line 43: | ||
<div class="parts silver medal" style="padding: 20px 50px 20px 100px;overflow:hidden;"> | <div class="parts silver medal" style="padding: 20px 50px 20px 100px;overflow:hidden;"> | ||
<p class="no-indent">4.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> | <p class="no-indent">4.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> | ||
- | <p>We used many modern software CI, such as Travis CI and coveralls. In details, please visit | + | <p>We used many modern software CI, such as Travis CI and coveralls. In details, please visit <a href="https://2014.igem.org/Team:UESTC-Software/Overview.html#p6">https://2014.igem.org/Team:UESTC-Software/Overview.html#p6</a></p> |
</div> | </div> | ||
<div class="parts bronze medal" style="padding: 20px 50px 20px 100px;"> | <div class="parts bronze medal" style="padding: 20px 50px 20px 100px;"> | ||
- | <h1 style="color: #9789CE;">Bronze Medal</h1><img src="https://static.igem.org/mediawiki/2014/3/31/2014-iGEM-UESTC-Software-Bronze.png"> | + | <h1 style="color: #9789CE !important;">Bronze Medal</h1><img src="https://static.igem.org/mediawiki/2014/3/31/2014-iGEM-UESTC-Software-Bronze.png"> |
<p class="no-indent">1.Register the team, have a great summer, and have fun attending the Jamboree in Boston.</p> | <p class="no-indent">1.Register the team, have a great summer, and have fun attending the Jamboree in Boston.</p> | ||
</div> | </div> | ||
Line 72: | Line 70: | ||
<div class="navbar"> | <div class="navbar"> | ||
<ul class="leftUl UL"> | <ul class="leftUl UL"> | ||
- | <li id="nav_home"></li> | + | <li id="nav_home"><a href="Home.html" style="width: inherit;height: 100%;position: fixed;"></a></li> |
<li id="nav_project" class="menu"> | <li id="nav_project" class="menu"> | ||
- | <ul style="bottom: | + | <ul style="bottom:257px;"> |
<li><a href="Overview.html">Overview</a></li> | <li><a href="Overview.html">Overview</a></li> | ||
<li><a href="Modeling.html">Modeling</a></li> | <li><a href="Modeling.html">Modeling</a></li> | ||
<li><a href="Demo.html">Demo</a></li> | <li><a href="Demo.html">Demo</a></li> | ||
<li><a href="Validation.html">Validation</a></li> | <li><a href="Validation.html">Validation</a></li> | ||
- | |||
<li><a href="Download.html">Download</a></li> | <li><a href="Download.html">Download</a></li> | ||
- | <li><a href=" | + | <li><a href="safety.html">Safety</a></li> |
</ul> | </ul> | ||
</li> | </li> | ||
- | <li id="nav_team"><a href=" | + | <li id="nav_team"><a href="team.html" style="width: inherit;height: 100%;position: fixed;"></a></li> |
</ul> | </ul> | ||
<ul class="rightUl UL"> | <ul class="rightUl UL"> | ||
<li id="nav_notebk" class="menu"> | <li id="nav_notebk" class="menu"> | ||
<ul style="bottom:90px;"> | <ul style="bottom:90px;"> | ||
- | <li><a href=" | + | <li><a href="journal.html">Journal</a></li> |
- | <li><a href="HumanPractice.html">Human | + | <li><a href="HumanPractice.html">Human Practice</a></li> |
</ul> | </ul> | ||
</li> | </li> | ||
<li id="nav_reqrmt" class="menu"> | <li id="nav_reqrmt" class="menu"> | ||
- | <ul style="bottom: | + | <ul style="bottom:93px;"> |
- | <li><a href=" | + | <li><a href="Requirement.html">Requirements</a></li> |
- | <li><a href=" | + | <li><a href="Medal.html">Medal Fulfillment</a></li> |
- | + | ||
</ul> | </ul> | ||
</li> | </li> | ||
<li id="nav_doc" class="menu"> | <li id="nav_doc" class="menu"> | ||
<ul style="bottom:170px;"> | <ul style="bottom:170px;"> | ||
- | <li><a href=" | + | <li><a href="API.html">API Documentation</a></li> |
- | <li><a href=" | + | <li><a href="Testing.html">Testing Documentation</a></li> |
<li><a href="Installation.html">Installation</a></li> | <li><a href="Installation.html">Installation</a></li> | ||
<li><a href="UserGuide.html">User Guide</a></li> | <li><a href="UserGuide.html">User Guide</a></li> | ||
Line 112: | Line 108: | ||
<img src="https://static.igem.org/mediawiki/2014/c/c5/2014-UESTC-Software-Top.png" id="top" onclick="javascript:$('#body').animate({scrollTop:0},700)"> | <img src="https://static.igem.org/mediawiki/2014/c/c5/2014-UESTC-Software-Top.png" id="top" onclick="javascript:$('#body').animate({scrollTop:0},700)"> | ||
<div id="logoRay" style="width:86px;height:86px;border-radius:1000px;position:fixed;bottom:-20px;z-index: 999999;"></div> | <div id="logoRay" style="width:86px;height:86px;border-radius:1000px;position:fixed;bottom:-20px;z-index: 999999;"></div> | ||
- | <img src="https://static.igem.org/mediawiki/2014/e/e5/2014_UESTC_Software_logo.gif" id="logo" style="border-radius: 90px;width:100px;height:100px;position:fixed;bottom:-20px;z-index: 999999;"/> | + | <a href="https://2014.igem.org/Team:UESTC-Software"><img src="https://static.igem.org/mediawiki/2014/e/e5/2014_UESTC_Software_logo.gif" id="logo" style="border-radius: 90px;width:100px;height:100px;position:fixed;bottom:-20px;z-index: 999999;"/></a> |
- | </ | + | <a class="iGEM" href="https://2014.igem.org/Main_Page" style="position: fixed;top: 0;right: 0;"><img src="https://static.igem.org/mediawiki/2014/8/8d/2014-UESTC-Software-Igem.png"></a> |
- | < | + | |
- | + | ||
- | + | ||
</div> | </div> | ||
+ | |||
<script type="text/javascript"> | <script type="text/javascript"> | ||
function resizeWindow(){ | function resizeWindow(){ | ||
Line 129: | Line 123: | ||
"overflow-y":"auto", | "overflow-y":"auto", | ||
"position":"absolute", | "position":"absolute", | ||
+ | }); | ||
+ | $("body").css({ | ||
+ | "height":winHeight/2+"px", | ||
}); | }); | ||
$("#logo").css({ | $("#logo").css({ | ||
Line 143: | Line 140: | ||
$(document).ready(function(){ | $(document).ready(function(){ | ||
var winWidth = window.innerWidth; | var winWidth = window.innerWidth; | ||
- | |||
- | |||
resizeWindow(); | resizeWindow(); | ||
- | |||
- | |||
//Navigation (in document.ready) | //Navigation (in document.ready) | ||
$("#top").click(function(){ | $("#top").click(function(){ | ||
Line 153: | Line 146: | ||
return false; | return false; | ||
}); | }); | ||
- | + | $(".menu").on("mouseenter",function(){ | |
- | + | $(this.children).fadeIn(200); | |
- | + | }); | |
- | + | $(".menu").on("mouseleave",function(){ | |
- | + | $(this.children).fadeOut(200); | |
- | + | }); | |
- | + | ||
- | + | ||
- | + | ||
}); | }); | ||
window.onresize = resizeWindow; | window.onresize = resizeWindow; |
Latest revision as of 16:24, 15 October 2014
Gold Medal
In addition to the Bronze and Silver Medal requirements, two additional goals must be achieved:
1.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.
We have provided a convincing validation in the validation of our wiki.https://2014.igem.org/Team:UESTC-Software/Validation.html
Bronze Medal
1.Register the team, have a great summer, and have fun attending the Jamboree in Boston.
2.Create and share a description of the team's project via the iGEM wiki.
3.Present a Poster and Talk at the Regional Jamboree and World Championship Jamboree.
4.Develop and make available via The Registry of Software Tools, an open source software tool that supports Synthetic Biology based on Standard Parts.
Our software supports RFC [10], RFC [12], RFC [21], RFC [23] and RFC [25].