Team:Davidson-MissouriW/Tools
From 2010.igem.org
Jstevens12 (Talk | contribs) |
|||
(10 intermediate revisions not shown) | |||
Line 5: | Line 5: | ||
<!--<div id="SubWrapper"> --> | <!--<div id="SubWrapper"> --> | ||
<div id="mission_box"> <h2> iGEM Davidson – Missouri Western 2010: Tools </h2> | <div id="mission_box"> <h2> iGEM Davidson – Missouri Western 2010: Tools </h2> | ||
- | <h3>The team has designed several tools | + | <h3>The team has designed several tools to guide and support our iGEM project.</h3> |
</div> | </div> | ||
<br><br><br><br><br><br> | <br><br><br><br><br><br> | ||
+ | <div id="Veripart"> | ||
+ | <a href="http://72.22.219.205/sequence"> | ||
+ | <h3>VeriPart</h3> | ||
+ | </a><a NAME="veripart"> | ||
+ | <table cellpadding=0 cellspacing=0> | ||
+ | <tbody> | ||
+ | <tr bgcolor="#ede8e2"> | ||
+ | <td width=30> | ||
+ | </td> | ||
+ | <td width=580> | ||
+ | <p>Verifying BioBrick parts can be difficult and tedious by hand. To solve this problem, we have developed a tool to identify BioBrick parts within a given DNA sequence. When a sequence is entered, the program checks the last archived version of the BioBrick Parts Registry and returns the best matched part. If your desired part is not found, you can attempt to align the sequence you entered with the part you desire. When a device is found in your sequence, you can click to view the sequences of individual parts. An alignment of the sequence with the part is presented to the user allowing for easier sequence analysis.</p> | ||
+ | </td> | ||
+ | <td align=center width=600> | ||
+ | <a href="http://72.22.219.205/sequence"><img src="https://static.igem.org/mediawiki/2010/3/32/Davidson-MissouriWveripart.png" alt="Veri" width=400/></a> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </tbody> | ||
+ | </table> | ||
+ | </div> | ||
+ | <br><br> | ||
<div id="Oligator"> | <div id="Oligator"> | ||
<a href="http://gcat.davidson.edu/igem10/index.html"> | <a href="http://gcat.davidson.edu/igem10/index.html"> | ||
Line 32: | Line 52: | ||
<div id="Optimoose"> | <div id="Optimoose"> | ||
<a href="http://gcat.davidson.edu/igem10/opt/opt_index.html"> | <a href="http://gcat.davidson.edu/igem10/opt/opt_index.html"> | ||
- | <h3> | + | <h3>Optimus</h3> |
</a><a NAME="optimoose"> | </a><a NAME="optimoose"> | ||
<table cellpadding=0 cellspacing=0> | <table cellpadding=0 cellspacing=0> | ||
Line 40: | Line 60: | ||
</td> | </td> | ||
<td width=580> | <td width=580> | ||
- | <p> | + | <p>Optimus is a tool designed to allow the user to evaluate the expression level of a gene sequence in <i>E. coli</i> using either RCBS-PC or the CAI formula. Additionally, the user has the option to optimize or deoptimize the sequence by using one of those two formulas. If the optimized or deoptimized option is selected, the user will be given a new sequence whose codons have been changed to reflect the best, or worst, codons as determined by the selected formula. Assuming the entered sequence is in frame, the amino acid sequence is preserved. |
- | + | Optimus serves as a mechanism by which we can engineer optimized and deoptimized sequences which represent a given "weight" to the items in a knapsack based on their protein production.</p> | |
</td> | </td> | ||
<td align=center width=600> | <td align=center width=600> | ||
- | <a href="http://gcat.davidson.edu/igem10/opt/opt_index.html"><img src="https://static.igem.org/mediawiki/2010/ | + | <a href="http://gcat.davidson.edu/igem10/opt/opt_index.html"><img src="https://static.igem.org/mediawiki/2010/2/25/Davidson-MissouriWoptimus.png" alt="Tools" width=280/></a> |
</td> | </td> | ||
</tr> | </tr> | ||
Line 54: | Line 74: | ||
<a NAME="Simulator"> | <a NAME="Simulator"> | ||
<a href="https://static.igem.org/mediawiki/2010/4/4a/ConstructSim.zip"> | <a href="https://static.igem.org/mediawiki/2010/4/4a/ConstructSim.zip"> | ||
- | <h3> | + | <h3>SimuLox</h3> |
</a> | </a> | ||
<table cellpadding=0 cellspacing=0> | <table cellpadding=0 cellspacing=0> | ||
Line 65: | Line 85: | ||
</td> | </td> | ||
<td align=center width=600> | <td align=center width=600> | ||
- | <a href="https://static.igem.org/mediawiki/2010/4/4a/ConstructSim.zip"><img src="https://static.igem.org/mediawiki/2010/ | + | <a href="https://static.igem.org/mediawiki/2010/4/4a/ConstructSim.zip"><img src="https://static.igem.org/mediawiki/2010/8/87/Davidson-MissouriWconsim.png" alt="sim" width=355/></a> |
</td> | </td> | ||
</tr> | </tr> | ||
Line 71: | Line 91: | ||
</table> | </table> | ||
</div> | </div> | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
<br><br> | <br><br> | ||
<center><a href="#main_wrapper">Top</a></center> | <center><a href="#main_wrapper">Top</a></center> |
Latest revision as of 22:19, 22 October 2010
iGEM Davidson – Missouri Western 2010: Tools
The team has designed several tools to guide and support our iGEM project.
VeriPart
The Oligator
Optimus
SimuLox
In order to better understand our fluorescent protein - TetA constructs, we designed a simulation of the cre-lox system. This simulation allows the user to test our pre-determined constructs as well as custom constructs from any number of promoters, lox sites, fluorescent proteins, essential genes, and/or terminators. The program will then show either a single, animated simulation that will allow the user to see how the lox sites interact, or it will run many simulations and then generate a histogram that shows the distribution of what fluorescent proteins were expressed. In addition, if the user chooses to include weights for the "items" and a capacity for the knapsack the program will tell you whether or not your construct has exceeded the capacity. In order to run the program, download the jar file. To see the actual percentages behind the histogram, the program needs to be run through a command line tool, but other than that simply double clicking the jar file to run it should be sufficient. |