|
|
| Line 27: |
Line 27: |
| | <h3> General Requirements </h3> | | <h3> General Requirements </h3> |
| | | | |
| − | <p>All iGEM teams must meet the following requirements to participate in the 2015 competition. Additional requirements specific to New Track teams are listed in the section below.</p> | + | <p>All iGEM teams must meet the following requirements to participate in the 2015 competition.</p> |
| | | | |
| | <ol id="reqlist"> | | <ol id="reqlist"> |
| Line 88: |
Line 88: |
| | | | |
| | | | |
| − | <h3> <a id="NewTrackRequirements"> </a> New Track Requirements </h3>
| |
| − | <ol id="reqlist">
| |
| | | | |
| − | <li style="padding-bottom:15px;">
| + | <h3> <a id="NewTrackRequirements"> </a> Additional Requirements </h3> |
| − | <h3><a id ="artdesign" class="anchor"></a>Art and Design:</h3> | + | In addition to compelting the requirements listed above, the following special cases apply: |
| | | | |
| − | <p> | + | <h4>High School</h4> |
| − | Art and Design teams, please see the <a href= "https://2015.igem.org/ Tracks/ Art_Design"> Art and Design page</a>. In addition the the general requirements for all iGEM teams listed above, Art and Design teams are required to complete the following: | + | All high school track participants must submit the appropriate <a href="https://2015.igem.org/ Requirements/ Consent"> consent forms</a>. Consent forms are required from all high school track participants including instructors, advisors, students, and others. <small><a href="https: //2015.igem.org/More/Consent_Forms">Why?</a></ small> |
| − | </p> | + | |
| | | | |
| − | <ul>
| |
| − | <li><strong>Team Composition</strong> While iGEM is primarily a student competition, we acknowledge that there may be artists and designers who are interested in participating and who do not have a university affiliation. We strongly recommend that artists interested in participating with a team or forming their own iGEM team find team members and advisors from local universities or <a href="https://2015.igem.org/Tracks/Community_Labs">community labs</a>. This is an experimental track, so please contact us at artdesign AT igem.org with any questions or concerns about participation and team requirements. </li>
| |
| − |
| |
| − | <li><strong>Project Presentation:</strong> Each team must give a twenty minute presentation discussing their project at the Jamboree, including description of goals, process, and outcomes. In addition, teams must present a poster during the Jamboree poster sessions. Please feel free to bring any additional materials that support the presentation of your projects. Special presentation requirements (e.g. video screening, installations) can be arranged on a case by case basis (deadline for special requests: TBD). Please contact artdesign AT igem.org with questions.</li>
| |
| − |
| |
| − | <li><strong>BioBrick Parts:</strong>Teams participating in the Art and Design tracks are strongly encouraged to work with the materials of synthetic biology, including BioBrick parts, although it is not a strict requirement. To receive a distribution copy of the parts registry, teams must request one from artdesign AT igem.org and have an affiliated university or community laboratory and follow all safety regulations. Teams that do wish to use and submit a new part must adhere to <a href="https://2015.igem.org/Safety"> safety </a> and <a href="http://parts.igem.org/cgi/dna_transfer/index.cgi"> iGEM submission guidelines</a>. </li>
| |
| − | </ul>
| |
| − |
| |
| − | <li style="padding-bottom:15px;">
| |
| − | <h3><a id ="communitylabs" class="anchor"></a>Community Labs:</h3>
| |
| − |
| |
| − | <p>
| |
| − | Community Lab teams please see the <a href="https://2015.igem.org/Tracks/Community_Labs"> Community Labs New Track page </a>. In addition the the general requirements for all iGEM teams listed above, Community Lab teams are required to complete the following:
| |
| − | </p>
| |
| − |
| |
| − | <ul>
| |
| − | <li>
| |
| − | Team composition. While there is no minimum number of team members, iGEM is a team competition and single individual entries will not be accepted. CL teams must have two advisors, one of which must be in the field of their chosen subject area.
| |
| − | </li>
| |
| − |
| |
| − | <li>
| |
| − | Community Lab teams must demonstrate they have access to a BL 1 lab in order to receive a copy of the distribution.
| |
| − | </li>
| |
| − |
| |
| − | <li>
| |
| − | Teams participating in the hardware aspect of the CL track are encouraged to bring their equipment to the Giant Jamboree. Teams may not bring live or inactive organisms as part of their equipment. This topic will be covered in more detail when evaluation criteria and awards are published.
| |
| − | </li>
| |
| − | </ul>
| |
| − |
| |
| − | <p>
| |
| − | As Community Lab teams are not operating within the framework offered by academic institutions, they must meet the following additional requirements:
| |
| − | </p>
| |
| − |
| |
| − | <ol>
| |
| − | <li>
| |
| − | CL teams must be an incorporated entity (for profit or not-for-profit).
| |
| − | </li>
| |
| − |
| |
| − | <li>
| |
| − | CL teams must have a legal entity that has the ability to sign contracts.
| |
| − | </li>
| |
| − | </ol>
| |
| − |
| |
| − | <li style="padding-bottom:15px;">
| |
| − | <h3><a id ="measurement" class="anchor"></a>Measurement:</h3>
| |
| − |
| |
| − | <p>
| |
| − | Measurement teams, please see the <a href="https://2015.igem.org/Tracks/Measurement">Measurement New Track page</a>. In addition the the general requirements for all iGEM teams listed above, Measurement teams are required to complete the following: </h4>
| |
| − | </p>
| |
| − |
| |
| − | <ul>
| |
| − | <li><strong>Interlab Measurement Study:</strong>
| |
| − | For the Measurement Track, it is also important to submit data taken for the <a href="https://2015.igem.org/Tracks/Measurement/Interlab_study">Interlab Study</a>. Data should be uploaded to the iGEM interlab measurement site, along with accompanying metrology worksheets. Data will not be considered if it is uploaded without an accompanying worksheet or if the worksheet does not give consent for inclusion of the data in the interlab study.</li>
| |
| − | <li><strong>Software Submission:</strong>
| |
| − | If your team's entry includes the development of new software, you must make your software tools available as open source projects on the iGEM servers.</li>
| |
| − | </ul>
| |
| − |
| |
| − |
| |
| − | <ul>
| |
| − | <li><strong>Developing your iGEM Policy & Practices Team:</strong>
| |
| − |
| |
| − | <ul>
| |
| − | <li> <strong>Faculty Advisors:</strong> Each team must work with at least two senior mentors. One of the senior mentors must be a faculty member. One mentor should be based in the humanities or social sciences (for example, law, economics, sociology, public policy), and one from any other discipline including, but not limited to, science, engineering, social sciences, medicine, and law. Additional faculty members may also be listed as faculty advisors. One faculty member must be designated as the primary faculty advisor. She or he is ultimately responsible for the official registration of the team, the team roster, and payment of team fees.
| |
| − |
| |
| − | <li><strong>Advisors:</strong> In addition to the required roles above, teams are encouraged to recruit non-faculty advisors. These can include postgraduate students and postdoctoral researchers, as well as current or former policymakers, government officials, legal advisors, entrepreneurs, or members of non-governmental organizations, regulatory agencies or funding bodies.
| |
| − |
| |
| − | <li><strong>Questions?</strong> This is an experimental track, so please contact us at policypractices AT igem.org if you have any questions or concerns about participation and team requirements.
| |
| − | </ul>
| |
| − |
| |
| − | <li><strong>Project Submissions:</strong>
| |
| − |
| |
| − | <p>
| |
| − | Team submissions are required to convey (1) the project inspiration, (2) clearly articulated question(s) the project proposes to address, (3) detailed method(s) used (and their assumptions), (4) discussion of the challenges encountered in pursuing this work, (5) an explanation of who the project findings should be of interest to and why, and (6) an explanation of how the approach(es) might be adapted and scaled for others to use.
| |
| − | </p>
| |
| − |
| |
| − | <p>
| |
| − | These questions should be addressed in the following ways, in addition to the standard wiki, poster and presentation requirements for all iGEM teams. [Please note that these requirements are subject to revision until medal criteria are announced]:
| |
| − | </p>
| |
| − |
| |
| − | <ul>
| |
| − | <li> A 2-page executive summary (that can reference additional resources on your wiki) </li>
| |
| − | <li> A 3-minute video that is accessible to an interested lay audience</li>
| |
| − | <li>any other formats you think can help iGEM teams and the broader community understand and
| |
| − | interact with your work. This could be anything from an educational handbook, a software tool, a
| |
| − | report, or a policy brief. We encourage you to be creative and to think about platforms that can be
| |
| − | broadly shared and adapted.</li>
| |
| − | </ul>
| |
| − |
| |
| − | <li><strong>Parts:</strong> Teams in the policy & practices division will not receive a copy of the 2015 distribution. They are not required to perform wet-lab work or to deposit new BioBricks in the Registry. Teams that do wish to receive a distribution copy of the parts registry must request one from policypractices AT igem.org, and be affiliated with a university or community laboratory. Teams that do wish to use and submit a new part must adhere to <a href="https://2015.igem.org/Safety"> safety </a> and <a href="http://parts.igem.org/cgi/dna_transfer/index.cgi"> iGEM submission guidelines</a>.
| |
| − |
| |
| − | </li>
| |
| − |
| |
| − | </ul>
| |
| − |
| |
| − | <li style="padding-bottom:15px;">
| |
| − | <h3><a id ="software" class="anchor"></a>Software:</h3>
| |
| − |
| |
| − | <p>
| |
| − | Software teams are not be required to contribute parts to the Registry (but instead are expected to contribute to the GitHub software repository). Key requirements for software teams are:
| |
| − | </p>
| |
| − |
| |
| − | <strong>End User Documentation</strong>
| |
| − | <p>
| |
| − | Core requirements are:
| |
| − | </p>
| |
| − | <ul>
| |
| − | <li>Wiki documentation of project aims, methods and success -- in line with the general iGEM requirements</li>
| |
| − | <li>Detailed installation or setup instructions (if applicable)</li>
| |
| − | <li>An well-designed User Guide explaining how to use of your program or tool</li>
| |
| − | </ul>
| |
| − |
| |
| − | <strong>Re-Use and Best software development practices</strong>
| |
| − | <p>
| |
| − | Core requirements are:
| |
| − | </p>
| |
| − | <ul>
| |
| − | <li>submission of your complete source code and any auxiliary files to the iGEM github repository</li>
| |
| − | <li>Use git versioninig from the start of your project so that the commit history is / will be available on github</li>
| |
| − | <li>Comprehensive code documentation for outside developers</li>
| |
| − | </ul>
| |
| − | <p>
| |
| − | Highly recommended:
| |
| − | </p>
| |
| − | <ul>
| |
| − | <li>more than one realistic test case</li>
| |
| − | <li>automated unit tests, documentation of test coverage</li>
| |
| − | <li>API documentation, preferably automatically built from source code documentation</li>
| |
| − | </ul>
| |
| − | <p>
| |
| − | Bonus points for:
| |
| − | </p>
| |
| − | <ul>
| |
| − | <li>use of SBOL and other standards</li>
| |
| − | <li>re-use and further development of previous iGEM software projects (or parts thereof)</li>
| |
| − | <li>use and/or improvement of existing synthetic biology tools or frameworks</li>
| |
| − | <li>development of well documented libraries for other developers rather than "only" stand-alone Apps for end users</li>
| |
| − | </ul>
| |
| − |
| |
| − | <strong>Relevance and Validation</strong>
| |
| − | <p>
| |
| − | Core requirement:
| |
| − | </p>
| |
| − | <ul>
| |
| − | <li>Demonstrate the relevance of your development for Synthetic Biolgy</li>
| |
| − | </ul>
| |
| − | Highly recommended:
| |
| − | <ul>
| |
| − | <li>Devise an experimental test for your program/algorithm/work flow</li>
| |
| − | </ul
| |
| − | <p>
| |
| − | The experimental validation of software/computational projects is <emph>not</emph> expected to result in a super fancy engineering project. Instead we would like to see simple and straightforward experiments (for example: gene synthesis, expression, fluorescence of x constructs) which can be delegated to external labs or collaborating teams.
| |
| − | iGEM/software will try to support teams who want to outsource experimental testing to academic or commercial labs. Details will follow.
| |
| − | </p>
| |
| − | <br>
| |
| − |
| |
| − |
| |
| − | </ol>
| |
| | | | |
| | <!-- end of content ----------------------------------------> | | <!-- end of content ----------------------------------------> |
