Team:Heidelberg/pages/midnightdoc

From 2014.igem.org

(Difference between revisions)
Line 5: Line 5:
For these reasons, we created a software which does just that. Our MidnightDoc enables reproducibility by making sure that documenting experimental methods becomes a fun activity; a natural extension of normal lab routine. In the following, we will describe the main design principles behind this fine piece of software.
For these reasons, we created a software which does just that. Our MidnightDoc enables reproducibility by making sure that documenting experimental methods becomes a fun activity; a natural extension of normal lab routine. In the following, we will describe the main design principles behind this fine piece of software.
-
===Overview===
+
===Lay out your plan, then record what you did===
 +
The most important design principle behind MidnightDoc is the fact that it accompanies lab work and in fact makes it easier. In order to illustrate this, consider the simple example of a restriction or ligation experiment: The user will first look up for the concentrations of his fragments, as measured for example by a spectrophotometer. Then, based on these concentration measurements and the manufacturer guidelines, which might specify the required amount of each fragment (e.g. in micromol or nanograms) or the ratio between them, the user will calculate the necessary volumina. Only after these calculation have been done, will the user be able to mix these components and then start the reactions. Once this has been done, he will document some of the aforementioned numbers (e.g. the volumina used) in his labbook for future reference.
 +
===You decide the level of detail===
 +
===Backtracking and Propagation===
-
=References=
+
===Version control===
-
[1] http://freegamedev.net/wiki/Portable_binaries#System_libraries_that_cannot_be_bundled
+
-
[2] http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html
+
===The web===
 +
 
 +
 
 +
 
 +
=References=

Revision as of 23:30, 17 October 2014

Contents

Introduction

Documentation is one of the most important aspects of any scientific project. Nevertheless, maintaining a detailed log of all experiments performed can often be a daunting task, especially when consistency and standardization across multiple persons is required. This consistency is particularly important in the context of iGEM, where group work is of paramount importance. Also, as many iGEM projects build upon results of preceding teams, a standardized way of documenting would further enhance this interaction. Reproducibility 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 researchers in general.

For these reasons, we created a software which does just that. Our MidnightDoc enables reproducibility by making sure that documenting experimental methods becomes a fun activity; a natural extension of normal lab routine. In the following, we will describe the main design principles behind this fine piece of software.

Lay out your plan, then record what you did

The most important design principle behind MidnightDoc is the fact that it accompanies lab work and in fact makes it easier. In order to illustrate this, consider the simple example of a restriction or ligation experiment: The user will first look up for the concentrations of his fragments, as measured for example by a spectrophotometer. Then, based on these concentration measurements and the manufacturer guidelines, which might specify the required amount of each fragment (e.g. in micromol or nanograms) or the ratio between them, the user will calculate the necessary volumina. Only after these calculation have been done, will the user be able to mix these components and then start the reactions. Once this has been done, he will document some of the aforementioned numbers (e.g. the volumina used) in his labbook for future reference.

You decide the level of detail

Backtracking and Propagation

Version control

The web

References