"
Team:BostonU/Clotho
From 2012.igem.org
| (2 intermediate revisions not shown) | |||
| Line 255: | Line 255: | ||
<ul> | <ul> | ||
<h7> | <h7> | ||
| - | <ul><a href="www.eugenecad.org">Eugene</a | + | <ul><a href="www.eugenecad.org">Eugene</a> 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.<br><br> |
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. <h7> | 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. <h7> | ||
<br> | <br> | ||
| Line 279: | Line 279: | ||
<h7> | <h7> | ||
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. <h7> | 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. <h7> | ||
| + | |||
| + | <br><br><br><br><br><br> | ||
Latest revision as of 03:36, 4 October 2012
Clotho and Eugene
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!
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.
