Team:Rutgers/MYS!S WT

From 2011.igem.org

(Difference between revisions)
m
m
 
(2 intermediate revisions not shown)
Line 1: Line 1:
 +
 +
__NOTOC__
 +
{{:Team:Rutgers/Template/Header}}
 +
<html>
<html>
<head>
<head>
Line 5: Line 9:
-
<!--CSS-->
+
</style>
-
<link rel='stylesheet' type='text/css' href='https://2011.igem.org/Template:Team:Rutgers/menu?action=raw&amp;ctype=text/css' />
+
-
 
+
-
<link rel='stylesheet' type='text/css' href='https://2011.igem.org/Template:Team:Rutgers/style?action=raw&amp;ctype=text/css' />
+
-
 
+
-
<!--REHOST-->
+
-
<link rel="stylesheet" href="http://zacstewart.github.com/Meow/jquery.meow.css" type="text/css" media="screen" title="no title" charset="utf-8">
+
-
 
+
-
 
+
-
<!-- jquery -->
+
-
<script type="text/javascript" src="http://code.jquery.com/jquery-1.4.2.js"></script>
+
-
 
+
-
<!-- JS -->
+
-
<script src="http://zacstewart.github.com/Meow/jquery.meow.js" type="text/javascript" charset="utf-8"></script>
+
-
 
+
-
<script type="text/javascript" src="https://2011.igem.org/Template:Team:Rutgers/css_menu?action=raw&amp;ctype=text/javascript"></script>
+
-
 
+
-
 
+
-
<--!
+
-
<link rel="stylesheet" href="menu.css" type="text/css" media="screen" />
+
-
<link rel="stylesheet" href="style.css" /
+
-
>-->
+
-
 
+
-
<script type="text/javascript">
+
-
 
+
-
$(document).ready(function()
+
-
{
+
-
$("#showcase").awShowcase(
+
-
{
+
-
content_width: 800,
+
-
content_height: 600,
+
-
fit_to_parent: false,
+
-
auto: false,
+
-
interval: 3000,
+
-
continuous: false,
+
-
loading: true,
+
-
tooltip_width: 200,
+
-
tooltip_icon_width: 32,
+
-
tooltip_icon_height: 32,
+
-
tooltip_offsetx: 18,
+
-
tooltip_offsety: 0,
+
-
arrows: true,
+
-
buttons: true,
+
-
btn_numbers: true,
+
-
keybord_keys: true,
+
-
mousetrace: false, /* Trace x and y coordinates for the mouse */
+
-
pauseonover: true,
+
-
stoponclick: false,
+
-
transition: 'fade', /* hslide/vslide/fade */
+
-
transition_delay: 0,
+
-
transition_speed: 500,
+
-
show_caption: 'onload', /* onload/onhover/show */
+
-
thumbnails: false,
+
-
thumbnails_position: 'outside-last', /* outside-last/outside-first/inside-last/inside-first */
+
-
thumbnails_direction: 'vertical', /* vertical/horizontal */
+
-
thumbnails_slidex: 1, /* 0 = auto / 1 = slide one thumbnail / 2 = slide two thumbnails / etc. */
+
-
dynamic_height: false, /* For dynamic height to work in webkit you need to set the width and height of images in the source. Usually works to only set the dimension of the first slide in the showcase. */
+
-
speed_change: true, /* Set to true to prevent users from swithing more then one slide at once. */
+
-
viewline: false, /* If set to true content_width, thumbnails, transition and dynamic_height will be disabled. As for dynamic height you need to set the width and height of images in the source. */
+
-
custom_function: null /* Define a custom function that runs on content change */
+
-
});
+
-
});
+
-
 
+
-
</script>
+
-
+
-
<!-- stick in its own global file -->
+
-
    <script>
+
-
      $(document).ready(function() {
+
-
        $.meow({
+
-
          message: $('#onready'),
+
-
          icon: 'folder_32.png'
+
-
        });
+
-
        $('#button').click(function () {
+
-
          $.meow({
+
-
            message: $('#onclick'),
+
-
            icon: 'folder_32.png'
+
-
          });
+
-
        });
+
-
        $('#onchange').change(function () {
+
-
          $.meow({
+
-
            title: 'I have a defined title!',
+
-
            message: $('#onchange'),
+
-
            /*icon: '/icons/chart_16.png'*/
+
-
          });
+
-
        });
+
-
+
-
$('#Link').click(function () {
+
-
          $.meow({
+
-
            message: 'What goes here?',
+
-
            icon: "83-calendar.png"
+
-
          });
+
-
});
+
-
+
-
        $('#selectonchange').change(function () {
+
-
          $.meow({
+
-
            message: $('#selectonchange'),
+
-
            icon: 'folder_32.png'
+
-
          });
+
-
        });
+
-
        $('#sticky').click(function () {
+
-
          $.meow({
+
-
            message: 'I\'m a sticky meow!',
+
-
            icon: 'folder_32.png',
+
-
            sticky: true
+
-
          });
+
-
        });
+
-
        $('#uncloseable').click(function () {
+
-
          $.meow({
+
-
            message: 'I am uncloseable!',
+
-
            icon: 'folder_32.png',
+
-
            closeable: false
+
-
          });
+
-
        });
+
-
        $('#callbacks').click(function () {
+
-
          $.meow({
+
-
            message: 'I have callbacks!',
+
-
            icon: 'folder_32.png',
+
-
            beforeCreateFirst: function () {
+
-
              alert(this + ' is the first meow!');
+
-
            },
+
-
            beforeCreate: function () {
+
-
              alert('About to create ' + this);
+
-
            },
+
-
            afterCreate: function () {
+
-
              alert('Just created ' + this);
+
-
            },
+
-
            onTimeout: function () {
+
-
              alert(this + ' just timed out.');
+
-
            },
+
-
            beforeDestroy: function () {
+
-
              alert('About to destroy ' + this);
+
-
            },
+
-
            afterDestroy: function () {
+
-
              alert('And it\'s gone');
+
-
            },
+
-
            afterDestroyLast: function () {
+
-
              alert('There are no meows left :3');
+
-
            }
+
-
          });
+
-
        });
+
-
      });
+
-
    </script>
+
-
 
+
-
 
+
<style type="text/css">
<style type="text/css">
-
 
<!--
<!--
-
table.mesa {
+
.style3 {
-
color: #f1f1f1;
+
-
}
+
-
table.mesa th {
+
-
padding: 0px;
+
-
background-color: #f1f1f1;
+
-
}
+
-
table.mesa td {
+
-
padding: 0px;
+
-
background-color: #f1f1f1;
+
-
}
+
-
body,td,th {
+
-
font-family: Arial, Helvetica, sans-serif;
+
-
font-size: 36px;
+
text-align: center;
text-align: center;
-
color: #CCC;
 
-
}
 
-
body {
 
-
margin-left: 0px;
 
-
margin-top: 0px;
 
-
margin-right: 0px;
 
-
margin-bottom: 0px;
 
-
}
 
-
.Test {
 
-
color: #252525;
 
-
text-align: right; font-size: px;
 
-
}
 
-
.Test strong {
 
-
color: #666;
 
-
font-size: 48px;
 
-
font-weight: bold;
 
-
}
 
-
 
-
 
-
<style type="text/css">
 
-
html, body { height:100% }
 
-
body, h1, h2, p {
 
-
border:0;
 
-
margin:0;
 
-
padding:0;
 
-
text-align: left;
 
-
}
 
-
body {
 
-
font-family: helvetica, arial, sans-serif;
 
-
background-image:-webkit-gradient(radial, 50% 50%, 0, 50% 50%, 300, from(#888), to(#444));
 
-
background-image:url();
 
-
background-size:100% 100%;
 
-
-webkit-perspective:500px;
 
-
-moz-perspective:500px;
 
-
background-repeat: repeat-x;
 
-
 
-
/* IE10 */
 
-
background-image: -ms-linear-gradient(top right, #212121 40%, #D4D4D4 70%, #FFFFFF 100%);
 
-
 
-
/* Mozilla Firefox */
 
-
background-image: -moz-linear-gradient(top right, #212121 40%, #D4D4D4 70%, #FFFFFF 100%);
 
-
 
-
/* Opera */
 
-
background-image: -o-linear-gradient(top right, #212121 40%, #D4D4D4 70%, #FFFFFF 100%);
 
-
 
-
/* Webkit (Safari/Chrome 10) */
 
-
background-image: -webkit-gradient(linear, right top, left bottom, color-stop(.4, #212121), color-stop(0.7, #D4D4D4), color-stop(1, #FFFFFF));
 
-
 
-
/* Webkit (Chrome 11+) */
 
-
background-image: -webkit-linear-gradient(top right, #212121 40%, #D4D4D4 70%, #FFFFFF 100%);
 
-
 
-
/* Proposed W3C Markup */
 
-
background-image: linear-gradient(top right, #212121 40%, #D4D4D4 70%, #FFFFFF 100%);
 
-
 
-
background-color: transparent;
 
-
 
-
 
-
 
-
 
-
 
-
}
 
-
a { color:#bbb; }
 
-
#text {
 
-
position:absolute;
 
-
width:998px;
 
-
height:53px;
 
-
left:601px;
 
-
top:398px;
 
-
margin-left:-300px;
 
-
margin-top:-60px;
 
-
text-align:center;
 
-
text-transform:uppercase;
 
-
-webkit-tranform:translateZ(0);
 
-
-webkit-transition-duration:0.05s;
 
-
-moz-tranform:translateZ(0);
 
-
color:#f3f3f3;
 
-
text-shadow:0 0 1px rgba(0,0,0,.2);
 
-
}
 
-
 
-
 
-
 
-
p {
 
-
top:0;
 
-
width:90%;
 
-
font-size:16px;
 
-
color:#333;
 
-
text-shadow:0 -1px 0 rgba(0,0,0,0.1);
 
-
font-family: Arial, Helvetica, sans-serif;
 
-
padding-top: 10px;
 
-
padding-right: 10;
 
-
padding-bottom: 10px;
 
-
padding-left: 10;
 
-
right: 2px;
 
-
text-align: left;
 
-
}
 
-
a:link {
 
-
color: #333;
 
-
}
 
-
a:visited {
 
-
color: #333;
 
-
}
 
-
a:hover {
 
-
color: #666;
 
-
}
 
-
a:active {
 
-
color: #FFF;
 
-
}
 
-
.floatingHeader {
 
-
  position: fixed;
 
-
  top: 0;
 
-
  visibility: hidden;
 
-
}
 
-
.imgshadow2 table {
 
-
text-align: left;
 
-
}
 
-
.imgshadow2 table tr td div p {
 
-
text-align: left;
 
-
}
 
-
.imgshadow2 table {
 
-
font-size: 24px;
 
-
text-align: justify;
 
-
}
 
-
.imgshadow2 table tr td div p {
 
-
text-align: justify;
 
-
}
 
-
.imgshadow2 {
 
-
text-align: left;
 
-
}
 
-
 
-
.style2 {font-family: Verdana, Geneva, sans-serif; text-align: center; color: #333333; }
 
-
.style3 {
 
-
color: #666666;
 
-
font-size: 24px;
 
-
}
 
-
.imgshadow2 blockquote table {
 
-
text-align: left;
 
-
}
 
-
.imgshadow2 blockquote table {
 
-
text-align: left;
 
-
}
 
-
.imgshadow2 blockquote table {
 
-
text-align: left;
 
}
}
 +
-->
</style>
</style>
 +
</head>
-
</head>
 
<body leftmargin="0" topmargin="0" marginwidth="0" marginheight="0">
<body leftmargin="0" topmargin="0" marginwidth="0" marginheight="0">
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
-
<table width="60%" border="0" align="center" cellpadding="0" cellspacing="20" bordercolor="#F1F1F1" background="https://static.igem.org/mediawiki/2011/9/96/Stripe.png" bgcolor="#F1F1F1" >
+
<table width="60%" border="0" align="center" cellpadding="0" cellspacing="20" bordercolor="#F1F1F1" background="https://static.igem.org/mediawiki/2011/9/96/Stripe.png" >
   <tr>
   <tr>
     <td height="58" colspan="2" td background="https://static.igem.org/mediawiki/2011/9/96/Stripe.png"><p class="style3">RUTGERS iGEM TEAM WIKI</p>
     <td height="58" colspan="2" td background="https://static.igem.org/mediawiki/2011/9/96/Stripe.png"><p class="style3">RUTGERS iGEM TEAM WIKI</p>
Line 340: Line 46:
           </tr>
           </tr>
         <tr>
         <tr>
-
           <td colspan="6" bgcolor="#F1F1F1" class="stuff"><h4 class="shadow">Walk through</h4>
+
           <td colspan="6" class="stuff"><h4 class="shadow">Walk through</h4>
             <p class="stuff">    One of the main ideas behind MYS!S was to make synthetic biology more accessible to a wider “spectrum” of people.  We want the program to provide an environment that enables the user to understand and explore the changes being made to the DNA in a more intuitive manner.  </p>
             <p class="stuff">    One of the main ideas behind MYS!S was to make synthetic biology more accessible to a wider “spectrum” of people.  We want the program to provide an environment that enables the user to understand and explore the changes being made to the DNA in a more intuitive manner.  </p>
             <p class="stuff">In addition, MYS!S is designed to be highly customizable by providing the user with the ability to add and modify components such as an organism’s codon usage table and new assembly standards.  The ultimate goal is to create a program that can be customized by the user for their specific work and the lab protocols they are comfortable with.              </p>
             <p class="stuff">In addition, MYS!S is designed to be highly customizable by providing the user with the ability to add and modify components such as an organism’s codon usage table and new assembly standards.  The ultimate goal is to create a program that can be customized by the user for their specific work and the lab protocols they are comfortable with.              </p>
Line 362: Line 68:
             <p class="stuff">&nbsp;</p>
             <p class="stuff">&nbsp;</p>
             <p class="stuff">Next, we need to enter all the information required to perform an assembly standard check.  The fields that have to be filled in are the name field, the organism, the standard, and the plasmid.  Obviously the user also needs a nucleotide sequence to analyze.  This sequence needs to be entered in the original DNA sequence text area.  Note MYS!S requires the nucleotide sequence to start with ATG and be in frame.</p>
             <p class="stuff">Next, we need to enter all the information required to perform an assembly standard check.  The fields that have to be filled in are the name field, the organism, the standard, and the plasmid.  Obviously the user also needs a nucleotide sequence to analyze.  This sequence needs to be entered in the original DNA sequence text area.  Note MYS!S requires the nucleotide sequence to start with ATG and be in frame.</p>
-
             <p class="stuff"><img src="https://static.igem.org/mediawiki/2011/2/29/Screen_Shot_2011-09-25_at_11.04.31_AM.jpg" width="901" height="643"></p>
+
             <p class="stuff"><img src="http://gears.rutgers.edu/images/Screen%20Shot%202011-09-25%20at%2011.05.36%20AM.jpg" width="901" height="643"></p>
             <p class="stuff">&nbsp;</p>
             <p class="stuff">&nbsp;</p>
             <p class="stuff">&nbsp;</p>
             <p class="stuff">&nbsp;</p>
Line 387: Line 93:
         <tr>
         <tr>
          
          
-
           <td colspan="6" bgcolor="#f1f1f1" class="stuff"><h4 class="shadow"><img src="https://static.igem.org/mediawiki/2011/6/68/16-line-chart.png" width="30" height="24"> I. Protocols </h4>
+
           <td colspan="6" class="stuff"><h4 class="shadow"><img src="https://static.igem.org/mediawiki/2011/6/68/16-line-chart.png" width="30" height="24"> I. Protocols </h4>
             <p class="stuff">In the protocol tab is a BioCoder compatible C++ file that contains the lab procedures for mutating the original Lovtap DNA into a standard safe form.  The C++ file can be compiled with the BioCoder software available here.
             <p class="stuff">In the protocol tab is a BioCoder compatible C++ file that contains the lab procedures for mutating the original Lovtap DNA into a standard safe form.  The C++ file can be compiled with the BioCoder software available here.
Line 417: Line 123:
         <tr>
         <tr>
          
          
-
           <td colspan="6" bgcolor="#f1f1f1" class="stuff"><h4 class="shadow"><img src="https://static.igem.org/mediawiki/2011/e/e5/59-flag.png" > beta</h4>
+
           <td colspan="6" class="stuff"><h4 class="shadow"><img src="https://static.igem.org/mediawiki/2011/e/e5/59-flag.png" > beta</h4>
             <p class="stuff">Unfortunately, we’re talking about the capabilities of the future MYS!S v.10, for now all we have is the beta edition.  So for the time being, these are the imminent improvements we would like to make for the second version of MYS!S.
             <p class="stuff">Unfortunately, we’re talking about the capabilities of the future MYS!S v.10, for now all we have is the beta edition.  So for the time being, these are the imminent improvements we would like to make for the second version of MYS!S.
</p>
</p>
Line 455: Line 161:
         <tr>
         <tr>
          
          
-
           <td colspan="6" bgcolor="#f1f1f1" class="stuff"><h4 class="shadow"><img src="https://static.igem.org/mediawiki/2011/8/85/56-cloud.png" width="24" height="16"> Github</h4>
+
           <td colspan="6" class="stuff"><h4 class="shadow"><img src="https://static.igem.org/mediawiki/2011/8/85/56-cloud.png" width="24" height="16"> Github</h4>
             <p class="stuff">MYS!S is currently available as an Eclipse download.  It will very soon be available as a java application.  </p>
             <p class="stuff">MYS!S is currently available as an Eclipse download.  It will very soon be available as a java application.  </p>
-
             <p class="stuff">The downloads can be obtained from our github site.              </p>
+
             <p class="stuff">The downloads can be obtained from our GitHub site.              </p>
             <p class="stuff"><img src="https://static.igem.org/mediawiki/2011/8/81/Github_white_black_cat_32.png" width="32" height="32"> <a href="https://github.com/RutgersGEARS/iGEM-Rutgers-Software">https://github.com/RutgersGEARS/iGEM-Rutgers-Software </a></p>
             <p class="stuff"><img src="https://static.igem.org/mediawiki/2011/8/81/Github_white_black_cat_32.png" width="32" height="32"> <a href="https://github.com/RutgersGEARS/iGEM-Rutgers-Software">https://github.com/RutgersGEARS/iGEM-Rutgers-Software </a></p>
             <p class="stuff">MYS!S is still a work in progress.  Please feel free to report any bugs or crashes that occur as issues on our github page.                </p>
             <p class="stuff">MYS!S is still a work in progress.  Please feel free to report any bugs or crashes that occur as issues on our github page.                </p>

Latest revision as of 03:36, 29 September 2011


Rutgers 2011 iGEM Team: Complex Circuits in Synthetic Biology

Rutgers 2011 iGEM Team: Complex Circuits in Synthetic Biology

 

 

RUTGERS iGEM TEAM WIKI

MYS!S
Menu >> The Bacterial Etch-a-Sketch >> Goals

MYS!S: An Introduction

Walk through

One of the main ideas behind MYS!S was to make synthetic biology more accessible to a wider “spectrum” of people. We want the program to provide an environment that enables the user to understand and explore the changes being made to the DNA in a more intuitive manner.

In addition, MYS!S is designed to be highly customizable by providing the user with the ability to add and modify components such as an organism’s codon usage table and new assembly standards. The ultimate goal is to create a program that can be customized by the user for their specific work and the lab protocols they are comfortable with.

To showcase the capabilities of MYS!S we would like to walk you through an analysis of a current BioBrick in the registry. For this example we are going to use part BBa_K191006 which is the protein coding sequence for LovTAP. LovTAP was used by both of our laboratory projects Etch-a-Sketch and Full Adder. One of the issues with LovTAP is that it contains restriction sites not allowed by some BioBrick assembly standards.

Lets say we want to transform the LovTAP coding region into e-coli After opening MYS!S, navigate to the screen to manage components. To do this go to the MYS!S menu and click “Manage Components”.

 

It will open up a screen that will allow the user to manage which organisms and assembly standards the program handles.

From this screen the user can add organism codon tables, modify existing ones, and delete those not needed anymore. The same functionality applies to standards. The user can specify the prefix, suffix, and the restriction sequences that the nucleotide sequence should not contain.

 

 

 

 

Now we are going to exit the manage components screen and open a new assembly standard check. You can find the assembly standard check option by going under the file menu then click “New” then click “Assembly Standard Check”.

 

 

Next, we need to enter all the information required to perform an assembly standard check. The fields that have to be filled in are the name field, the organism, the standard, and the plasmid. Obviously the user also needs a nucleotide sequence to analyze. This sequence needs to be entered in the original DNA sequence text area. Note MYS!S requires the nucleotide sequence to start with ATG and be in frame.

 

 

After these fields are completed the user can hit the go button to perform an assembly standard check.

The original DNA sequence and the modified sequence are displayed top and bottom. All proposed changes in the modified sequence are colored green the corresponding nucleotides in the unmodified sequence are colored purple. The primers needed to transform the original Lovtap sequence to the assembly standard acceptable Lovtap are shown in alignment with the 5’ and 3’ ends labeled.

 

 

Features

I. Protocols

In the protocol tab is a BioCoder compatible C++ file that contains the lab procedures for mutating the original Lovtap DNA into a standard safe form. The C++ file can be compiled with the BioCoder software available here. http://research.microsoft.com/en-us/um/india/projects/biocoder/

 

II. Rna Structure Analysis

In the RNA structure tab there are images of the unmodified and modified RNA structure. We hope that this will help the user decide whether the changes are structurally advantageous. Hopefully in the future more advanced RNA structure modeling algorithms can be implemented to help the user make an informed decision.

 

 

Future of MYS!S

beta

Unfortunately, we’re talking about the capabilities of the future MYS!S v.10, for now all we have is the beta edition. So for the time being, these are the imminent improvements we would like to make for the second version of MYS!S.

Better algorithms for modifying DNA

Currently, when determining how to modify DNA MYS!S does not take into account the eventual RNA structure and whether the changes will inhibit protein production. We would like to incorporate algorithms that make changes to DNA in a way that will increase the amount of protein formed by translation. On the same note, it might also be helpful for a synthetic biologist not just to increase protein production but maybe to limit it.

 

Not just support site directed mutagenesis

Right now MYS!S for a codon optimization creates a large number of primers for a sequence of say 700bp. We’re talking about upwards of 50 primers making site directed mutagenesis realistically impossible. We would like MYS!S to support other methods of manipulating physical DNA.

 

Better visualization methods for RNA structure

We want the user to be able to visually check whether the RNA structure is acceptable. If it is not acceptable the user should be able to manually modify the DNA sequence to improve the RNA structure. Preference for lab protocols : Not all labs do things the same, MYS!S should be able to customize lab protocols to how the user’s lab gets things done.

 

 

Where can I get MYS!S?

Github

MYS!S is currently available as an Eclipse download. It will very soon be available as a java application.

The downloads can be obtained from our GitHub site.

https://github.com/RutgersGEARS/iGEM-Rutgers-Software

MYS!S is still a work in progress. Please feel free to report any bugs or crashes that occur as issues on our github page.

https://github.com/RutgersGEARS/iGEM-Rutgers-Software/issues

 

 

 

 

 

 

 

 

 

 

 

 

 

Retrieved from "http://2011.igem.org/Team:Rutgers/MYS!S_WT"