Design usu.html

From 2010.igem.org

(Difference between revisions)
 
(7 intermediate revisions not shown)
Line 1: Line 1:
-
{{:Team:Utah_State/header1}}
+
{{:Team:Utah_State/usu_bg}}
 +
{{:Team:Utah_State/usu_header}}
 +
{{:Team:Utah_State/usu_menu}}
-
<html>
 
-
<head>
 
-
<title>iGEM 2010 - USU - Design</title>
+
<div id="HomeCenterCenterBB">
 +
<div id="Tittle">
 +
Design
 +
</div>
 +
=Plasmid Design=
 +
In this project, we designed our integration vector as a standardized and adaptable plasmid to allow for integration in a variety of species. The full integration vector (Figure 1) allows for the easy exchange of resistance genes and integration regions with only a restriction digest and ligation of the new regions. A variety of recombination regions can be added to the plasmid to allow for gene integration in any desired area of the genome, and multiple resistance genes allows for more complex experiments where multiple regions are integrated and selected for simultaneously.
 +
The integration plasmid is based off of pSB1A3, which allows it to replicate in high copy number in ''E. coli'' during the construction of the BioBrick part. This provides large amounts of DNA for analysis and future transformations into cyanobacteria.
 +
[[Image:USU_Plamid_1C.png]]
 +
 +
'''Figure 1.''' Integration Plasmid pSB1A3_IntC. Plasmid contains two exchangeable recombination regions RS1 and RS2, each flanked by restriction sites for easy modification. Plasmid also contains the Chloramphenicol resistance gene (CmR), which is also easily exchanged through restriction digest.
-
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+
==Overview of Integration==
 +
In ''Synechocystis'' sp. PCC 6803, the cells naturally take up DNA from the media and recombine it with the genome in regions of homology. If two regions of homology are closely spaced on the chromosome and the foreign DNA, the regions between the two homologous regions are exchanged (Figure 2).  After recombination with the recombination plasmid in this project, the exchanged fragment of genomic DNA is lost from the cell due to the plasmid’s inability to replicate in PCC 6803.
-
</head>
+
[[Image:USU_Integration_1.png|428px]]
 +
[[Image:USU_Integration_2.png|435px]]
 +
 
 +
'''Figure 2.''' (A) Once the integration plasmid comes across the homologous part of the genome, crossing over occurs between the plasmid and the chromosome. (B) Since there are two recombination regions, the crossing over resolves with the regions between the homologous regions switching locations, leaving the BioBrick and resistance gene in the genome. The plasmid is then lost from the cells as it is unable to replicate in PCC 6803.
-
<!--/*Change this link with the one from iGEM*/-->
+
==Advantages and Applications of Integration==
 +
The use of an integration plasmid for synthetic biological engineering possesses many advantages, and a few disadvantages, compared to using plasmid vectors.
-
<body leftmargin="0" topmargin="0" marginwidth="0" marginheight="0">
+
<ul>
 +
<li>With integration, the copy number of the inserted BioBrick is more precisely known than with plasmids, allowing for more predicable levels of protein expression. Inserted into the main genome, only one or two copies of the gene will exist in the cell at any given time. If higher copy number is desired, and the species possesses other chromosomes of different copy number, the integration can be targeted to these other chromosomes. The copy number of chromosomes is generally more stable, varying only by one or two copies from cell to cell, whereas a plasmid vary between cells by as much as several hundred copies.
 +
<li> Integration also affords more stable replication and retention of the BioBrick, as entire chromosomes are rarely lost from a cell, but plasmids with low replication rates may be lost to some daughter cells during division. This is especially true for species such as Synechocystis, which do not retain plasmids very efficiently.
 +
<li>Traditional cloning with plasmids is also limited in scale. Plasmid vectors start becoming unstable in cells at around 20,000 bp in length, and may be retained only in a small proportion of cells. By inserting the BioBricks into the chromosome from integration vector, a series of 20,000 bp inserts can be added to the cell, giving a potentially limitless capacity for modification.
 +
<li>Using integration, more dramatic changes can be made to cells than with traditional plasmid cloning. If the recombination regions flank a gene you wish to remove from the cells, the act of inserting the BioBrick (or merely the antibiotic selection marker) will cause the gene to be deleted. This can enable new genes to be inserted to replace those in the host species, for example exchanging a gene requiring that a cofactor be added to the media with a gene homolog that doesn’t need the cofactor could enable a bio-product to be produced much less expensively.
 +
<li>With proper homologous regions, genes could also be inserted into the middle of operons, allowing gene expression to occur in a predictable fashion, with little effort expended in choosing proper promoter conditions.
 +
</ul>
 +
=Promoter and RBS Design=
 +
==Genome Analyzer Program==
 +
Team member Cody Tramp constructed a computer program to analyze a GenBank genome file and provide information about promoter and RBS design (see Figure 3 for a screenshot). The program (which is currently undergoing compatibility revisions before releasing it for general use) creates a searchable database of individual genes that can be filtered for similarity to promoter consensus sequences or can be used to determine common structural features of the genome. In this project, the program was used to identify the codon usage profile for Synechocystis and to determine the consensus ribosome binding site.
 +
 +
[[Image:USU_Program.png]]
 +
'''Figure 3.''' Screenshot of Cody’s Genome Analyzer program. The left window shows the database of all genes in the genome, and the right window is a pop-up window containing links to major databases with information on the gene. The pop-up window can also be programmed to highlight matches to consensus promoter sequences or ribosome binding sites.
-
<div class="container">
+
==Consensus Ribosome Binding Site==
 +
The ribosome bindings site used in device construction are vital to the final performance of the part. RBS sequences, however, are dependent on the sequence of the 3’ end of the 16S rRNA ribosomal subunit, which can vary from species to species. Using the Genome Analyzer program, we were able to determine the consensus RBS of ''Synechocystis'' sp. PCC 6803 by analyzing the sequence upstream of every gene in the genome. The sequence complimentary to the 3’ end of the 16S rRNA sequence for ''Syncechocystis'' (and thus the RBS as seen on the mRNA) is AAAGGAGGT. The Genome Analyzer program found each of these bases to be conserved in different percentages of genes, and that some sequences surrounding the RBS to be highly conserved as well (Figure 4). Thus, the full consensus RBS for ''Synechocystis'' is TTTAAAGGAGGTTAAA, followed by the start codon.
 +
 +
[[Image:USU_RBS_Program.png]]
 +
'''Figure 4.''' Ribosome binding site consensus sequence as determined by Genome Analyzer program analyzing the upstream region of every gene in the genome. Note positions are number relative to the first base pair match with the 16S rRNA sequence, and not with the start codon. Colors on the lower sequence indicate level of conservation, with red indicating high conservation, yellow moderate, and green low.
-
<div class="content"><!--Add here the content of the site-->
 
-
 
-
<table width="850px" border="0">
 
-
 
-
  <tr>
 
-
 
-
    <td style="font-size: 20px; font-weight: bold;">&nbsp;</td>
 
-
 
-
  </tr>
 
-
 
-
 
-
  <tr bgcolor="#ADD8E6" style="color: #000000;">
 
-
 
-
    <td style="font-size: 35px; font-weight: bold;" height="50px">Design</td>
 
-
 
-
  </tr>
 
-
 
-
  <tr bgcolor="#87AFC7">
 
-
 
-
    <td bgcolor="#87AFC7" height="1px"></td>
 
-
 
-
  </tr>
 
-
 
-
  <tr bgcolor="#ADD8E6" style="color: #000000;">
 
-
 
-
    <td>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque vel sapien lectus, in dignissim leo. Duis diam tortor, facilisis id tincidunt in, fringilla a est. Ut elit libero, venenatis porttitor ultrices eget, rutrum sed diam. Duis semper libero posuere lorem pharetra pretium. Nulla a lacus eu ante elementum rutrum et a neque. Aenean volutpat tellus non est tempus rhoncus in nec lacus. Vivamus ac nibh at eros porta iaculis. Duis non magna ligula. Vivamus nec ipsum quis magna faucibus eleifend pretium sed lectus. Pellentesque sit amet augue non dolor tempor pharetra. Vivamus rhoncus turpis sed risus mollis sit amet ullamcorper tellus molestie. Vivamus eget lorem eget purus scelerisque sollicitudin vel ut ipsum. Nam aliquet urna odio. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Etiam semper condimentum felis, eget mollis neque pulvinar et. Cras a augue enim, a facilisis nisi. Suspendisse potenti. Sed sit amet est augue. Quisque non tortor enim, quis pretium ante.<br/><br/>
 
-
 
-
 
-
 
-
Integer consequat convallis diam, quis cursus justo ultricies sit amet. Integer in dui nec magna scelerisque aliquet. Etiam placerat, velit at semper pretium, purus massa fringilla dui, id malesuada lectus est id enim. Nunc sit amet lobortis leo. Aliquam ut purus id mauris molestie faucibus molestie at sapien. Vestibulum ut nulla velit, id convallis risus. Pellentesque gravida, sem eu faucibus accumsan, urna ante facilisis ante, at tempus ante purus at massa. Proin leo arcu, tristique at sollicitudin eget, dictum non risus. Curabitur faucibus ante interdum enim suscipit mattis. Mauris massa ante, sagittis ac lobortis eu, pulvinar sed velit. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae; Cras ac nisl sed quam facilisis laoreet. Sed faucibus magna sit amet ante blandit in aliquet quam bibendum. Donec viverra convallis pretium. Curabitur purus neque, sodales ut pretium ut, commodo a erat. Pellentesque at risus nulla, a fermentum nisi. Nullam et justo at enim volutpat porttitor quis ut sem. Quisque odio diam, pretium et adipiscing gravida, varius sed justo.</td>
 
-
 
-
  </tr>
 
-
 
-
  <tr>
 
-
 
-
    <td bgcolor="#ADD8E6" height="1px"></td>
 
-
 
-
  </tr>
 
-
 
-
  <tr bgcolor="#ADD8E6" style="color: #000000;">
 
-
 
-
    <td>Integer consequat convallis diam, quis cursus justo ultricies sit amet. Integer in dui nec magna scelerisque aliquet. Etiam placerat, velit at semper pretium, purus massa fringilla dui, id malesuada lectus est id enim. Nunc sit amet lobortis leo. Aliquam ut purus id mauris molestie faucibus molestie at sapien. Vestibulum ut nulla velit, id convallis risus. Pellentesque gravida, sem eu faucibus accumsan, urna ante facilisis ante, at tempus ante purus at massa. Proin leo arcu, tristique at sollicitudin eget, dictum non risus. Curabitur faucibus ante interdum enim suscipit mattis. Mauris massa ante, sagittis ac lobortis eu, pulvinar sed velit. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae; Cras ac nisl sed quam facilisis laoreet. Sed faucibus magna sit amet ante blandit in aliquet quam bibendum. Donec viverra convallis pretium. Curabitur purus neque, sodales ut pretium ut, commodo a erat. Pellentesque at risus nulla, a fermentum nisi. Nullam et justo at enim volutpat porttitor quis ut sem. Quisque odio diam, pretium et adipiscing gravida, varius sed justo.
 
-
 
-
<p>
 
-
<groupparts>iGEM010 Utah_State</groupparts>
 
-
 
-
</td>
 
-
 
-
  </tr>
 
-
 
-
  <tr>
 
-
 
-
    <td style="font-size: 20px; font-weight: bold;">&nbsp;</td>
 
-
 
-
  </tr>
 
-
 
-
</table>
 
 +
==Codon Usage Profile==
 +
In addition to determining the consensus RBS for optimal gene expression, the codon usage of the gene’s themselves must be matched with the new host genome’s tRNA usage in order to be efficiently produced. The codons for each amino acid that are favored by tRNA’s can be roughly deduced from the frequencies with which each codon is used across all the genes in the genome. Figure 5 shows the summary of the codon usage profile for ''Synechocystis'' sp. PCC 6038 as generated by the Genome Analyzer program.
 +
[[Image:USU_Codon_Usage_Program.png|900px]]
 +
 +
'''Figure 5.''' Codon usage profile for ''Synechocystis'' sp. PCC 6038 as generated by the Genome Analyzer program. Blue bars indicate relative usage levels within that amino acid, scaled relative to the most used codon for each amino acid. All values are in percent.
</div>
</div>
-
 
+
{{:Team:Utah_State/usu_footer}}
-
</div>
+
-
 
+
-
 
+
-
 
+
-
 
+
-
</body>
+
-
 
+
-
<head>
+
-
<style>
+
-
table {
+
-
  background-color: #ADD8E6;
+
-
  font-color: white;
+
-
  color:white;
+
-
}
+
-
 
+
-
a.menu {
+
-
  background-color: transparent;
+
-
  color: white;
+
-
  width: 12em;
+
-
}
+
-
 
+
-
.firstHeading {
+
-
  color:white;
+
-
}
+
-
 
+
-
#bodyContent {
+
-
background-color: transparent;
+
-
}
+
-
 
+
-
#content {
+
-
background-color: transparent;
+
-
}
+
-
 
+
-
#footer-box {
+
-
  background-color: #231F20;
+
-
}
+
-
p {
+
-
  color:white;
+
-
}
+
-
body {
+
-
  background-color:transparent;
+
-
}
+
-
.firstHeading {
+
-
  display:none;
+
-
}
+
-
 
+
-
</style>
+
-
</head>
+
-
 
+
-
 
+
-
 
+
-
</p><p><br />
+
-
</p><p>
+
-
<style type="text/css">
+
-
body {background-color:#231f20; background-image:url(http://2010.igem.org/wiki/images/b/b6/USU2010banner.jpg);/*Change this link with the one from iGEM*/
+
-
background-repeat:no-repeat;}
+
-
#content{
+
-
border:0px;
+
-
}
+
-
 
+
-
</style>
+
-
 
+
-
 
+
-
</p><p>
+
-
<head>
+
-
 
+
-
<style type="text/css">
+
-
 
+
-
.container { position:inherit; height:auto; width: 900px; margin:auto; z-index:4; background-color: transparent; background-repeat:no-repeat}
+
-
 
+
-
.header { position:inherit; height:158px; width: 966px; margin:auto; z-index:2; background-image:url(http://2010.igem.org/wiki/images/b/b6/USU2010banner.jpg);/*Change this link with the one from iGEM*/
+
-
 
+
-
background-repeat:no-repeat;}
+
-
 
+
-
.menu {position: relative; height:auto; width: 970px; margin:auto; z-index:3;}
+
-
 
+
-
.menu1 {position: relative; height:auto; width: 900px; margin:auto; z-index:7;}
+
-
 
+
-
.intro {position: relative; height:auto; width: 900px; margin:auto; z-index:9;}
+
-
 
+
-
.content{position:inherit; height:auto; width: 850px; margin:auto; z-index:4; background-color:#FFF; background-repeat:no-repeat}
+
-
 
+
-
.content_logo{}
+
-
 
+
-
.footer{position:relative; height:auto; width: 900px; margin:auto; z-index:5; background-image:url(http://2010.igem.org/wiki/images/7/7d/Background.gif); background-color:#000}
+
-
 
+
-
.bottom{position:relative; height:16px; width: 900px; margin:auto; z-index:6; background-image:url(http://2010.igem.org/wiki/images/7/7d/Background.gif)/*Change this link with the one from iGEM*/}
+
-
 
+
-
 
+
-
 
+
-
.slideshow { height:auto; width: 224px; margin-left:200px; margin-top:40px; position:relative}
+
-
 
+
-
.slideshow img { padding: 15px; border: 0px solid #ccc; background-color:transparent;  background-image:url(http://2010.igem.org/wiki/images/7/7d/Background.gif);}
+
-
 
+
-
body {
+
-
 
+
-
background-attachment:fixed;
+
-
 
+
-
background-image: url(http://2010.igem.org/wiki/images/7/7d/Background.gif)/*Change this link with the one from iGEM*/;
+
-
 
+
-
background-repeat: no-repeat;
+
-
 
+
-
        background-color: #3CF;
+
-
 
+
-
}
+
-
 
+
-
 
+
-
content{
+
-
                background:transparent url("http://2010.igem.org/wiki/images/8/86/Transpa30.png") center top fixed repeat-y;
+
-
                padding: 0px;
+
-
        margin:0 auto;
+
-
                border: none; 
+
-
            }
+
-
 
+
-
 
+
-
ul.topnav {
+
-
 
+
-
list-style: none;
+
-
 
+
-
padding: 0 20px;
+
-
 
+
-
margin: 0;
+
-
 
+
-
float: left;
+
-
 
+
-
width: 900px;
+
-
 
+
-
background: #222;
+
-
 
+
-
font-size: 1.2em;
+
-
 
+
-
background: url(http://2010.igem.org/wiki/images/1/1b/Topnav_bg.gif)/*Change this link with the one from iGEM*/ no-repeat;
+
-
 
+
-
}
+
-
 
+
-
ul.topnav li {
+
-
 
+
-
float: left;
+
-
 
+
-
margin: 0;
+
-
 
+
-
padding: 0 15px 0 0;
+
-
 
+
-
position: relative; /*--Declare X and Y axis base for sub navigation--*/
+
-
 
+
-
}
+
-
 
+
-
ul.topnav li a{
+
-
 
+
-
padding: 10px 5px;
+
-
 
+
-
color: #fff;
+
-
 
+
-
display: block;
+
-
 
+
-
text-decoration: none;
+
-
 
+
-
float: left;
+
-
 
+
-
}
+
-
 
+
-
ul.topnav li a:hover{
+
-
 
+
-
background: url(images/topnav_hover.gif) no-repeat center top;
+
-
 
+
-
}
+
-
 
+
-
ul.topnav li span { /*--Drop down trigger styles--*/
+
-
 
+
-
width: 17px;
+
-
 
+
-
height: 35px;
+
-
 
+
-
float: left;
+
-
 
+
-
background: url(images/subnav_btn.gif) no-repeat center top;
+
-
 
+
-
}
+
-
 
+
-
ul.topnav li span.subhover {background-position: center bottom; cursor: pointer;} /*--Hover effect for trigger--*/
+
-
 
+
-
ul.topnav li ul.subnav {
+
-
 
+
-
list-style: none;
+
-
 
+
-
position: absolute; /*--Important - Keeps subnav from affecting main navigation flow--*/
+
-
 
+
-
left: 0; top: 35px;
+
-
 
+
-
background: #333;
+
-
 
+
-
margin: 0; padding: 0;
+
-
 
+
-
display: none;
+
-
 
+
-
float: left;
+
-
 
+
-
width: 170px;
+
-
 
+
-
border: 1px solid #111;
+
-
 
+
-
}
+
-
 
+
-
ul.topnav li ul.subnav li{
+
-
 
+
-
margin: 0; padding: 0;
+
-
 
+
-
border-top: 1px solid #252525; /*--Create bevel effect--*/
+
-
 
+
-
border-bottom: 1px solid #444; /*--Create bevel effect--*/
+
-
 
+
-
clear: both;
+
-
 
+
-
width: 170px;
+
-
 
+
-
}
+
-
 
+
-
html ul.topnav li ul.subnav li a {
+
-
 
+
-
float: left;
+
-
 
+
-
width: 145px;
+
-
 
+
-
background: #333 url(images/dropdown_linkbg.gif)/*Change this link with the one from iGEM*/ no-repeat 10px center;
+
-
 
+
-
padding-left: 20px;
+
-
 
+
-
}
+
-
 
+
-
html ul.topnav li ul.subnav li a:hover { /*--Hover effect for subnav links--*/
+
-
 
+
-
background: #222 url(images/dropdown_linkbg.gif)/*Change this link with the one from iGEM*/ no-repeat 10px center;
+
-
 
+
-
}
+
-
 
+
-
 
+
-
 
+
-
body,td,th {
+
-
 
+
-
font-family: Arial, Helvetica, sans-serif;
+
-
 
+
-
}
+
-
 
+
-
</style>
+
-
 
+
-
<!-- include jQuery library -->
+
-
 
+
-
 
+
-
 
+
-
</head>
+
-
 
+
-
</html>
+
-
 
+
-
{{:Team:Utah_State/footer1}}
+

Latest revision as of 21:49, 27 October 2010

USU_IGEM

Content on this page requires a newer version of Adobe Flash Player.

Get Adobe Flash player


Design

Contents

Plasmid Design

In this project, we designed our integration vector as a standardized and adaptable plasmid to allow for integration in a variety of species. The full integration vector (Figure 1) allows for the easy exchange of resistance genes and integration regions with only a restriction digest and ligation of the new regions. A variety of recombination regions can be added to the plasmid to allow for gene integration in any desired area of the genome, and multiple resistance genes allows for more complex experiments where multiple regions are integrated and selected for simultaneously.

The integration plasmid is based off of pSB1A3, which allows it to replicate in high copy number in E. coli during the construction of the BioBrick part. This provides large amounts of DNA for analysis and future transformations into cyanobacteria.


USU Plamid 1C.png

Figure 1. Integration Plasmid pSB1A3_IntC. Plasmid contains two exchangeable recombination regions RS1 and RS2, each flanked by restriction sites for easy modification. Plasmid also contains the Chloramphenicol resistance gene (CmR), which is also easily exchanged through restriction digest.

Overview of Integration

In Synechocystis sp. PCC 6803, the cells naturally take up DNA from the media and recombine it with the genome in regions of homology. If two regions of homology are closely spaced on the chromosome and the foreign DNA, the regions between the two homologous regions are exchanged (Figure 2). After recombination with the recombination plasmid in this project, the exchanged fragment of genomic DNA is lost from the cell due to the plasmid’s inability to replicate in PCC 6803.

USU Integration 1.png USU Integration 2.png

Figure 2. (A) Once the integration plasmid comes across the homologous part of the genome, crossing over occurs between the plasmid and the chromosome. (B) Since there are two recombination regions, the crossing over resolves with the regions between the homologous regions switching locations, leaving the BioBrick and resistance gene in the genome. The plasmid is then lost from the cells as it is unable to replicate in PCC 6803.

Advantages and Applications of Integration

The use of an integration plasmid for synthetic biological engineering possesses many advantages, and a few disadvantages, compared to using plasmid vectors.

  • With integration, the copy number of the inserted BioBrick is more precisely known than with plasmids, allowing for more predicable levels of protein expression. Inserted into the main genome, only one or two copies of the gene will exist in the cell at any given time. If higher copy number is desired, and the species possesses other chromosomes of different copy number, the integration can be targeted to these other chromosomes. The copy number of chromosomes is generally more stable, varying only by one or two copies from cell to cell, whereas a plasmid vary between cells by as much as several hundred copies.
  • Integration also affords more stable replication and retention of the BioBrick, as entire chromosomes are rarely lost from a cell, but plasmids with low replication rates may be lost to some daughter cells during division. This is especially true for species such as Synechocystis, which do not retain plasmids very efficiently.
  • Traditional cloning with plasmids is also limited in scale. Plasmid vectors start becoming unstable in cells at around 20,000 bp in length, and may be retained only in a small proportion of cells. By inserting the BioBricks into the chromosome from integration vector, a series of 20,000 bp inserts can be added to the cell, giving a potentially limitless capacity for modification.
  • Using integration, more dramatic changes can be made to cells than with traditional plasmid cloning. If the recombination regions flank a gene you wish to remove from the cells, the act of inserting the BioBrick (or merely the antibiotic selection marker) will cause the gene to be deleted. This can enable new genes to be inserted to replace those in the host species, for example exchanging a gene requiring that a cofactor be added to the media with a gene homolog that doesn’t need the cofactor could enable a bio-product to be produced much less expensively.
  • With proper homologous regions, genes could also be inserted into the middle of operons, allowing gene expression to occur in a predictable fashion, with little effort expended in choosing proper promoter conditions.

Promoter and RBS Design

Genome Analyzer Program

Team member Cody Tramp constructed a computer program to analyze a GenBank genome file and provide information about promoter and RBS design (see Figure 3 for a screenshot). The program (which is currently undergoing compatibility revisions before releasing it for general use) creates a searchable database of individual genes that can be filtered for similarity to promoter consensus sequences or can be used to determine common structural features of the genome. In this project, the program was used to identify the codon usage profile for Synechocystis and to determine the consensus ribosome binding site.

USU Program.png

Figure 3. Screenshot of Cody’s Genome Analyzer program. The left window shows the database of all genes in the genome, and the right window is a pop-up window containing links to major databases with information on the gene. The pop-up window can also be programmed to highlight matches to consensus promoter sequences or ribosome binding sites.


Consensus Ribosome Binding Site

The ribosome bindings site used in device construction are vital to the final performance of the part. RBS sequences, however, are dependent on the sequence of the 3’ end of the 16S rRNA ribosomal subunit, which can vary from species to species. Using the Genome Analyzer program, we were able to determine the consensus RBS of Synechocystis sp. PCC 6803 by analyzing the sequence upstream of every gene in the genome. The sequence complimentary to the 3’ end of the 16S rRNA sequence for Syncechocystis (and thus the RBS as seen on the mRNA) is AAAGGAGGT. The Genome Analyzer program found each of these bases to be conserved in different percentages of genes, and that some sequences surrounding the RBS to be highly conserved as well (Figure 4). Thus, the full consensus RBS for Synechocystis is TTTAAAGGAGGTTAAA, followed by the start codon.


USU RBS Program.png

Figure 4. Ribosome binding site consensus sequence as determined by Genome Analyzer program analyzing the upstream region of every gene in the genome. Note positions are number relative to the first base pair match with the 16S rRNA sequence, and not with the start codon. Colors on the lower sequence indicate level of conservation, with red indicating high conservation, yellow moderate, and green low.


Codon Usage Profile

In addition to determining the consensus RBS for optimal gene expression, the codon usage of the gene’s themselves must be matched with the new host genome’s tRNA usage in order to be efficiently produced. The codons for each amino acid that are favored by tRNA’s can be roughly deduced from the frequencies with which each codon is used across all the genes in the genome. Figure 5 shows the summary of the codon usage profile for Synechocystis sp. PCC 6038 as generated by the Genome Analyzer program.


USU Codon Usage Program.png

Figure 5. Codon usage profile for Synechocystis sp. PCC 6038 as generated by the Genome Analyzer program. Blue bars indicate relative usage levels within that amino acid, scaled relative to the most used codon for each amino acid. All values are in percent.