Search results

From 2014.igem.org

Create the page "Documentation" on this wiki!

Page title matches

Page text matches

  • Team:UCSD Software/Notebook
    <div class="btn btn-lg " id="doc">Documentation</div> <li> Added documents to google drive and everyone must read those documentation summarizing our plans and implementation details </li>
    125 KB (19,368 words) - 02:47, 18 October 2014
  • Team:SJTU-Software/Requirement/Medal
    ...tailed API documentation, preferably, automatically built from source code documentation (use tools like doxygen, yard, rdoc, naturaldocs, etc).<br></B> ...cally built from source code documentation using doxygen. Download of this documentation is available through this link:<a href="https://2014.igem.org/Team:SJTU-Sof
    29 KB (3,487 words) - 20:21, 17 October 2014
  • Requirements
    <li> <a href= "#documentation"> Project Documentation</a></li> <h3><a id ="documentation" class="anchor"></a>Project Documentation:</h3>
    20 KB (3,116 words) - 21:49, 29 September 2014
  • Team:UESTC-Software/Requirement.html
    <p class="no-indent">4.Project Documentation: </p> <p class="no-indent no-bg">1.End User Documentation </p>
    10 KB (1,387 words) - 02:17, 16 October 2014
  • Team:NCTU Formosa/Safety
    ==== 8. Gel Documentation System==== [[File:NCTU Formosa 2014 gel imager.jpg|200px|thumb|center|Fig.1-3-8 Gel documentation system]]
    11 KB (1,642 words) - 03:48, 18 October 2014
  • Team:UESTC-Software/Medal.html
    ...tailed API documentation, preferably, automatically built from source code documentation (use tools like doxygen, yard, rdoc, naturaldocs, etc). </p> ...d unit testing and documentation of test coverage bug tracking facilities, documentation of releases and changes between releases. </p>
    10 KB (1,395 words) - 16:24, 15 October 2014
  • Tracks/Software
    Software projects will also be judged by the quality of documentation (both for users and for other developers), by how much they embrace best pr <li>Wiki documentation must contain project aims, methods and success</li>
    10 KB (1,608 words) - 15:07, 11 October 2014
  • Team:UESTC-Software/API.html
    <h1 style="padding-top: 30px">API Documentation</h1> <div class="question" id="p1">Documentation & Download</div>
    18 KB (2,362 words) - 18:11, 17 October 2014
  • Tracks/Software/Judging
    * Wiki documentation of project aims, methods and success * Basic code documentation for outside developers
    4 KB (591 words) - 22:08, 10 July 2014
  • Team:AMU-Poznan/Project
    <h1>API documentation</h1> </br>Here you can find documentation from code:</br>
    26 KB (3,892 words) - 21:18, 17 October 2014
  • Team:SJTU-Software/Database/AssessmentModel
    ...r><th>Part Status<td>The status of a part based on the completeness of its documentation and characterization. <tr><th>Length of Documentation<td>Length of documentation for the part on Registry
    38 KB (4,797 words) - 20:15, 17 October 2014
  • Team:SYSU-Software/Medal
    <li><a href="https://2014.igem.org/Team:SYSU-Software/Documentation">Documentation</a></li> ...tailed API documentation, preferably, automatically built from source code documentation (use tools like doxygen, yard, rdoc, naturaldocs, hetc).</p>
    14 KB (2,134 words) - 21:33, 17 October 2014
  • Team:UCSD Software/Documentation
    <div class="btn btn-lg " id="doc">Documentation</div> ...a href = "#" class = "list_items"><font size = "4px" color = "#000000">API Documentation</font></a></li>
    68 KB (8,340 words) - 03:16, 18 October 2014
  • Team:Heidelberg/pages/midnightdoc
    ...y of projects would also be increased. Thus, a consistent, semi-automated, documentation method could help solve many of the problems faced by iGEM teams, but also ...erse publications, but also modify and improve upon them. We believe, that documentation of wet lab work, should also try to make use some of these concepts (and vi
    9 KB (1,425 words) - 03:55, 18 October 2014
  • Team:StanfordBrownSpelman/Lab
    ...uloseAcetateProduction.pdf"><b>Biomaterials Project Notebook:</b> Complete documentation of our methods, protocols, and scientific processes can be found in the lin ...berlessHellCell.pdf"><b>Amberless Hell Cell Project Notebook:</b> Complete documentation of our methods, protocols, and scientific processes can be found in the lin
    10 KB (1,387 words) - 03:04, 18 October 2014
  • Team:UCSD Software/SoftwareAchievements
    <div class="btn btn-lg " id="doc">Documentation</div> ... on the <a href = "https://2014.igem.org/Team:UCSD_Software/Documentation">Documentation</a> page as well as on <a href="https://github.com/igemsoftware/UCSD-iGEM_2
    13 KB (1,434 words) - 03:27, 18 October 2014
  • Team:SF Bay Area DIYbio/NotebookDocumentation
    <p><b>Real Vegan Cheese Notebook Documentation Guidelines</b><br> ... all got our training in different ways/places, we developed the following documentation standard for Real Vegan Cheese experiments on October 4, 2014.
    4 KB (541 words) - 18:42, 16 October 2014
  • Team:HFUT CHINA/Medal.html
    ...led API documentation, preferably, automatically built from source code documentation (use tools like doxygen, yard, rdoc, naturaldocs, etc).</p><a name="1"></a> ...it testing and documentation of test coverage, bug tracking facilities, documentation of releases and changes between releases.</p>
    13 KB (1,790 words) - 03:50, 18 October 2014
  • Team:SYSU-Software/Documentation
    <li><a href="https://2014.igem.org/Team:SYSU-Software/Documentation">Documentation</a></li> ...-align: center; font-size: 40px; font-weight: bold; font-family: verdana;">Documentation</h1><br/>
    7 KB (998 words) - 21:30, 17 October 2014
  • Team:USTC-Software/requirements.php
    ...tailed API documentation, preferably, automatically built from source code documentation (use tools like doxygen, yard, rdoc, naturaldocs, etc). ...unit testing and documentation of test coverage , bug tracking facilities, documentation of releases and changes between releases.
    23 KB (3,230 words) - 03:46, 18 October 2014
  • Tracks/Measurement
    <li>Quality of presentation and documentation</li> <li>Quality of presentation and documentation</li>
    19 KB (2,976 words) - 23:06, 5 August 2014
  • Calendar of Events
    ...ion due, including documentation for all medal criteria</span> <br><small>[documentation due as part of wiki freeze and judging form deadlines below]</small>
    4 KB (539 words) - 21:07, 15 October 2014
  • Team:Example C/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    7 KB (1,159 words) - 16:03, 24 March 2014
  • Team:UMaryland/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    6 KB (1,036 words) - 16:07, 4 June 2014
  • Team:CU-Boulder/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    3 KB (561 words) - 00:56, 29 May 2014
  • Team:WPI-Worcester/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    5 KB (813 words) - 15:46, 11 June 2014
  • Team:LIKA-CESAR-Brasil/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r <p> As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    8 KB (1,238 words) - 17:11, 15 August 2014
  • Team:Bielefeld-CeBiTec/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    6 KB (1,035 words) - 13:01, 1 June 2014
  • Team:Groningen/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    6 KB (1,009 words) - 08:45, 19 June 2014
  • Team:SDU-Denmark/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    6 KB (1,034 words) - 07:05, 20 June 2014
  • Team:UCSC/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    9 KB (1,485 words) - 07:10, 21 March 2015
  • Team:Pitt/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    6 KB (1,057 words) - 03:50, 23 June 2014
  • Team:Auckland New Zealand/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    3 KB (600 words) - 07:50, 9 July 2014
  • Team:AlumniGEM/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    7 KB (1,148 words) - 18:12, 15 September 2014
  • Team:Carnegie Mellon/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    7 KB (1,159 words) - 19:28, 29 July 2014
  • Team:UNC-Chapel Hill/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    6 KB (1,014 words) - 02:35, 5 August 2014
  • Team:Queens Canada/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    6 KB (1,076 words) - 15:25, 24 July 2014
  • Team:UFMG Brazil/Our Institute
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    7 KB (1,159 words) - 16:10, 30 July 2014
  • Team:ATOMS-Turkiye/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    7 KB (1,193 words) - 10:01, 3 August 2014
  • Team:Gifu/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    9 KB (1,638 words) - 23:38, 17 October 2014
  • Team:Freiburg/Content/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    3 KB (587 words) - 17:36, 13 August 2014
  • Team:Tufts/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    6 KB (943 words) - 01:27, 30 September 2014
  • Team:Calgary/PoliciesAndPractices/DiagnosticLandscape/Implementation
    ...n in a different manner, our team sought to determine exactly what sort of documentation must be in place before a device such as ours could reach the market. ...HO) then FMHSACA usually registers the device provided all of the required documentation is submitted. Otherwise, FMHSACA might choose to run its own safety and qua
    8 KB (1,271 words) - 03:06, 18 October 2014
  • AlumniGEM/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    7 KB (1,139 words) - 18:47, 15 September 2014
  • Team:Michigan Software/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    7 KB (1,145 words) - 01:33, 20 September 2014
  • Team:Hannover/Safety/Saftey Heavy Metal
    ...enic and its inorganic compounds (with the exception of arsine) [MAK Value Documentation, 2005]. The MAK Collection for Occupational Health and Safety. 50–106. DO 3. 2012. Kupfer und seine anorganischen Verbindungen [MAK Value Documentation in German language, 2004]. The MAK Collection for Occupational Health and S
    7 KB (1,093 words) - 19:34, 17 October 2014
  • Team:The Tech Museum/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    3 KB (555 words) - 23:17, 8 October 2014
  • Team:Valencia UPV/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    7 KB (1,159 words) - 16:31, 4 October 2014
  • Team:LMU-Munich/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    7 KB (1,148 words) - 17:21, 11 October 2014
  • Team:ArtCenter MDP/Attributions
    Brainstorming, concept development, documentation, further concept development and iterations, wiki design, graphics, writing Research, brainstorming, concept development, running simulations, documentation, further concept development and iterations, graphics, writing, pool ph tes
    11 KB (1,491 words) - 03:05, 18 October 2014
  • Team:Peking/Part
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    7 KB (1,148 words) - 16:09, 17 October 2014
  • Team:Heidelberg/Software
    MidnightDoc is the new way of lab documentation – enabling backtraces of experiments and provides an easy to use platform <a href="https://2014.igem.org/Team:Heidelberg/Software/Linker_Software/Documentation" class="cell box">
    4 KB (501 words) - 03:53, 18 October 2014
  • Team:UESTC-Software/Testing.html
    <h1 style="padding-top: 30px">Testing Documentation</h1> <li><a href="API.html">API Documentation</a></li>
    6 KB (766 words) - 02:20, 18 October 2014
  • Team:WLC-Milwaukee/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    8 KB (1,337 words) - 03:31, 18 October 2014
  • Team:Melbourne/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    14 KB (1,751 words) - 10:34, 17 October 2014
  • Team:Example 2/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    7 KB (1,148 words) - 21:29, 16 October 2014
  • Team:SJTU-Software/Database/FutureDevelopment
    ...entation automatically built from source code documentation using doxygen, documentation of automated unit testing and test coverage built using EclEmma and manual
    22 KB (2,474 words) - 20:18, 17 October 2014
  • Team:Hong Kong-CUHK
    ... <a href="#" class="dropdown-toggle" data-toggle="dropdown">Documentation</a> ...<li><a href="https://2014.igem.org/Team:Hong_Kong-CUHK/home.html?page=link-documentation">Protocol</a>
    14 KB (1,312 words) - 18:27, 4 January 2015
  • Team:Berlin/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    7 KB (1,148 words) - 13:32, 17 October 2014
  • Team:Heidelberg/Software/MidnightDoc
    subtitle= Documentation made easy ...life of next iGEM teams, but also researchers in general, easier by making documentation an activity naturally intertwined with any wet lab work. We also believe th
    718 B (88 words) - 01:57, 18 October 2014
  • Team:Example/Parts
    ...ary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper r As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The soone
    7 KB (1,148 words) - 22:41, 24 June 2015
  • Tracks/Art Design
    ...ckground information, context, inspirations and goals for the project, and documentation of your process and outcomes.</li> ...art of your project, during the initiation, development, presentation, and documentation your project.</li></ol>
    17 KB (2,624 words) - 22:49, 5 August 2014
  • Judging
    <li> <a href= "https://2014.igem.org/Requirements#documentation"> Project Documentation</a></li> ... to understand about synthetic biology, parts and why characterization and documentation on the Registry is so important. We also have a <a href="https://2014.igem.
    11 KB (1,872 words) - 13:48, 1 November 2014
  • Guidelines
    <h3>Project Documentation</h3> * High-quality documentation in the iGEM Registry.
    4 KB (642 words) - 19:57, 13 January 2014
  • Judging/Awards
    ...p:Adding_Parts">adding new parts</a>. A new application and/or outstanding documentation (quantitative data showing the Part’s/ Device’s function) of a previous ...e improvement of an existing part is just as important as the creation and documentation of a new part. An "improvement" is anything that improves the functionality
    22 KB (3,544 words) - 17:34, 9 October 2014
  • Wiki/Tracks/MeasurementRequirements
    <li style="padding-bottom: 15px;"><strong>Project Documentation:</strong><br> <li> High-quality documentation in the iGEM Registry. </li>
    6 KB (966 words) - 17:12, 30 January 2014
  • Wiki How-To
    <b> 3.- Start working on your documentation early on. </b> <br> ...ted a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. I
    14 KB (2,500 words) - 07:36, 20 June 2015
  • Team:NYMU-Taipei/jquery-easing.js
    * of conditions and the following disclaimer in the documentation and/or other materials * of conditions and the following disclaimer in the documentation and/or other materials
    8 KB (1,292 words) - 08:54, 11 April 2014
  • Team:Aachen/TestBench2
    * a copy of this software and associated documentation files (the * a copy of this software and associated documentation files (the
    266 KB (20,502 words) - 17:32, 12 October 2014
  • Team:KIT-Kyoto/MaxImage
    Examples and documentation at: http://www.aaronvanderzwan.com/maximage/2.0/ Documentation at:
    21 KB (2,458 words) - 02:04, 19 May 2014
  • Team:UCL/Team Portal
    * Add all documentation to the wiki. * As part of your documentation, keep the links from the menu to the left.
    2 KB (254 words) - 01:07, 17 June 2014
  • Team:Goettingen/jquery.cycle.all.js
    * Examples and documentation at: http://jquery.malsup.com/cycle/ * Examples and documentation at: http://malsup.com/jquery/cycle/
    51 KB (6,652 words) - 10:02, 31 May 2014
  • Team:Goettingen/jquery cycle
    * Examples and documentation at: http://jquery.malsup.com/cycle/ * Examples and documentation at: http://malsup.com/jquery/cycle/
    51 KB (6,649 words) - 14:19, 4 June 2014
  • Meetups/August HZAU-China/jquery.easing.js
    * of conditions and the following disclaimer in the documentation and/or other materials * of conditions and the following disclaimer in the documentation and/or other materials
    8 KB (1,292 words) - 15:58, 13 June 2014
  • Team:Austin Texas/kit
    ...widely (re)used. They are published in single, short articles lacking full documentation, and our own experiences of working with a number of ncAAs indicate that no Documentation, including sequence information, of the tRNA synthetase/tRNA pairs used can
    35 KB (5,717 words) - 23:54, 18 March 2015
  • Team:Imperial/js/carousel
    * of conditions and the following disclaimer in the documentation and/or other materials * of conditions and the following disclaimer in the documentation and/or other materials
    16 KB (2,191 words) - 10:04, 29 July 2014
  • Team:Valencia UPV/Core:JS/jquery.easing.1.3.js
    * of conditions and the following disclaimer in the documentation and/or other materials * of conditions and the following disclaimer in the documentation and/or other materials
    8 KB (1,292 words) - 21:44, 23 July 2014
  • Team:Aalto-Helsinki/Business
    ...hin the organization. Vapaakallio will also be responsible for Open Source documentation. Otto Lamminpää and Niklas Itänen will be in charge of modeling and math ...e required in the original license. As we are in charge of the Open Source documentation, we can easily manage all the data available and come up with new solutions
    59 KB (8,872 words) - 14:34, 25 November 2014
  • Team:UESTC-Software/Overview.html
    <li><a href="API.html">API Documentation</a></li> <li><a href="Testing.html">Testing Documentation</a></li>
    21 KB (3,246 words) - 02:23, 18 October 2014
  • Team:Michigan Software/Project
    ...s success. In turn, the lack of commonly accepted protocols and inadequate documentation affects experimental reproducibility through method inconsistencies across
    6 KB (886 words) - 01:20, 3 August 2015
  • Team:Aix-Marseille/js/elevatezoom.js
    * Demo's and documentation: * Demo's and documentation:
    57 KB (5,875 words) - 10:48, 18 August 2014
  • Team:Calgary/Notebook/Journal/PoliciesAndPractices
    ...HO) then FMHSACA usually registers the device provided all of the required documentation is submitted. Otherwise, FMHSACA might choose to run its’ own safety and
    25 KB (4,045 words) - 03:31, 18 October 2014
  • Team:UESTC-Software/journal.html
    <li><a href="API.html">API Documentation</a></li> <li><a href="Testing.html">Testing Documentation</a></li>
    16 KB (2,391 words) - 03:26, 18 October 2014
  • Team:UCSD Software/Project
    <div class="btn btn-lg " id="doc">Documentation</div> ...se: gene sequencing and indexing to understand gene presence and function, documentation of chemical interactions, and investigations into crosstalk and modeling of
    105 KB (15,839 words) - 03:46, 18 October 2014
  • Team:UESTC-Software/safety.html
    <li><a href="API.html">API Documentation</a></li> <li><a href="Testing.html">Testing Documentation</a></li>
    12 KB (1,782 words) - 16:20, 15 October 2014
  • Team:CityU HK/lablog/project1.js2
    * of conditions and the following disclaimer in the documentation and/or other materials * of conditions and the following disclaimer in the documentation and/or other materials
    8 KB (1,292 words) - 14:20, 10 September 2014
  • Team:Dundee/Implementation
    ... and the functionality involved. This became an iterative process with the documentation being updated after feedback from our supervisors, patients and medical sta
    12 KB (1,929 words) - 20:21, 5 October 2014
  • Team:SYSU-Software/jquery.easing.1.3.js
    * of conditions and the following disclaimer in the documentation and/or other materials * of conditions and the following disclaimer in the documentation and/or other materials
    8 KB (1,292 words) - 09:48, 1 October 2014
  • Team:CityU HK/lablog/project1 js2
    * of conditions and the following disclaimer in the documentation and/or other materials * of conditions and the following disclaimer in the documentation and/or other materials
    8 KB (1,292 words) - 14:23, 10 September 2014
  • Team:Sheffield/Template:jquery.easing.1.3.js
    * of conditions and the following disclaimer in the documentation and/or other materials * of conditions and the following disclaimer in the documentation and/or other materials
    8 KB (1,292 words) - 05:04, 26 September 2014
  • Team:StanfordBrownSpelman/Achievements
    Following is documentation of the <a href="https://2014.igem.org/Judging/Awards" target="_blank">2014 ...parts.igem.org/Main_Page" target="_blank">registry</a> to see the complete documentation.</div>
    10 KB (1,336 words) - 00:13, 18 October 2014
  • Team:UT-Tokyo/jquery.easing.1.3.js
    * of conditions and the following disclaimer in the documentation and/or other materials * of conditions and the following disclaimer in the documentation and/or other materials
    8 KB (1,294 words) - 15:02, 29 September 2014
  • Team:KIT-Kyoto/Achievement
    ...ckground information, context, inspirations and goals for the project, and documentation of your process and outcomes.</li> ...art of your project, during the initiation, development, presentation, and documentation your project. → <a href="/Team:KIT-Kyoto/Acknowledgements">Acknowledgemen
    7 KB (936 words) - 13:54, 20 November 2014
  • Team:Sheffield/Template:menujquery.easing.1.3.js
    * of conditions and the following disclaimer in the documentation and/or other materials * of conditions and the following disclaimer in the documentation and/or other materials
    8 KB (1,292 words) - 11:40, 7 October 2014
  • Team:Braunschweig/Achievements-content
    ...ed for controlled protein biosynthesis and chosen because of the excellent documentation.</li> ...ere to the iGEM Registry guidelines). A new application of and outstanding documentation (quantitative data showing the Part’s/ Device’s function) of a previous
    40 KB (5,342 words) - 00:19, 18 October 2014
  • Team:UESTC-Software/team.html
    <li><a href="API.html">API Documentation</a></li> <li><a href="Testing.html">Testing Documentation</a></li>
    16 KB (2,343 words) - 20:35, 17 October 2014
  • Team:UESTC-Software/Modeling.html
    <li><a href="API.html">API Documentation</a></li> <li><a href="Testing.html">Testing Documentation</a></li>
    20 KB (2,845 words) - 02:52, 18 October 2014
  • Team:Tongji/docs css
    Bootstrap's documentation styles Special styles for presenting Bootstrap's documentation and examples
    24 KB (2,120 words) - 20:21, 11 October 2014
  • Team:Dundee/Implementation/realWorld
    ...as possible. In addition to receiving suggestions about how to improve our documentation (which have been acted upon) we were informed of the following:
    8 KB (1,249 words) - 22:30, 17 October 2014
  • Team:SJTU-Software/Database
    ...>DNA status; Group Favorite; Whether or not deleted; Used Times; Length of Documentation ...th>part status<td> The status of the part based on the completeness of its documentation and characterization.system not currently in place
    39 KB (4,883 words) - 20:12, 17 October 2014
  • Team:UCSF UCB/team.html
    ...low cytometry. Sabrina (along with Jeffrey Shu) has also been in charge of documentation and has completed the safety forms for the competition.</p></article> ...Biotechnology. Jeffrey (along with Sabrina Chu) has also been in charge of documentation and has completed the safety and judging forms for the competition.</p></ar
    540 KB (81,331 words) - 01:20, 18 October 2014
  • Team:Heidelberg/Notebook
    <p>&ndash;&nbsp;the different way of documentation</p> ...itle=Team:Heidelberg/Software/MidnightDoc">MidnightDoc</a>, our new wetlab documentation system. Each circle below represents one experiment, for example a restrict
    66 KB (9,823 words) - 03:52, 18 October 2014
  • Team:SF Bay Area DIYbio/Notebook
    <p>General Documentation Information</p><ul> .../Team:SF_Bay_Area_DIYbio/NotebookDocumentation">Real Vegan Cheese Notebook Documentation Guidelines</a><br>
    8 KB (1,314 words) - 03:09, 18 October 2014
  • Team:Hong Kong-CUHK/testingtesting
    about: "Documentation", background: "images/menu/documentation.png",
    6 KB (492 words) - 18:03, 14 October 2014
  • Team:UT-Dallas/jquery.easing.1.3.js
    * of conditions and the following disclaimer in the documentation and/or other materials * of conditions and the following disclaimer in the documentation and/or other materials
    8 KB (1,292 words) - 23:28, 14 October 2014
  • Team:CAU China/home.star.js
    * Examples and documentation at: http://jquery.malsup.com/cycle/ * Examples and documentation at: http://malsup.com/jquery/cycle/
    41 KB (5,666 words) - 15:00, 15 October 2014
  • Team:UESTC-Software/Validation.html
    <li><a href="API.html">API Documentation</a></li> <li><a href="Testing.html">Testing Documentation</a></li>
    99 KB (15,751 words) - 18:00, 17 October 2014
  • Team:UESTC-Software/HumanPractice.html
    <li><a href="API.html">API Documentation</a></li> <li><a href="Testing.html">Testing Documentation</a></li>
    14 KB (2,038 words) - 03:33, 18 October 2014
  • Team:ZJU-China/JS/jquery.easing.1.3.js
    * of conditions and the following disclaimer in the documentation and/or other materials * of conditions and the following disclaimer in the documentation and/or other materials
    8 KB (1,292 words) - 20:10, 15 October 2014
  • Team:UB Indonesia/js/jquery-easing
    * of conditions and the following disclaimer in the documentation and/or other materials * of conditions and the following disclaimer in the documentation and/or other materials
    8 KB (1,292 words) - 00:20, 16 October 2014
  • Team:UESTC-Software/Download.html
    <li><a href="API.html">API Documentation</a></li> <li><a href="Testing.html">Testing Documentation</a></li>
    13 KB (1,604 words) - 15:47, 17 October 2014
  • Team:Nevada/jquery.easing.1.3.js
    * of conditions and the following disclaimer in the documentation and/or other materials * of conditions and the following disclaimer in the documentation and/or other materials
    8 KB (1,292 words) - 02:33, 16 October 2014
  • Team:UESTC-Software/Demo.html
    <li><a href="API.html">API Documentation</a></li> <li><a href="Testing.html">Testing Documentation</a></li>
    7 KB (765 words) - 12:17, 17 October 2014
  • Team:SCUT-China/Data Page/Judging Criteria
    2.We completed and submitted our safety documentation and published general safety information on our wiki safety page<br/><br/> 3.We completed and submitted our safety documentation and published general lab safety information on our
    4 KB (686 words) - 03:04, 18 October 2014
  • Team:Melbourne/Project
    Delft documentation) with the standard T7 promoter and RBS BioBrick <a synthesis. As the Delft documentation did not specify whether the gene
    44 KB (6,443 words) - 13:47, 11 December 2014
  • Team:Hong Kong-CUHK/index.html
    <a href="#" class="dropdown-toggle" data-toggle="dropdown">Documentation</a> about: "Documentation",
    15 KB (1,426 words) - 22:15, 16 October 2014
  • Team:UESTC-Software/Installation.html
    <li><a href="API.html">API Documentation</a></li> <li><a href="Testing.html">Testing Documentation</a></li>
    13 KB (1,746 words) - 19:10, 17 October 2014
  • Team:Tsinghua-A/css/font-awesome.min.css
    * The full suite of pictographic icons, examples, and documentation * - Font Awesome documentation licensed under CC BY 3.0 License -
    19 KB (2,260 words) - 20:15, 17 October 2014
  • Team:UESTC-Software/Home.html
    <li><a href="API.html">API Documentation</a></li> <li><a href="Testing.html">Testing Documentation</a></li>
    4 KB (541 words) - 08:56, 17 October 2014
  • Team:USTC-Software/develop.php
    ...istering as colleagues. For more information about project management, see documentation of the Back End.</p> ...is a kind of completely public and universal interface and offers detailed documentation. You can develop your own applications based on these interfaces. These int
    23 KB (3,359 words) - 03:41, 18 October 2014
  • Team:UESTC-Software/UserGuide.html
    <li><a href="API.html">API Documentation</a></li> <li><a href="Testing.html">Testing Documentation</a></li>
    12 KB (1,618 words) - 01:44, 18 October 2014
  • Tracks/Microfluidics
    ...abricated and tested any milli-, micro- or nano-fluidic system. The system documentation should include both the fluidic device and any hardware for controlling the
    11 KB (1,625 words) - 23:05, 5 August 2014
  • Tracks/Community Labs
    <li>Create step-by-step documentation for your method, sufficient that it could be replicated by another communit
    12 KB (1,942 words) - 22:54, 5 August 2014
  • Software/Requirements
    <li style="padding-bottom:15px;"><strong>Project Documentation:</strong><br>
    6 KB (909 words) - 18:05, 29 January 2014
  • Entrepreneurship/Requirements
    <li style="padding-bottom:15px;"><strong>Project Documentation:</strong><br>
    6 KB (949 words) - 18:16, 29 January 2014
  • Team:Example C
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    7 KB (1,236 words) - 19:30, 24 March 2014
  • Team:CU-Boulder/Original
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    7 KB (1,218 words) - 02:35, 10 May 2014
  • Team:LZU-China/Team
    ...extraordinary image processing skills and the ability of reading scientech documentation and also brought several important ideas for the team.In addition,he takes
    41 KB (5,530 words) - 00:50, 18 October 2014
  • Team:Penn State/Human Practices
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    8 KB (1,295 words) - 01:36, 10 June 2014
  • Team:Tuebingen/Notebook/Journal
    Besides that, we ran tests with several lab devices, including the gel documentation system where we also tested out our DNA ladder and our DNA-Stain-G, which w
    12 KB (2,029 words) - 02:52, 18 October 2014
  • Team:Virginia/Notebook
    ...o go back!<br> This lab notebook contains 155 pages of text! It contains a documentation of the entire summer's worth of lab work!</div>
    24 KB (2,793 words) - 23:00, 21 November 2014
  • Team:Virginia/Attributions
    ...bution, and to help provide both regional and international teams with the documentation necessary for approval at their respective schools.</p>
    10 KB (1,399 words) - 04:59, 27 November 2014
  • Team:Tuebingen/repository
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    7 KB (1,180 words) - 18:38, 30 May 2014
  • Team:Dundee/animate
    ... of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, includ
    4 KB (453 words) - 12:34, 29 May 2014
  • Meetups/August HZAU-China/jquery.cycle.min.all.js
    * Examples and documentation at: http://jquery.malsup.com/cycle/
    27 KB (4,159 words) - 15:58, 13 June 2014
  • Team:Michigan Software/Protocat
    ...ugins or "installed_apps", and do some general tweaking. Please see Django documentation for more information.
    4 KB (554 words) - 03:48, 18 October 2014
  • Team:Braunschweig
    ... summer, feel free to have a look at our Notebook, where we put together a documentation of our lab work.
    22 KB (2,582 words) - 20:24, 17 October 2014
  • Team:UMBC-Maryland
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    6 KB (1,023 words) - 02:46, 18 June 2014
  • Meetups/August HZAU-China/js/jquery.cycle.min.all.js
    * Examples and documentation at: http://jquery.malsup.com/cycle/
    28 KB (4,166 words) - 10:03, 15 June 2014
  • Meetups/August HZAU-China/js/jquery.easing.js
    * of conditions and the following disclaimer in the documentation and/or other materials * of conditions and the following disclaimer in the documentation and/or other materials
    8 KB (1,299 words) - 10:04, 15 June 2014
  • Team:Valencia UPV/prueba2
    <p class="lead">Just like the Webpop documentation? <strong>Pin</strong> it and relax.</p>
    12 KB (1,496 words) - 18:43, 29 September 2014
  • Team:DTU-Denmark/mainarchive
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    8 KB (1,379 words) - 15:01, 18 June 2014
  • Team:Sheffield/backup MainPage
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    7 KB (1,217 words) - 14:08, 19 June 2014
  • Team:Colombia/Parts
    ..._blank"> offical part's submission page</a>, where you also can find their documentation and characterization. </font><br><br>
    2 KB (297 words) - 00:44, 18 October 2014
  • Team:Ollin MexicoZamorano
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    7 KB (1,236 words) - 20:17, 24 June 2014
  • Team:UCSD Software/Safety
    <div class="btn btn-lg " id="doc">Documentation</div> window.location.href="https://2014.igem.org/Team:UCSD_Software/Documentation";
    11 KB (1,257 words) - 02:46, 18 October 2014
  • Team:VictoriaBC
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    7 KB (1,234 words) - 00:42, 4 September 2014
  • Team:Hong Kong HKUST/human practice/start-up kit/database/data
    ...ica\"",name: "\"UIUC-Illinois\"",type: "\"Survey\"",description: "\"Made a documentation with graphs about common lab errors\"",medal: "\"Bronze\"",advancement: "N/
    367 KB (43,850 words) - 09:23, 21 September 2014
  • Team:USyd-Australia/WikiDetailsPage
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    7 KB (1,214 words) - 05:54, 5 July 2014
  • Team:SJTU-Software/Team
    ...is second major. He wrote the whole background program of Easy BBK and API documentation. Also, he communicates well with all those on our team who wrote GUI to con
    30 KB (3,565 words) - 19:55, 17 October 2014
  • Equipe: ULB Bruxelles
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    4 KB (680 words) - 15:15, 10 July 2014
  • Equipe: ULB Bruxelles/Accueil
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    4 KB (683 words) - 21:37, 13 August 2014
  • Equipe: ULB Bruxelles/L'équipe
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    7 KB (1,092 words) - 00:11, 6 July 2014
  • Equipe: ULB Bruxelles/Profil-officiel
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    6 KB (1,016 words) - 23:38, 5 July 2014
  • Equipe: ULB Bruxelles/Projet
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    7 KB (1,092 words) - 00:12, 6 July 2014
  • Equipe: ULB Bruxelles/Genes-IGEM
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    7 KB (1,092 words) - 00:12, 6 July 2014
  • Equipe: ULB Bruxelles/Modelisation
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    7 KB (1,092 words) - 00:13, 6 July 2014
  • Equipe: ULB Bruxelles/Actus
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    7 KB (1,092 words) - 00:13, 6 July 2014
  • Team:ULB-Brussels/Notebook
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    15 KB (2,013 words) - 10:10, 8 July 2014
  • Team:ULB-Brussels/Attributions
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    15 KB (2,013 words) - 10:15, 8 July 2014
  • Handbook
    <h3> Documentation and presentation</h3>
    6 KB (1,041 words) - 22:12, 6 August 2014
  • Team:USyd-Australia/TestPage
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    4 KB (637 words) - 06:57, 23 July 2014
  • Team:EPF Lausanne/Notebook/Bacteria
    ...9007 by putting the missing sequence in front of the RFP. With the further documentation we discovered that the promoter is not specific for dimerised CpxR.</p>
    243 KB (37,755 words) - 16:14, 17 October 2014
  • Team:UCSD Software
    <div class="btn btn-lg " id="doc">Documentation</div> window.location.href="https://2014.igem.org/Team:UCSD_Software/Documentation";
    20 KB (2,150 words) - 03:05, 18 October 2014
  • Team:DTU-Denmark/Achievements/Medal fulfillings
    <ul><li>The two Spinach2.1 BioBricks and the corresponding documentation can be found in the Registry with the entries <a href="http://parts.igem.or
    9 KB (1,430 words) - 00:10, 18 October 2014
  • Team:UGA-Georgia/Project
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    9 KB (1,404 words) - 22:12, 11 October 2014
  • Team:SYSU-Software/Overview
    <li><a href="https://2014.igem.org/Team:SYSU-Software/Documentation">Documentation</a></li>
    15 KB (2,036 words) - 03:56, 18 October 2014
  • Team:Kent/what we need
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    7 KB (1,280 words) - 09:13, 13 August 2014
  • Team:Uppsala/Safety
    ...</i> is stated to be specific towards <i>Y.enterocolitica</i>, however the documentation is poor. This might mean that the expressed colicin is at a higher risk of
    16 KB (2,833 words) - 13:00, 17 October 2014
  • Team:TU Delft-Leiden/Achievements
    ...abricated and tested any milli-, micro- or nano-fluidic system. The system documentation includes both the fluidic device and any hardware for controlling the devic
    6 KB (914 words) - 23:59, 17 October 2014
  • Team:Aalto-Helsinki/Journal
    <h3>Thorough Documentation</h3>
    55 KB (7,574 words) - 16:12, 30 November 2014
  • Team:Nagahama
    ...gistry help page on adding new parts. A new application and/or outstanding documentation (quantitative data showing the Part's/ Device's function) of a previously e
    10 KB (1,567 words) - 23:05, 17 October 2014
  • Team:WLC-Milwaukee-Test
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    4 KB (639 words) - 23:04, 15 August 2014
  • Team:UCL/Requirements
    * As part of your documentation, keep the links from the menu to the left.
    2 KB (342 words) - 16:13, 14 August 2014
  • Team:StanfordBrownSpelman/Material Waterproofing
    ...WaspProteins.pdf"><b>Material Waterproofing Project Notebook:</b> Complete documentation of our methods, protocols, and scientific processes can be found in the lin
    30 KB (4,495 words) - 14:04, 16 December 2014
  • Team:ETH Zurich/lab/protocols
    history for documentation of the acquisition parameters for each image
    36 KB (5,179 words) - 23:45, 17 October 2014
  • Team:DTU-Denmark/Achievements/Medal fulfillments
    <ul><li>The two Spinach2.1 BioBricks and the corresponding documentation can be found in the Registry with the entries <a href="http://parts.igem.or
    9 KB (1,430 words) - 02:33, 18 October 2014
  • Team:Washington/efawe
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    8 KB (1,246 words) - 00:45, 14 August 2014
  • Team:TU Eindhoven/Project/protocols
    ...on numerous protocols were devoloped to guide our experiments and keep our documentation neat and tidy. Because these protocols can also be useful to other projects
    5 KB (726 words) - 19:19, 31 August 2014
  • Team:Hannover/Team
    ...lanie Barth</b><br>Degree course: B.Sc. Plant Biotechnology<br>Task: Photo documentation, transformations and chairing meetings</p><p class="text member_quote">“F
    15 KB (2,510 words) - 17:23, 17 October 2014
  • Team:Pitt/cathelicidinModels/Methods
    ...d analyzed using a custom Python script and Microsoft Excel. See below for documentation: </p>
    3 KB (511 words) - 23:41, 17 October 2014
  • Team:Harrisburg NBT
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    8 KB (1,303 words) - 19:41, 15 August 2014
  • Team:Vanderbilt Software/Project
    ..."http://github.com/igemsoftware/Vanderbilt_2014">repository on github</a>. Documentation on the produced software tool can be found on the <a href="https://2014.ige
    4 KB (652 words) - 22:35, 17 October 2014
  • Team:WLC-Milwaukee/Probiotics
    ...awiki/2014/0/0a/Wlc.FDAlogo.png">Probiotics must pass rigorous testing and documentation before becoming suitable for the market. It is necessary to clearly identif
    15 KB (2,318 words) - 01:48, 14 November 2014
  • Team:Valencia UPV/javascript slider
    * a copy of this software and associated documentation files (the
    162 KB (11,239 words) - 11:29, 25 August 2014
  • Team:Valencia UPV/javascript utils
    * a copy of this software and associated documentation files (the
    79 KB (6,702 words) - 11:42, 25 August 2014
  • Team:Valencia UPV/javascript core
    * a copy of this software and associated documentation files (the
    4 KB (475 words) - 11:43, 25 August 2014
  • Team:Dundee/js/raphael-js
    ...s data attribute’s format are described in the SVG specification.">SVG documentation regarding path string</a>. Raphaël fully supports it.</p>
    293 KB (30,061 words) - 21:31, 26 August 2014
  • Team:The Tech Museum/Project
    <p><h3>Details and Documentation:</h3></p>
    9 KB (1,335 words) - 03:19, 18 October 2014
  • Team:Austin Texas/project
    *Update/make better our official biobrick parts pages. With proper documentation
    5 KB (806 words) - 15:56, 14 October 2014
  • Team:British Columbia/Home old
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    10 KB (1,581 words) - 22:00, 12 September 2014
  • Team:SYSU-Software/Design
    <li><a href="https://2014.igem.org/Team:SYSU-Software/Documentation">Documentation</a></li>
    14 KB (2,134 words) - 23:30, 17 October 2014
  • Team:SZU-China/judging/achievement
    ...gistry help page on adding new parts. A new application and/or outstanding documentation (quantitative data showing the Part's/ Device's function) of a previously e
    20 KB (2,458 words) - 03:23, 18 October 2014
  • AlumniGEM
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    7 KB (1,201 words) - 18:26, 15 September 2014
  • Team:AMU-Poznan/Modeling
    documentation</br>
    7 KB (1,012 words) - 21:02, 16 October 2014
  • Team:Glasgow/Notebook
    <p>The key to a successful project is good documentation. We have recorded both our week-to-week activities and our protocols - plea
    1 KB (159 words) - 01:23, 18 October 2014
  • Team:UCL/Template:BioprocessGalleryCoinSlider
    * Examples and documentation at: http://workshop.rs/projects/coin-slider/
    11 KB (1,496 words) - 22:08, 23 September 2014
  • Team:Bordeaux/Medalrequirement
    ...e improvement of an existing part is just as important as the creation and documentation of a new part. An "improvement" is anything that improves the functionality
    5 KB (799 words) - 00:53, 18 October 2014
  • Team:UT-Tokyo/jquery.mCustomScrollbar.js
    of this software and associated documentation files (the "Software"), to deal
    82 KB (8,923 words) - 15:03, 29 September 2014
  • Team:Cornell/temp
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    7 KB (1,217 words) - 16:02, 27 September 2014
  • Team:EPF Lausanne/HumanPractice
    ...nt_hackuarium20140928.jpg" data-lightbox="img4" data-title="Working on the documentation at the Hackuarium"><img src="https://static.igem.org/mediawiki/2014/b/b2/IG <figcaption class="cntr">Working on the documentation at the Hackuarium</figcaption>
    39 KB (5,752 words) - 02:59, 18 October 2014
  • Team:TU Delft-Leiden/Human Practices/stakeholders
    ...ge building projects. Such a procedure consist of the research of historic documentation and doing sample measurements with a metal detector. Bergman: “We increas
    41 KB (6,836 words) - 16:07, 6 October 2014
  • Team:Heidelberg/pages/igemathome/implementation
    ...C++ BOINC Api and thus can be accessed and simply be reading the BOINC API documentation.
    17 KB (2,662 words) - 23:06, 16 October 2014
  • Team:IvyTech SouthBend IN/meet our team
    ...in fall 2014. Responsible for soliciting third party financial support and documentation of project protocols and meetings.</p>
    6 KB (943 words) - 01:29, 16 October 2014
  • Team:Hong Kong HKUST/wetlab/safety
    Risks associated with UV exposure during gel documentation and excision are also minimized by wearing face shields
    16 KB (2,155 words) - 01:37, 18 October 2014
  • Team:Marburg:Policy Practices
    afraid of bacteria since she watched a documentation dealing with the possibilities of biotechnology and Synthetic Biology.
    20 KB (3,289 words) - 02:41, 18 October 2014
  • Team:Marburg:Policy Practices:Blista
    ...he realized that she does not have to be afraid of bacteria when she saw a documentation on the possibilities of biotechnology and synthetic biology.
    17 KB (2,806 words) - 01:54, 18 October 2014
  • Team:NCTU Formosa/js/jquery.jticker.js
    // Project and documentation site:
    6 KB (618 words) - 15:08, 4 October 2014
  • Team:TU Delft-Leiden/Human Practices/Appendix
    ...ge building projects. Such a procedure consist of the research of historic documentation and doing sample measurements with a metal detector. Bergman: “We increas
    48 KB (7,984 words) - 23:43, 17 October 2014
  • Team:TU Delft-Leiden/Project/Appendix
    ...umber of casualties decreased to the lowest level since 1999 (the start of documentation of casualties by the Landmine
    18 KB (2,713 words) - 16:46, 6 October 2014
  • Team:Groningen/PolicyandpracticeScenario
    ...al stage. The clinical trials were held between 2020-2026, after which all documentation was submitted to the EMA and FDA for approval regarding safety, risk and qu
    8 KB (1,272 words) - 09:59, 9 October 2014
  • Team:Groningen/Awards/Checklist
    adding new parts. A new application and/or outstanding documentation (quantitative data showing the Part’s/ Device’s function) of a previous
    5 KB (842 words) - 07:45, 10 October 2014
  • Team:UT-Dallas/animate
    ... of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, includ
    60 KB (4,253 words) - 00:36, 14 October 2014
  • Team:Sheffield/zzz
    ... the specific questions asked, as well as the necessary ethics and consent documentation we gained is also presented here.
    2 KB (335 words) - 18:18, 17 October 2014
  • Team:Rutgers/main.html
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    10 KB (1,616 words) - 04:31, 13 October 2014
  • Team:Aachen/Scripts/jssor.js
    * a copy of this software and associated documentation files (the
    87 KB (7,380 words) - 19:27, 11 October 2014
  • Team:ETH Zurich/criteria
    ! Documentation of part characterization in the Registry
    3 KB (413 words) - 02:30, 18 October 2014
  • Wiki/buct/jquery.easing.min.js
    * of conditions and the following disclaimer in the documentation and/or other materials
    5 KB (1,053 words) - 13:18, 8 October 2014
  • Team:Macquarie Australia/Project/Parts
    ...equences of parts, we thoroughly researched these genes and improved their documentation to elucidate the function and interactions between each part in the system.
    16 KB (2,389 words) - 03:03, 18 October 2014
  • Team:Hannover/Medals
    ...ubmit this part to the iGEM Registry. A new application and/or outstanding documentation (quantitative data showing the Part’s/ Device’s function) of a previous
    4 KB (650 words) - 21:15, 17 October 2014
  • Team:TU Eindhoven/Protocols
    ...on numerous protocols were devoloped to guide our experiments and keep our documentation neat and tidy. Because these protocols can also be useful to other projects
    9 KB (1,173 words) - 00:06, 18 October 2014
  • Team:ArtCenter/Attributions
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    7 KB (1,165 words) - 22:54, 11 October 2014
  • Team:Valencia UPV/Core:JS/custom.elements.min.js
    * in the documentation and/or other materials provided with the
    16 KB (2,652 words) - 12:03, 11 October 2014
  • Team:SYSU-Software/Ackmt
    <li><a href="https://2014.igem.org/Team:SYSU-Software/Documentation">Documentation</a></li>
    6 KB (905 words) - 23:54, 17 October 2014
  • Team:Tufts/medal
    ...gistry help page on adding new parts. A new application and/or outstanding documentation (quantitative data showing the Part's/ Device's function) of a previously e
    6 KB (882 words) - 04:02, 14 February 2015
  • Team:Heidelberg/pages/Parts
    ...r assembly. Take a look and visit the Partsregistry to read the associated documentation.</p>
    18 KB (2,730 words) - 18:59, 24 May 2015
  • Team:Dundee/Implementation/methodology
    ...ment criteria compels the completion of a <i> Requirements Document </i> - documentation to show how we were meeting the users needs, the final aims of how the L.A.
    7 KB (1,002 words) - 00:42, 18 October 2014
  • Team:Aachen/Scripts/jssor.slider.js
    * a copy of this software and associated documentation files (the
    162 KB (11,345 words) - 19:29, 11 October 2014
  • Team:USTC-China/assets/css/animate.min.js
    ... of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, includ
    55 KB (4,934 words) - 06:33, 12 October 2014
  • Team:USTC-China/assets/css/animate.min.css
    ... of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, includ
    55 KB (4,934 words) - 06:33, 12 October 2014
  • Team:UT-Dallas/animate.css
    ... of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, includ
    60 KB (4,253 words) - 07:11, 12 October 2014
  • Team:Heidelberg/Software/Linker Software/Documentation
    subtitle= Documentation
    708 B (92 words) - 12:52, 17 October 2014
  • Team:LMU-Munich/Results/Judging
    ...gistry help page on adding new parts. A new application and/or outstanding documentation (quantitative data showing the Part's/ Device's function) of a previously e
    7 KB (1,039 words) - 23:33, 4 December 2014
  • Team:ITB Indonesia/Team
    ... nothing. We introduce synthetic biology, make collaboration, make project documentation, make synthethic biology become enjoyable science, and spread happiness :)<
    17 KB (2,281 words) - 16:33, 17 October 2014
  • Team:Heidelberg/Project
    Setting new standards also for wiki documentation we created and developed a new way of documenting collaborative lab work by
    29 KB (3,798 words) - 08:22, 5 February 2015
  • Team:UCSD Software/Teaml
    <div class="btn btn-lg " id="doc">Documentation</div> window.location.href="https://2014.igem.org/Team:UCSD_Software/Documentation";
    71 KB (9,131 words) - 03:55, 18 October 2014
  • Team:UCSD Software/Attributions
    <div class="btn btn-lg " id="doc">Documentation</div> window.location.href="https://2014.igem.org/Team:UCSD_Software/Documentation";
    14 KB (1,509 words) - 02:46, 18 October 2014
  • Team:UCC Ireland/jquery.easing.min.js
    * of conditions and the following disclaimer in the documentation and/or other materials
    5 KB (1,053 words) - 16:27, 13 October 2014
  • Team:HUST-Innovators
    <br/>Documentation: Zhang Yue, Hou Yuhan
    40 KB (5,823 words) - 00:47, 18 October 2014
  • Team:EPF Lausanne/Acknowledgments
    <p>Celia Lutherbacher helped us polish the documentation.</p>
    14 KB (2,016 words) - 18:39, 13 June 2017
  • Team:Bielefeld-CeBiTec/Project/CO2-fixation/CarbonDioxide
    ...veral goals were formulated to reduce the carbon dioxide emission when the documentation started (<a href="#sumida">Sumida et al., 2012</a>). An additional factor i
    11 KB (1,422 words) - 09:55, 2 December 2014
  • Team:Wageningen UR/outreach/interviews
    ... affecting the soil ecology. We would need field experiments and extensive documentation on how the GMO bacteria works to support that there is no risk of horizonta
    20 KB (3,549 words) - 02:58, 18 October 2014
  • Team:TU Delft-Leiden/Human Practices/DeskStudy
    ...umber of casualties decreased to the lowest level since 1999 (the start of documentation of casualties by the Landmine
    18 KB (2,756 words) - 15:13, 15 October 2014
  • Team:HUST-Innovators/Attributions
    <li>As part of your documentation, keep the links from the menu to the left. </li>
    16 KB (2,099 words) - 02:33, 15 October 2014
  • Team:SUSTC-Shenzhen/static/timelinejs/js/storyjs-embed.js
    this software and associated documentation files (the 'Software'), to deal in
    10 KB (1,656 words) - 11:40, 16 October 2014
  • Team:Bielefeld-CeBiTec/Notebook/Safety
    ... second level of safety regulation. Next, there is the need for a detailed documentation of all experimental work, including all levels of accidents. Last but not l
    12 KB (1,777 words) - 22:20, 17 October 2014
  • Team:UCL/Template:firewall.js
    obtaining a copy of this software and associated documentation
    48 KB (3,777 words) - 10:29, 15 October 2014
  • Team:XMU-China/Judging Achievements
    ...gistry help page on adding new parts. A new application and/or outstanding documentation (quantitative data showing the Part&#39;s/ Device&#39;s function) of a prev
    65 KB (6,978 words) - 03:52, 18 October 2014
  • Team:Tsinghua-A/css/animate.css
    ... of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, includ
    60 KB (4,236 words) - 06:09, 17 October 2014
  • Team:Braunschweig/Notebook-content
    ...and separated at 80-120 V for about 1 h. Last the gel was photographed for documentation.
    54 KB (7,125 words) - 23:10, 17 October 2014

View (previous 250 | next 250) (20 | 50 | 100 | 250 | 500)

Retrieved from "http://2014.igem.org/Special:Search"