Team:BostonU/Clotho

From 2013.igem.org

(Difference between revisions)
Line 34: Line 34:
/*only use for current page content header (i.e. Team, G-nomeSurferPro, etc)*/
/*only use for current page content header (i.e. Team, G-nomeSurferPro, etc)*/
-
H6 {
 
-
      font-family: Signika;
 
-
      text-transform: uppercase;
 
-
      text-decoration: none;
 
-
      text-align: left;
 
-
      color: #B22222;
 
-
      font-size: 28pt;
 
-
    }
 
H4 {
H4 {
Line 60: Line 52:
       font-size: 12pt;
       font-size: 12pt;
     }
     }
-
 
H7 {
H7 {
       font-family: Signika;
       font-family: Signika;
Line 69: Line 60:
       font-size: 12pt;
       font-size: 12pt;
     }
     }
 +
H8 {
H8 {
       font-family: Signika;
       font-family: Signika;
Line 75: Line 67:
       text-align: left;
       text-align: left;
       color: #B22222;
       color: #B22222;
-
       font-size: 18pt;
+
       font-size: 12pt;
     }
     }
-
H2 {
+
H6 {
       font-family: Signika;
       font-family: Signika;
       text-transform: none;
       text-transform: none;
Line 84: Line 76:
       text-align: left;
       text-align: left;
       color: #B22222;
       color: #B22222;
-
       font-size: 14pt;
+
       font-size: 13pt;
 +
          font-width: 300;
     }
     }
Line 95: Line 88:
       font-size: 14pt;
       font-size: 14pt;
     }
     }
 +
 +
</style>
</style>
-
<link rel="stylesheet" type="text/css" href="http://static.tumblr.com/bepcnvc/zlPm6ibrh/team.css">
+
<link rel="stylesheet" type="text/css" href="http://static.tumblr.com/bepcnvc/YKnm67emn/team.css">
-
<link href='http://fonts.googleapis.com/css?family=Signika' rel='stylesheet' type='text/css'>
+
<link href='http://fonts.googleapis.com/css?family=Signika:300,400' rel='stylesheet' type='text/css'>
-
<link href='http://fonts.googleapis.com/css?family=Electrolize' rel='stylesheet' type='text/css'>
+
<style type="text/css">@import "http://cs.wellesley.edu/~hcilab/iGEM_wiki/css/videobox.css";</style>
<style type="text/css">@import "http://cs.wellesley.edu/~hcilab/iGEM_wiki/css/videobox.css";</style>
Line 107: Line 101:
<div id="bu-wellesley_wiki_content">
<div id="bu-wellesley_wiki_content">
-
<p  style="text-align:center;"><a href="https://2013.igem.org/Team:BostonU"><img src="https://static.igem.org/mediawiki/2012/2/2d/NotebookBU.png" width="800px"></a></p>
+
<p  style="text-align:center;"><a href="https://2013.igem.org/Team:BostonU"><img src="https://static.igem.org/mediawiki/2013/2/2c/Marsh.png" width="800px" length="200px"></a></p>
<ul id="nav">  
<ul id="nav">  
Line 119: Line 113:
<ul>  
<ul>  
<li><a href="https://2013.igem.org/Team:BostonU/Project_Overview">Project Overview and Abstract</a></li>  
<li><a href="https://2013.igem.org/Team:BostonU/Project_Overview">Project Overview and Abstract</a></li>  
-
                         <li><a href="https://2013.igem.org/Team:BostonU/MoClo2">Introduction to MoClo</a></li>
+
                         <li><a href="https://2013.igem.org/Team:BostonU/MoCloChara">Introduction to MoClo and Characterization</a></li>
-
<li><a href="https://2013.igem.org/Team:BostonU/Characterization">Introduction to Characterization</a></li>
+
 
-
                         <li><a href="https://2013.igem.org/Team:BostonU/DataSheet">Introduction to Data Sheets</a></li>   
+
 +
                        <li><a href="https://2013.igem.org/Team:BostonU/QS">Quorum Sensing</a></li>
 +
                        <li><a href="https://2013.igem.org/Team:BostonU/HK">Histidine Kinase</a></li>
 +
                        <li><a href="https://2013.igem.org/Team:BostonU/ML">MoClo Library</a></li>
 +
                         <li><a href="https://2013.igem.org/Team:BostonU/DataSheet">Data Sheets App</a></li>   
<li><a href="https://2013.igem.org/Team:BostonU/Methodology ">Methodology Overview</a></li>  
<li><a href="https://2013.igem.org/Team:BostonU/Methodology ">Methodology Overview</a></li>  
<li><a href="https://2013.igem.org/Team:BostonU/Results ">Results Summary</a></li>  
<li><a href="https://2013.igem.org/Team:BostonU/Results ">Results Summary</a></li>  
Line 140: Line 138:
<li><a href="https://2013.igem.org/Team:BostonU/Protocols">Protocols</a></li>
<li><a href="https://2013.igem.org/Team:BostonU/Protocols">Protocols</a></li>
<li><a href="https://2013.igem.org/Team:BostonU/Clotho">Clotho and Eugene</a></li>
<li><a href="https://2013.igem.org/Team:BostonU/Clotho">Clotho and Eugene</a></li>
-
<li><a href="https://2013.igem.org/Team:BostonU/Notebook">Weekly Notebook</a></li>
+
<li><a href="https://2013.igem.org/Team:BostonU/NotebookQS">Quorum Sensing Notebook</a></li>
 +
                        <li><a href="https://2013.igem.org/Team:BostonU/NotebookHK">Histidine Kinase Notebook</a></li>
 +
                        <li><a href="https://2013.igem.org/Team:BostonU/NotebookML">MoClo Library Notebook</a></li>
 +
                        <li><a href="https://2013.igem.org/Team:BostonU/TroubleShooting">Trouble Shooting</a></li>
</ul>
</ul>
</li>
</li>
Line 160: Line 161:
                 </ul>
                 </ul>
</li>
</li>
 +
 +
</ul>
 +
</ul>  
</ul>  

Revision as of 14:19, 21 May 2013

BostonU iGEM Team: Welcome


Clotho and Eugene


Clotho Introduction


    Our project is focused on creating a standardized method for the characterization of genetic circuits in synthetic biology. In order to achieve this goal, it is necessary to have a platform that enables us to create the standardized data, organize it and manage it efficiently. Clotho is a great synthetic biology tool that has been helping us with exactly that!

    This section aims to describe how we have been using Clotho in our project. We divided the content into the Clotho Apps we used, giving a brief explanation of how each App works and examples of situations in which they were useful for our project. We hope you can all get good ideas on how to use Clotho on your projects and take advantage of this amazing tool!




SpreadIt Oligos

    SpreadIt Oligos is an app that allows users to browse and input oligos from and into the data base. We used this app to add on additional oligos one at a time aside from spreadsheets of primers that were added by Bull Trowell. SpreadIt Oligos does what Bull Trowell does on a smaller scale.





Bull Trowell

    Bull Trowel is a very useful app for adding large amounts of Parts, Oligos, Vectors, Plasmids and etc from an excel sheet to Clotho`s inventory. In our case, we had a list of almost 200 primers that we designed in an Excel sheet that we wanted to include in our inventory. All of them could be added much faster and with lower mistake rate by using Bull Trowel. Below, there is an example of the interface of the app while we were adding our oligos and the Excel sheet from which we took the oligo sequences.


    Also, the description section helps to give meaning to the nickname and makes the inventory more user-friendly.




Sequence Viewer

    Sequence Viewer is a very useful app to analyze sequences that are in the inventory . It allows us not only to view the sequences of DNA, but also to interact with it by highlighting specific portions that we are interested in. For example, we used sequence viewer to find and highlight restriction and fusion sites within the sequence.





SpreadIt Features

    SpreadIt Features was a very useful tool while we were designing our MoClo primers. When we create primers for moclo, we need to make sure the genes for which we create the primers do not have certain restriction sites within them where our moclo enzymes will cut. We thus use the spreadit feature app to create features such as restriction sites by entering the sequence into the data base so that when viewing the gene sequence in sequence viewer, we can look for these restriction sites. Also, SpreadIt Features enabled us to create MoClo fusion sites as features to be analyzed in our sequences so we can better predict how and where ligation in MoClo reaction is occurring.








Eugene


      Eugene is a language based off of Java which is both human and machine readable. Currently the language can speed up the designs of new parts by providing a list of possible transcriptional units based on specific rules and parts available.

      Still in its beta stages, the BU iGEM team used Eugene to come up with list of possible transcriptional units that could be assembled from the Moclo parts we made. By specifying rules concerning fusion sites and restriction sites, we let Eugene do the designing for us, while we then selectively choose which transcriptional units to create. Below is a sample of Eugene script for which we used today.

      We were fortunate to be able to use Eugene through Clotho's Eugene Scriptor. The first task to do in writing a Eugene script is to define what the parts are. Notice that the language is very straightforward and intuitive.



      In this example above, we are defining our basic parts. Although the fusion/MoClo sites themselves are not basic parts, we consider them as a separate entities because they are essential when combining different MoClo parts. At this point, fusion sites as a separate part would be a more versatile method of using the language.

      After defining which parts Eugene will be combining to together, the next step would be to identify the device. In this case, different basic parts are combined to form a moclo level 0 part.



      After defining our MoClo level 0 devices, the next step is to define level MoClo Level 1 devices. In this case, a level 1 device is designated to include a promotor, rbs, gene and terminator. Additional rules are added as needed. For instance, we are creating rules to make sure the Moclo sites of subsequent parts are the same so they are able to be ligated together. In the picture the rule is expressed for Promoter and RBS. Also, we have to be consistent with the design of the MoClo parts, it means that the part can`t be flanked by the same MoClo sites as show in the second rule.



      Although we did not have the chance to use Eugene extensively, we do hope to use it more hand in hand with our experiments as we continue to create novel Moclo parts.