Difference between revisions of "Team:Michigan Software/Results"

 
(32 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{Michigan_Software}}
 
{{Michigan_Software}}
 
<html>
 
<html>
 +
<style>
 +
.list{
 +
color:#FCA708;
 +
font-weight:bold;
 +
}
  
−
<h2> Project Results</h2>
+
.NEW{
 +
float:left;
 +
width:40%;
 +
}
  
−
<p>Here you can describe the results of your project and your future plans. </p>
+
</style>
 +
<h1> Project Results</h1>
 +
<p>
 +
Protocat 2.0 is a crowd sourced catalog of protocol. Non-registered users can only search for and access the protocols stored in our database. On the other hand, registered users have access to Protocat 2.0's full capabilities. In addition to searching for protocol, registered users can upload and edit protocol of their own their own. Registered users can also rate and comment on others' protocol, generating feedback for the author about the efficacy of his/her protocol.
 +
</p>
 +
<center><img src="https://static.igem.org/mediawiki/2015/8/88/Team_Michigan_Software_Usage.png" width=500px /></center>
 +
<br><br>
 +
<div class="NEW">
 +
<h3> New Features in Protocat 2.0: </h3>
 +
<ul>
 +
<li>Refined search engine</li>
 +
<li>Protocol can be rated</li>
 +
<li>Protocol can be both sorted and reverse sorted</li>
 +
<li>Protocat users can register an account and have user pages</li>
 +
</ul>
 +
 
 +
<br>
  
−
<h5>What should this page contain?</h5>
+
<h3> Future Improvements </h3>
 
<ul>
 
<ul>
−
<li> Clearly and objectively describe the results of your work.</li>
+
<li>Implement version control</li>
−
<li> Future plans for the project </li>
+
<li>Implement variable protocol for limited supplies of reagents</li>
−
<li> Considerations for replicating the experiments </li>
+
<li>Implement experiment modeling</li>
 +
<li>Implement a timer for time-sensitive protocol</li>
 +
<li>Link users to reagent suppliers</li>
 +
<li>Grow protocat userbase and protocol repository</li>
 
</ul>
 
</ul>
 +
</div>
 +
<img src="https://static.igem.org/mediawiki/2015/8/83/Team_Michigan_Software_Improve.png" width=45%/>
  
  
 +
<h3> Medal Requirements</h3>
 +
<h4>Bronze</h4>
 +
<ul>
 +
<li>
 +
<i>Register for iGEM, have a great summer, and attend the Giant Jamboree.</i>
 +
<span class="list">DONE</span>
 +
</li>
  
 +
<li>
 +
<i>Complete the Judging form.</i>
 +
<span class="list">DONE</span>
 +
</li>
  
 +
<li>
 +
<i>Create and share a Description of the team's project using the iGEM wiki, and document the team's parts (if any) using the Registry of Standard Biological Parts.</i>
 +
<span class="list"><a href="https://2015.igem.org/Team:Michigan_Software/Description">DONE</a></span>
 +
</li>
  
−
<h4> Project Achievements </h4>
+
<li>
 +
<i>Present a poster and a talk at the iGEM Jamboree. See the 2015 poster guidelines for more information.</i>
 +
<span class="list">DONE</span>
 +
</li>
  
−
<p>You can also include a list of bullet points (and links) of the successes and failures you have had over your summer. It is a quick reference page for the judges to see what you achieved during your summer.</p>
+
<li>
 +
<i>Create a page on your team wiki with clear attribution of each aspect of your project. This page must clearly attribute work done by the students and distinguish it from work done by others, including host labs, advisors, instructors, sponsors, professional website designers, artists, and commercial services.</i>
 +
<a href="https://2015.igem.org/Team:Michigan_Software/Attribution">DONE</a>
 +
</li>
 +
 
 +
<li>
 +
<i>Develop and make available, via the iGEM GitHub page, an open source software that supports Synthetic Biology based on Standard Parts or interacts with the Registry.</i>
 +
<a href="https://github.com/igemsoftware/Michigan15"> DONE</a>
 +
</li>
  
−
<ul>
 
−
<li>A list of linked bullet points of the successful results during your project</li>
 
−
<li>A list of linked bullet points of the unsuccessful results during your project. This is about being scientifically honest. If you worked on an area for a long time with no success, tell us so we know where you put your effort.</li>
 
 
</ul>
 
</ul>
  
  
 +
<h4>Silver</h4>
 +
<ul>
 +
<li>
 +
<i>Provide a comprehensive, well-designed User Guide for your software and upload it to your wiki. Be creative! (An instructional video may work as well.)</i>
 +
<a href="https://2015.igem.org/Team:Michigan_Software/UserGuide">DONE</a>
 +
</li>
  
−
<h4> Further Improvements </h4>
+
<li>
−
<p> If we are to continue, what are things we are looking to improve> </p>
+
<i>Develop a well documented library or API for other developers (rather than "only" a stand-alone app for end users.)</i>  
 +
<a href="https://2015.igem.org/Team:Michigan_Software/Documentation">DONE</a>
 +
</li>
  
−
<h4>Inspiration</h4>
+
<li>
−
<p>See how other teams presented their results.</p>
+
<i>Demonstrate that you followed best practices 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, and documentation of releases and changes between releases.</i>  
 +
<span class="list">DONE <a href="https://github.com/igemsoftware/Michigan15">Code</a>and <a href="https://static.igem.org/mediawiki/2015/8/83/Team_Michigan_Software_TC.png">Test Coverage</a></span>
 +
</li>
 +
</ul>
 +
 
 +
 
 +
<h4>Gold</h4>
 
<ul>
 
<ul>
−
<li><a href="https://2014.igem.org/Team:TU_Darmstadt/Results/Pathway">2014 TU Darmstadt </a></li>
+
<li>
−
<li><a href="https://2014.igem.org/Team:Imperial/Results">2014 Imperial </a></li>
+
<i>iGEM projects involve important questions beyond the bench, for example relating to (but not limited to) ethics, sustainability, social justice, safety, security, and intellectual property rights. We refer to these activities as Human Practices in iGEM. Demonstrate how your team has identified, investigated and addressed one or more of these issues in the context of your project.</i>
−
<li><a href="https://2014.igem.org/Team:Paris_Bettencourt/Results">2014 Paris Bettencourt </a></li>
+
<a href="https://2015.igem.org/Team:Michigan_Software/Practices">DONE</a>
 +
</li>
 +
 
 +
<li>
 +
<i>Address a problem that you would like to co-develop with a wetlab team. This should be a collaboration where the wetlab team posts a problem they are having and your team addresses the issue by creating an online software solution.</i>
 +
<span class="list">Protocat was designed based on a <a href="https://2015.igem.org/Team:Michigan_Software/Practices">survey</a> we sent to lab teams.</span>
 +
</li>
 +
 
 +
<li>
 +
<i>Re-use and further develop a previous iGEM software project (or parts thereof) and demonstrate how future teams can continue this trend through good code documentation, use of open source materials and creation of great instructional materials.</i>
 +
<span class="list">We expanded upon <a href="https://2014.igem.org/Team:Michigan_Software">Michigan Software 2014's project.</a></span>
 +
</li>
 +
 
 +
<li>
 +
<i>Demonstrate your software at the iGEM Giant Jamboree in the software demo suite. You should show a functional prototype that teams can use in following years.</i>
 +
<span class="list">DONE</span>
 +
</li>
 
</ul>
 
</ul>
  
 
</div>
 
</div>
 
</html>
 
</html>

Latest revision as of 14:05, 18 September 2015


Michigan Software 2015

Project Results

Protocat 2.0 is a crowd sourced catalog of protocol. Non-registered users can only search for and access the protocols stored in our database. On the other hand, registered users have access to Protocat 2.0's full capabilities. In addition to searching for protocol, registered users can upload and edit protocol of their own their own. Registered users can also rate and comment on others' protocol, generating feedback for the author about the efficacy of his/her protocol.



New Features in Protocat 2.0:

  • Refined search engine
  • Protocol can be rated
  • Protocol can be both sorted and reverse sorted
  • Protocat users can register an account and have user pages

Future Improvements

  • Implement version control
  • Implement variable protocol for limited supplies of reagents
  • Implement experiment modeling
  • Implement a timer for time-sensitive protocol
  • Link users to reagent suppliers
  • Grow protocat userbase and protocol repository

Medal Requirements

Bronze

  • Register for iGEM, have a great summer, and attend the Giant Jamboree. DONE
  • Complete the Judging form. DONE
  • Create and share a Description of the team's project using the iGEM wiki, and document the team's parts (if any) using the Registry of Standard Biological Parts. DONE
  • Present a poster and a talk at the iGEM Jamboree. See the 2015 poster guidelines for more information. DONE
  • Create a page on your team wiki with clear attribution of each aspect of your project. This page must clearly attribute work done by the students and distinguish it from work done by others, including host labs, advisors, instructors, sponsors, professional website designers, artists, and commercial services. DONE
  • Develop and make available, via the iGEM GitHub page, an open source software that supports Synthetic Biology based on Standard Parts or interacts with the Registry. DONE

Silver

  • Provide a comprehensive, well-designed User Guide for your software and upload it to your wiki. Be creative! (An instructional video may work as well.) DONE
  • Develop a well documented library or API for other developers (rather than "only" a stand-alone app for end users.) DONE
  • Demonstrate that you followed best practices 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, and documentation of releases and changes between releases. DONE Codeand Test Coverage

Gold

  • iGEM projects involve important questions beyond the bench, for example relating to (but not limited to) ethics, sustainability, social justice, safety, security, and intellectual property rights. We refer to these activities as Human Practices in iGEM. Demonstrate how your team has identified, investigated and addressed one or more of these issues in the context of your project. DONE
  • Address a problem that you would like to co-develop with a wetlab team. This should be a collaboration where the wetlab team posts a problem they are having and your team addresses the issue by creating an online software solution. Protocat was designed based on a survey we sent to lab teams.
  • Re-use and further develop a previous iGEM software project (or parts thereof) and demonstrate how future teams can continue this trend through good code documentation, use of open source materials and creation of great instructional materials. We expanded upon Michigan Software 2014's project.
  • Demonstrate your software at the iGEM Giant Jamboree in the software demo suite. You should show a functional prototype that teams can use in following years. DONE