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

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