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

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

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