Team:Amsterdam/software/logbook designer/future perspective

From 2012.igem.org

(Difference between revisions)
 
(2 intermediate revisions not shown)
Line 8: Line 8:
<h1>Logbook Designer: Future Perspective</h1>
<h1>Logbook Designer: Future Perspective</h1>
-
__TOC__
+
__NOTOC__
The Logbook Designer is not yet a product that is able to fully push the boundaries of the Cellular Logbook such as, for example, Blast is in its field. This page provides some insight on what is needed to add and adjust to this webtool if the Cellular Logbook is to be a massive platform for new technology.
The Logbook Designer is not yet a product that is able to fully push the boundaries of the Cellular Logbook such as, for example, Blast is in its field. This page provides some insight on what is needed to add and adjust to this webtool if the Cellular Logbook is to be a massive platform for new technology.
<div class='clear'></div>
<div class='clear'></div>
-
 
-
</div>
 
-
<div id="sub-menu" class="content-block">
 
<h2>Optimization</h2>
<h2>Optimization</h2>
The Logbook Designer presents the user with a construct that does not break any rules when plasmid design is taken into account. However, it does not attempt to create the optimal Cellular Logbook plasmid. A sub-optimal plasmid is more than good enough when creating a proof of concept, which is what we are doing with our iGEM project. But when we think about industrializing the Cellular Logbook, it is necessary that every plasmid is optimized. If the Logbook Designer wants to achieve this, the algorithm does not only have to take into account the optimal distances between features, optimal features and optimal combination of features. The algorithm also has to think ahead when it comes to primer design and cloning steps required to create the plasmid. In order to have a fully functional and industrialized Logbook Designer, the optimization of the algorithm is an absolute necessity.
The Logbook Designer presents the user with a construct that does not break any rules when plasmid design is taken into account. However, it does not attempt to create the optimal Cellular Logbook plasmid. A sub-optimal plasmid is more than good enough when creating a proof of concept, which is what we are doing with our iGEM project. But when we think about industrializing the Cellular Logbook, it is necessary that every plasmid is optimized. If the Logbook Designer wants to achieve this, the algorithm does not only have to take into account the optimal distances between features, optimal features and optimal combination of features. The algorithm also has to think ahead when it comes to primer design and cloning steps required to create the plasmid. In order to have a fully functional and industrialized Logbook Designer, the optimization of the algorithm is an absolute necessity.
-
 
-
</div>
 
-
<div id="sub-menu" class="content-block">
 
<h2>Database</h2>
<h2>Database</h2>
-
[[File:Amsterdam_db_future.png|right|300px]]
+
[[File:Amsterdam_db_future.png|right|300px|thumb|Figure 1: An abstract view of the user interaction with a database, allowing the user to communicate with the database by uploading, downloading and editting plasmids]]
In order to make the Cellular Logbook the standard biosensor system not only is quick and efficient plasmid design a necessity, but also the easy to retrieve, edit and distribute already existing plasmids. The easiest way to accomplish all this is by designing and maintaining a Cellular Logbook database on a dedicated server. This database should allow for easy to use uploading, downloading and editing of Cellular Logbook plasmids.
In order to make the Cellular Logbook the standard biosensor system not only is quick and efficient plasmid design a necessity, but also the easy to retrieve, edit and distribute already existing plasmids. The easiest way to accomplish all this is by designing and maintaining a Cellular Logbook database on a dedicated server. This database should allow for easy to use uploading, downloading and editing of Cellular Logbook plasmids.
-
 
-
</div>
 
-
<div id="sub-menu" class="content-block">
 
<h2>Literature</h2>
<h2>Literature</h2>

Latest revision as of 03:54, 27 September 2012