Team:Penn State/MultipleStartCodons

From 2012.igem.org

(Difference between revisions)
 
(11 intermediate revisions not shown)
Line 1: Line 1:
<html>
<html>
-
 
-
 
-
 
<head>
<head>
-
  <title>Multiple Start Codons</title>
+
<title>Multiple Start Codons Overview</title>
-
 
+
-
 
+
-
 
+
-
  <style type="text/css" media="all">
+
-
<!--
+
-
/*
+
-
* This is used just to have a position: relative so I can then put the tabbed panels in it.
+
-
* it is ugly and a mess, I wonder what people where thinking when they thought about this
+
-
* boxing model.
+
-
*/
+
-
div#tabFrame
+
-
  {
+
-
  position: relative;
+
-
width: 600px;
+
-
  }
+
-
 
+
-
 
+
-
div#tabMenuDiv
+
-
  {
+
-
  /* position MUST be relative so to palce this and the TabFiller into a common z-order reference
+
-
    * this fix the Internet Explorer crappy BUG
+
-
    */
+
-
  position: relative;
+
-
  /* since the z-index is four this will be on top of the tabFiller border */
+
-
  z-index: 4;
+
-
  }
+
-
 
+
-
/* this is used to fill the tabs with something so they do not mess up with the page
+
-
* This div will be used to set the size of the tabPane, the width is automatic.
+
-
* so, basically, the only thing to set is the height, use the em unit !
+
-
*/
+
-
div#tabFiller
+
-
  {
+
-
  /* position MUST be relative so to palce this and the TabFiller into a common z-order reference
+
-
    * this fix the Internet Explorer crappy BUG
+
-
    */
+
-
  position: relative;
+
-
  background: #F0f0f0;
+
-
  border: 2px solid black;
+
-
  height: 300px;
+
-
  /* z-Index must be lower than the one of tabMenuDiv since this div should be below it */
+
-
  z-index:1;
+
-
  }
+
-
 
+
-
/*
+
-
* This defines the general properties of the tabMenu something like borders, colors, etc.
+
-
* One important property is the z-index, it must be above the other panels.
+
-
*/
+
-
span.tabMenu, span.tabMenuActive, span.tabMenuOver
+
-
  {
+
-
  /* the background must be the same as the tabFiller background */
+
-
  background: #f0f0f0;
+
-
  border: 2px solid black;
+
-
  margin: 0px 0px 0px 12px;    /* this moves the buttons to the right */
+
-
  padding: 0px 12px 0px 10px;
+
-
  }
+
-
 
+
-
span.tabMenuActive
+
-
  {
+
-
  /* the color must be the same as the tabFiller background */
+
-
  border-bottom: 2px solid #f0f0f0;
+
-
  }
+
-
 
+
-
span.tabMenuOver
+
-
  {
+
-
  /* You can set whatever foreground and background color you wish */
+
-
  background:  #FFCC66;
+
-
  color: #FFFFFF;
+
-
  }
+
-
 
+
-
/* the various tab panels are in absolute position relative to the parent, so basically
+
<style type="text/css">
-
* they all overlap one with the other.
+
-
* The problem is that their size is dependent on the content and therefore that has to be adjusted.
+
-
* to do this I need of javascript...
+
-
* If you want to define some special fonts for the tabbed pane, do it here.
+
-
*/
+
-
div.tabPane
+
-
  {
+
-
  position: absolute;
+
-
  margin: 4px;
+
-
  overflow: auto;
+
-
  /* the background of this must be the same of tabFiller */
+
-
  background: #f0f0f0;
+
-
  }
+
-
-->
+
body {background:#e0e0e0; color:#303030; font:76% tahoma, verdana, sans-serif; margin:0; padding:15px 0 0;}
body {background:#e0e0e0; color:#303030; font:76% tahoma, verdana, sans-serif; margin:0; padding:15px 0 0;}
#container {
#container {
Line 140: Line 53:
li {margin:0 0 3px 0;}
li {margin:0 0 3px 0;}
-
 
-
 
-
 
-
/* Toptabs menu */
 
-
#toptabs {font-size:.8em; margin:10px auto -13px; width:760px;}
 
-
#toptabs p {color:gray; text-align:right;}
 
-
.toptab {background:#f0f0f0 url(../images/corner2.gif) top right no-repeat; border-bottom:1px solid #e0e0e0; color:gray; margin:0 0 0 4px; padding:4px 5px 3px; text-decoration:none;}
 
-
.toptab:hover {background:#fafafa url(../images/corner2.gif) top right no-repeat; border-bottom:1px solid #eaeaea; color:#505050; text-decoration:none;}
 
-
.activetoptab {
 
-
background: #fff url(../images/corner2.gif) top right no-repeat;
 
-
border-bottom: 1px solid #fff;
 
-
margin: 0 0 0 4px;
 
-
padding: 4px 5px 3px;
 
-
text-decoration: none;
 
-
color: #282C2D;
 
-
}
 
-
.activetoptab:hover {border-bottom:1px solid #fff; text-decoration:none;}
 
/* Navitabs menu */
/* Navitabs menu */
#navitabs {clear:both;}
#navitabs {clear:both;}
-
.navitab {background:#e0e0e0 url(../images/corner.gif) top right no-repeat; border-bottom:1px solid #fff; border-left:1px solid #fff; font-size:1.1em; margin:0 0 4px; padding:4px 8px; text-decoration:none;}
+
.navitab {background:#e0e0e0 url(https://static.igem.org/mediawiki/2012/7/72/Corner.gif) top right no-repeat; border-bottom:1px solid #fff; border-left:1px solid #fff; font-size:1.1em; margin:0 0 4px; padding:4px 8px; text-decoration:none;}
-
.navitab:hover {background:#d0d0d0 url(../images/corner.gif) top right no-repeat; border-bottom:1px solid #fff; text-decoration:none;}
+
.navitab:hover {background:#d0d0d0 url(https://static.igem.org/mediawiki/2012/7/72/Corner.gif) top right no-repeat; border-bottom:1px solid #fff; text-decoration:none;}
-
.activenavitab {background:#505050 url(../images/corner.gif) top right no-repeat; color:#fff; font-size:1.1em; margin:0 0 5px; padding:4px 8px 5px; text-decoration:none;}
+
.activenavitab {background:#505050 url(https://static.igem.org/mediawiki/2012/7/72/Corner.gif) top right no-repeat; color:#fff; font-size:1.1em; margin:0 0 5px; padding:4px 8px 5px; text-decoration:none;}
.activenavitab:hover {color:#fff; text-decoration:none;}
.activenavitab:hover {color:#fff; text-decoration:none;}
Line 197: Line 93:
border-right: 1px solid #d8d8d8;
border-right: 1px solid #d8d8d8;
float: left;
float: left;
-
width: 620px;
+
width: 600px;
margin-top: 0;
margin-top: 0;
-
margin-right: 5;
 
margin-bottom: 0;
margin-bottom: 0;
-
margin-left: 5;
 
padding-top: 0;
padding-top: 0;
-
padding-right: 15px;
 
padding-bottom: 0;
padding-bottom: 0;
padding-left: 0;
padding-left: 0;
Line 215: Line 108:
#sidebar li {list-style:none;}
#sidebar li {list-style:none;}
ul.sidelink li {list-style:none; margin:0 0 3px; padding:0;}
ul.sidelink li {list-style:none; margin:0 0 3px; padding:0;}
-
ul.sidelink li a{background:#f0f0f0 url(../images/corner.gif) top right no-repeat; border:none; display:block; margin:5px 10px 5px 0; padding:3px 4px 3px 8px; text-align:left; width:140px;}
+
ul.sidelink li a{background:#f0f0f0 url(https://static.igem.org/mediawiki/2012/7/72/Corner.gif) top right no-repeat; border:none; display:block; margin:5px 10px 5px 0; padding:3px 4px 3px 8px; text-align:left; width:140px;}
-
ul.sidelink li a:hover {background:#e0e0e0 url(../images/corner.gif) top right no-repeat; border:none; text-decoration:none;}
+
ul.sidelink li a:hover {background:#e0e0e0 url(https://static.igem.org/mediawiki/2012/7/72/Corner.gif) top right no-repeat; border:none; text-decoration:none;}
/* Footer */
/* Footer */
Line 257: Line 150:
width: 280px;
width: 280px;
float: right;
float: right;
-
background-image: url(../images/Sweatshirt_Logo.jpg);
+
background-image: url(https://static.igem.org/mediawiki/2012/4/4b/Sweatshirt_Logo.jpg);
padding-bottom: 15px;
padding-bottom: 15px;
background-repeat: no-repeat;
background-repeat: no-repeat;
Line 264: Line 157:
height: 54px;
height: 54px;
width: 116px;
width: 116px;
-
background-image: url(../images/psuLogo.jpeg);
+
background-image: url(https://static.igem.org/mediawiki/2012/f/f9/PsuLogo.jpeg);
}
}
-
</style>
 
-
  <script language="JavaScript" type="text/javascript" src="tab-panel.js">
+
/*Tabbed Panels*/
-
  </script>
+
#maintabs {clear:both;}
 +
.maintab {
 +
border-bottom: 1px solid #fff;
 +
border-left: 1px solid #fff;
 +
font-size: 1.1em;
 +
margin: 0 0 4px;
 +
padding: 4px 8px;
 +
text-decoration: none;
 +
background-color: #CCCCCC;
 +
background-image: url(https://static.igem.org/mediawiki/2012/7/72/Corner.gif);
 +
background-repeat: no-repeat;
 +
background-position: right top;
 +
}
 +
.maintab:hover {
 +
background:#d0d0d0 url(https://static.igem.org/mediawiki/2012/7/72/Corner.gif) top right no-repeat; border-bottom:1px solid #fff; text-decoration:none;
 +
}
 +
.activemaintab {background:#f0f0f0 url(https://static.igem.org/mediawiki/2012/7/72/Corner.gif) top right no-repeat; color:#333; font-size:1.1em; margin:0 0 5px; padding:4px 8px 5px; text-decoration:none;}
 +
.activemaintab:hover {color:#fff; text-decoration:none;}
 +
/* Header description area */
 +
#tabfiller {
 +
clear: both;
 +
color: #fff;
 +
margin: 5px 0 15px;
 +
padding: 0 0 5px 0;
 +
background-image: url(../images/indexNav1.jpg);
 +
background-color: #f0f0f0;
 +
background-repeat: no-repeat;
 +
background-position: left bottom;
 +
text-align: left;
 +
font-size: 18pt;
 +
}
 +
#tabfiller p {
 +
font-size: 10pt;
 +
line-height: 1.3em;
 +
padding: 0 15px 15px 15px;
 +
width: 570px;
 +
color: #333;
 +
}
 +
#tabfiller h2 {
 +
color: #333;
 +
padding: 15px 15px 0;
 +
text-align: left;
 +
font-size: 18pt;
 +
 +
}
 +
#tabfiller h3 {
 +
color: #333;
 +
padding: 15px 15px 0;
 +
text-align: left;
 +
font-size: 14pt;
 +
 +
#tabfiller a {border-color:#fff; color:#fff; text-decoration:none;}
 +
</style>
</head>
</head>
-
 
-
 
-
 
-
 
-
 
<body>
<body>
 +
<div id="container">
<div id="container">
   <div id="logoiGEM"></div>
   <div id="logoiGEM"></div>
Line 286: Line 226:
   <div id="navitabs">
   <div id="navitabs">
     <h2 class="hide">Sample navigation menu:</h2>
     <h2 class="hide">Sample navigation menu:</h2>
-
     <a class="navitab" href="https://2012.igem.org/Team:Penn_State">Home</a><span class="hide"> | </span> <a class="navitab" href="https://2012.igem.org/Team:Penn_State/Team">Team</a><span class="hide"> | </span> <a class="activenavitab" href="#">Projects</a><span class="hide"> | </span> <a class="navitab" href="https://2012.igem.org/Team:Penn_State/Parts">Parts</a><span class="hide"> | </span> <a class="navitab" href="#">Modeling</a><span class="hide"> | </span> <a class="navitab" href="https://2012.igem.org/Team:Penn_State/Notebook">Notebook</a><span class="hide"> | </span> <a class="navitab" href="https://2012.igem.org/Team:Penn_State/Attributions">Other</a> </div>
+
     <a class="navitab" href="https://2012.igem.org/Team:Penn_State">Home</a>
 +
    <span class="hide"> | </span> <a class="navitab" href="https://2012.igem.org/Team:Penn_State/Team">Team</a>
 +
    <span class="hide"> | </span> <a class="activenavitab" href="https://2012.igem.org/Team:Penn_State/Project">Projects</a>
 +
    <span class="hide"> | </span> <a class="navitab" href="https://2012.igem.org/Team:Penn_State/Parts">Parts</a>
 +
    <span class="hide"> | </span> <a class="navitab" href="https://2012.igem.org/Team:Penn_State/Modeling">Modeling</a>
 +
    <span class="hide"> | </span> <a class="navitab" href="https://2012.igem.org/Team:Penn_State/Notebook">Notebook</a>
 +
    <span class="hide"> | </span> <a class="navitab" href="https://2012.igem.org/Team:Penn_State/Other">Other</a>
 +
  </div>
 +
   
   <div id="desc">
   <div id="desc">
     <h2>Multiple Start Codons</h2>
     <h2>Multiple Start Codons</h2>
-
     <p>Multiple start codons are a frustrating and persistent pheomenon in molcular biology. While some may see them as a nuisance in the laboratory, we see them as a topic of investigation. By learning the specific conditions of codon slippage, we may be better prepared as scientists to recognize its potential as a research tool.   </p>
+
     <p>A frustrating yet commonly observed phenomenon in the lab is the production of unexpected proteins. These occurrences may be explainable by multiple start codons in the mRNA strand. Codon slippage is a theory practically untouched by research, and this project aspires to shed some light on the issue.</p>
-
    <p class="right"><a href="https://2012.igem.org/Team:Penn_State/new page">new page</a> &raquo;</p>
+
   </div>
   </div>
 +
 
   <div id="main">
   <div id="main">
     <h2>Multiple Start Codons</h2>
     <h2>Multiple Start Codons</h2>
-
<p onload="bodyOnLoad()" onResize="raisePanel(currentMenuIndex)">
 
-
 
-
<div id="tabFrame">
 
-
 
-
<div id="tabMenuDiv">
 
-
<span class="tabMenu" id="tabMenu0" onClick="return raisePanel(0)" onMouseOver="mouseOver(0)" onMouseOut="mouseOut(0)" >
 
-
  First Tab Menu</span>
 
-
<span class="tabMenu" id="tabMenu1" onClick="return raisePanel(1)" onMouseOver="mouseOver(1)" onMouseOut="mouseOut(1)">
 
-
  Second Tab Menu</span>
 
-
<span class="tabMenu" id="tabMenu2" onClick="return raisePanel(2)" onMouseOver="mouseOver(2)" onMouseOut="mouseOut(2)">
 
-
  Third Tab Menu</span>
 
-
</div>
 
-
 
-
<div class="tabPane" id="tabPane0">
 
-
<p>Vtab #1</p>
 
-
 
-
<p>in another paragraph</p>
 
-
</div>
 
-
 
-
<div class="tabPane" id="tabPane1">
 
-
tab #2
 
-
</div>
 
-
 
-
<div class="tabPane" id="tabPane2">
 
-
pane#3
 
-
</div>
 
-
 
-
<div id="tabFiller" ></div>
 
-
 
-
</div>
 
-
 
-
 
-
 
-
 
-
 
-
<script>
 
-
 
-
 
-
// Global vars to hold the object in the panel.
 
-
tabPanelArray = new Array(3);
 
-
tabMenuArray = new Array(3);
 
-
currentMenuIndex = 0;
 
-
 
-
/**
 
-
* This MUST be called on page load to fill up the shared global values.
 
-
* Having the panes object accessible by index makes things easier.
 
-
* This is also a good place to display the first page.
 
-
*/
 
-
function bodyOnLoad()
 
-
  {
 
-
  tabPanelArray[0] = getItemObj('tabPane0');
 
-
  tabPanelArray[1] = getItemObj('tabPane1');
 
-
  tabPanelArray[2] = getItemObj('tabPane2');
 
-
 
-
  tabMenuArray[0] = getItemObj('tabMenu0');
 
-
  tabMenuArray[1] = getItemObj('tabMenu1');
 
-
  tabMenuArray[2] = getItemObj('tabMenu2');
 
-
 
-
  raisePanel ( currentMenuIndex );
 
-
  }
 
-
 
-
/**
 
-
* Utility function just to show an error if I try to get non existen objects
 
-
*/
 
-
function getItemObj ( itemId )
 
-
  {
 
-
  obj = document.getElementById(itemId);
 
-
 
-
  if ( obj == null ) alert('Script Error: id='+itemId+' does not exist');
 
-
 
-
  return obj;
 
-
  }
 
-
 
-
 
-
/**
 
-
* raising a panel means setting all the other panels to a lower level
 
-
* and setting the raided panel to a higher level
 
-
* note that also the size must be set correctly !
 
-
* to activate a menu i switch the class between active and not active.
 
-
*/
 
-
function raisePanel ( panelIndex )
 
-
  {
 
-
  for (index=0; index<3; index++ )
 
-
      {
 
-
      // the panel with the index == wantedIndex gets raised.
 
-
      if (index == panelIndex )
 
-
        {
 
-
        raiseObject (tabPanelArray[index], 4);
 
-
        tabMenuArray[index].className = 'tabMenuActive';
 
-
        }
 
-
      else
 
-
        {
 
-
        raiseObject (tabPanelArray[index], 2);
 
-
        tabMenuArray[index].className = 'tabMenu';
 
-
        }
 
-
      }
 
-
 
-
  currentMenuIndex=panelIndex;
 
-
 
-
  return true;
 
-
  }
 
-
 
-
/**
 
-
* When I raise a panel I may as well check for the correct size and fix it.
 
-
* it is a bit of doubling work, but it does not happens often !
 
-
*/
 
-
function raiseObject ( target, level )
 
-
  {
 
-
  /* the number of pixels we shave to the outside filler to fit everything in
 
-
    * this value depends on the border set for the filler div and possible padding
 
-
    * it is best to experiment a bit with it.
 
-
    */
 
-
  safeMargin = 6;
 
-
 
-
  // the size of the panels depends on the size of the tabFiller
 
-
  obj = getItemObj('tabFiller');
 
-
 
-
  newWidth = obj.offsetWidth - safeMargin;
 
-
  if ( newWidth < safeMargin ) newWidth = safeMargin;
 
-
  target.style.width = newWidth+'px';
 
-
 
-
  newHeight =obj.offsetHeight - safeMargin;
 
-
  if ( newHeight < safeMargin ) newHeight = safeMargin;
 
-
  target.style.height = newHeight+'px';
 
-
 
-
  // setting the z-index last should optimize possible resize.
 
-
  target.style.zIndex=level;
 
-
  }
 
-
 
-
/**
 
-
* When we mouse out of the span we restore the class to the default value
 
-
* But this only if we are not over the current selected menu
 
-
*/
 
-
function mouseOut ( menuIndex )
 
-
  {
 
-
  if ( menuIndex == currentMenuIndex ) return true;
 
-
 
-
  tabMenuArray[menuIndex].className = 'tabMenu';
 
-
  }
 
-
 
-
/**
 
-
* When we mouse over of the span we set the class of the span to the over one
 
-
* But this only if we are not over the current selected menu
 
-
*/
 
-
function mouseOver ( menuIndex )
 
-
  {
 
-
  if ( menuIndex == currentMenuIndex ) return true;
 
-
 
-
  tabMenuArray[menuIndex].className = 'tabMenuOver';
 
-
  }
 
-
 
-
</script>
 
-
 
 +
    <div id="maintabs">
 +
    <h2 class="hide">Sample navigation menu:</h2>
 +
    <a class="activemaintab" href="#">Overview</a>
 +
    <span class="hide"> | </span> <a class="maintab" href="https://2012.igem.org/Team:Penn_State/MSC_Design">Design</a>
 +
    <span class="hide"> | </span> <a class="maintab" href="https://2012.igem.org/Team:Penn_State/MSC_Results">Results</a>
 +
    </div>
 +
   
 +
  <div id="tabfiller">
 +
<h3>Background</h3>
 +
    <p>mRNA is the molecule that carries information about the sequence of amino acids in a protein. However, much like the lines on a sheet of paper, the protein coding sequence of an mRNA molecule does not start right at the beginning, or top of the page. Instead, once the mRNA is bound by a ribosome, a start codon must first be read before the protein can be translated. This start codon is generally AUG, or Methionine.
 +
</p>
 +
<h3>The Problem</h3>
 +
<p>Once this start codon in read the ribosome will continue reading and building the polypeptide (protein) until a stop codon is reached. But what happens if you have two AUG codons close together? That is the question we are attempting to answer.</p>
 +
<p>We are trying to understand what happens when there are two start codons very close together, but out of frame. Out of frame refers to how the ribosome reads the mRNA. Remember those codons and how they are groups of three bases on the mRNA? The reading frame refers to which group of three. If you start at one base and read the bases in groups of three from that point on, that is one frame of reference. If you then move your start point ahead one base, then you are reading in a new reading frame. If you advance you starting point one more base, that is the third reading frame. If you advance it again you are now back in your first reading frame, but you have skipped the first codon. We are looking into what happens when you have multiple start codons close together, but in different reading frames. Which frame will be preferred?</p>
 +
  </div>
   </div>
   </div>
 +
 
 +
 
   <div id="sidebar">
   <div id="sidebar">
-
     <h3>Check these Out! </h3>
+
     <h3>Check these Out!</h3>
     <ul class="sidelink">
     <ul class="sidelink">
-
       <li><a href="#">Judging Criteria</a></li>
+
       <li><a href="https://2012.igem.org/Team:Penn_State/Judging_Criteria">Judging Criteria</a></li>
-
       <li><a href="#">Parts</a></li>
+
       <li><a href="https://2012.igem.org/Team:Penn_State/Parts">Parts</a></li>
-
       <li><a href="#">Human Practices</a></li>
+
       <li><a href="https://2012.igem.org/Team:Penn_State/Human_Practices">Human Practices</a></li>
     </ul>
     </ul>
     <h3>Picture Gallery</h3>
     <h3>Picture Gallery</h3>
     <img class="photo" src="../images/test.jpg" height="100" width="130" alt="" />
     <img class="photo" src="../images/test.jpg" height="100" width="130" alt="" />
     <h3>What to Put Here?</h3>
     <h3>What to Put Here?</h3>
 +
    <h3>Projects</h3>
     <ul>
     <ul>
-
       <li><a href="#">Possible Link</a></li>
+
       <li><a href="https://2012.igem.org/Team:Penn_State/Multiple_Start_Codons">Multiple Start Codons</a></li>
-
       <li><a href="#">Possible Link</a></li>
+
       <li><a href="https://2012.igem.org/Team:Penn_State/Bidirectional_Promoters">Bidirectional Promoters</a></li>
 +
      <li><a href="https://2012.igem.org/Team:Penn_State/Codon_Optimization">Codon Optimization</a></li>
     </ul>
     </ul>
   </div>
   </div>
Line 468: Line 282:
   </div>
   </div>
</div>
</div>
-
 
-
</body>
 
 +
</body>
</html>
</html>

Latest revision as of 07:02, 3 October 2012

Multiple Start Codons Overview

Multiple Start Codons

A frustrating yet commonly observed phenomenon in the lab is the production of unexpected proteins. These occurrences may be explainable by multiple start codons in the mRNA strand. Codon slippage is a theory practically untouched by research, and this project aspires to shed some light on the issue.

Multiple Start Codons

Sample navigation menu:

Overview | Design | Results

Background

mRNA is the molecule that carries information about the sequence of amino acids in a protein. However, much like the lines on a sheet of paper, the protein coding sequence of an mRNA molecule does not start right at the beginning, or top of the page. Instead, once the mRNA is bound by a ribosome, a start codon must first be read before the protein can be translated. This start codon is generally AUG, or Methionine.

The Problem

Once this start codon in read the ribosome will continue reading and building the polypeptide (protein) until a stop codon is reached. But what happens if you have two AUG codons close together? That is the question we are attempting to answer.

We are trying to understand what happens when there are two start codons very close together, but out of frame. Out of frame refers to how the ribosome reads the mRNA. Remember those codons and how they are groups of three bases on the mRNA? The reading frame refers to which group of three. If you start at one base and read the bases in groups of three from that point on, that is one frame of reference. If you then move your start point ahead one base, then you are reading in a new reading frame. If you advance you starting point one more base, that is the third reading frame. If you advance it again you are now back in your first reading frame, but you have skipped the first codon. We are looking into what happens when you have multiple start codons close together, but in different reading frames. Which frame will be preferred?

Retrieved from "http://2012.igem.org/Team:Penn_State/MultipleStartCodons"