Team:BostonU/Clotho

From 2013.igem.org

Revision as of 20:03, 18 July 2013 by Pshah23 (Talk | contribs)



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



Bull Trowell



Sequence Viewer



SpreadIt Features






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.