Team:SUSTC-Shenzhen-B/standard.html
From 2013.igem.org
Line 139: | Line 139: | ||
<section id="standard"></section> | <section id="standard"></section> | ||
<h3>Introduction</h3> | <h3>Introduction</h3> | ||
- | <p>We establish two RFC (Request for Comments) documents this year. They are the basis of the Circuit+ database. We tried our best to make the definition of a | + | <p>We establish two RFC (Request for Comments) documents this year. They are the basis of the Circuit+ database. We tried our best to make the definition of a genetic circuit, especially for those that contain some logical regulatory modules like genetic AND gate. As a result, a genetic circuit is well defined and the relations of individual part in circuit can be definitely clear.</p> |
<h3>RFC 101: Logic Gene Module Standard</h3> | <h3>RFC 101: Logic Gene Module Standard</h3> | ||
<a href="https://static.igem.org/mediawiki/2013/5/55/BBF_RFC101_Logic_Gene_Module_Standard_.pdf">Browse RFC 101</a> | <a href="https://static.igem.org/mediawiki/2013/5/55/BBF_RFC101_Logic_Gene_Module_Standard_.pdf">Browse RFC 101</a> | ||
- | <p>The first technique standard, RFC 101: Logic Gene Module Standard, gives the definition of a logic gene module. This is a very important part of genetic circuit in Synthetic Biology fields. And the logical relations in genes and electric circuit can be seen as the original idea of synthetic biology. We’ve noticed that many gene circuits that were mentioned in previous iGEM projects lacked of a logic module description. They didn’t pay attention to the concept of a logical device and simply constructed their circuits. We built up the standard for promoting the concept of logic functional modules in | + | <p>The first technique standard, RFC 101: Logic Gene Module Standard, gives the definition of a logic gene module. This is a very important part of genetic circuit in Synthetic Biology fields. And the logical relations in genes and electric circuit can be seen as the original idea of synthetic biology. We’ve noticed that many gene circuits that were mentioned in previous iGEM projects lacked of a logic module description. They didn’t pay attention to the concept of a logical device and simply constructed their circuits. We built up the standard for promoting the concept of logic functional modules in genetic circuits that are corresponding to the concept in electronics.</p> |
<h3>RFC 97: Genetic Circuit Standard (version_2.0)</h3> | <h3>RFC 97: Genetic Circuit Standard (version_2.0)</h3> | ||
<a href="https://static.igem.org/mediawiki/2013/4/45/BBF_RFC_97-Genetic_Circuit_Standard_%28version_2.0%29.pdf">Browse RFC 97</a> | <a href="https://static.igem.org/mediawiki/2013/4/45/BBF_RFC_97-Genetic_Circuit_Standard_%28version_2.0%29.pdf">Browse RFC 97</a> | ||
- | <p>The second | + | <p>The second technical standard, RFC97: Genetic Circuit Standard (version 2.0), gives a more detailed and normative definition of a genetic circuit. A logic genetic circuit has a higher level than a gene device. In order to make this definition, we firstly define coding-frame. A coding-frame is a DNA sequence which has at least one RBS, at least one promoter, at least one protein domain, at least one terminator. A genetic circuit contains one or more than one coding-frames and can consist one or more than one plasmids. It can be regulated in many different pathways. It can accept various input signals followed by giving various output signals. Most importantly. In this RFC, we also give a standard format to record a circuit. Please see RFC 97(version 2.0) for more information. This standard is an update of RFC 97 (old version): Genetic Circuit Standard (version 1.0), which was published by us at the end of September.</p> |
<h2 class="ui dividing header">Database</h2> | <h2 class="ui dividing header">Database</h2> | ||
<section id="actions"></section> | <section id="actions"></section> | ||
<h3>Introduction</h3> | <h3>Introduction</h3> | ||
- | <p> To record the standard circuits, we set up a database. The information and format follow strictly the RFC | + | <p> To record the standard circuits, we set up a database. The information and format follow strictly the RFC 97 (version 2.0). And this database is open and dynamic. You can upload your circuits into the database and download information from it. We also provide APIs that allow developers to use the information of the database for other software.</p> |
<h3>Structure</h3> | <h3>Structure</h3> | ||
<p> So far, we’ve collected a number of valuable information from iGEM wikis and the journals about their respective gene circuits. And we set up a central database which can store all these useful information. Referring to the RFC document, all the information of a circuit can be separated into following parts:</p> | <p> So far, we’ve collected a number of valuable information from iGEM wikis and the journals about their respective gene circuits. And we set up a central database which can store all these useful information. Referring to the RFC document, all the information of a circuit can be separated into following parts:</p> |
Revision as of 01:24, 29 October 2013
Standard and databse
This page will tell you about technical standard and databse
Technical standard
Introduction
We establish two RFC (Request for Comments) documents this year. They are the basis of the Circuit+ database. We tried our best to make the definition of a genetic circuit, especially for those that contain some logical regulatory modules like genetic AND gate. As a result, a genetic circuit is well defined and the relations of individual part in circuit can be definitely clear.
RFC 101: Logic Gene Module Standard
Browse RFC 101The first technique standard, RFC 101: Logic Gene Module Standard, gives the definition of a logic gene module. This is a very important part of genetic circuit in Synthetic Biology fields. And the logical relations in genes and electric circuit can be seen as the original idea of synthetic biology. We’ve noticed that many gene circuits that were mentioned in previous iGEM projects lacked of a logic module description. They didn’t pay attention to the concept of a logical device and simply constructed their circuits. We built up the standard for promoting the concept of logic functional modules in genetic circuits that are corresponding to the concept in electronics.
RFC 97: Genetic Circuit Standard (version_2.0)
Browse RFC 97The second technical standard, RFC97: Genetic Circuit Standard (version 2.0), gives a more detailed and normative definition of a genetic circuit. A logic genetic circuit has a higher level than a gene device. In order to make this definition, we firstly define coding-frame. A coding-frame is a DNA sequence which has at least one RBS, at least one promoter, at least one protein domain, at least one terminator. A genetic circuit contains one or more than one coding-frames and can consist one or more than one plasmids. It can be regulated in many different pathways. It can accept various input signals followed by giving various output signals. Most importantly. In this RFC, we also give a standard format to record a circuit. Please see RFC 97(version 2.0) for more information. This standard is an update of RFC 97 (old version): Genetic Circuit Standard (version 1.0), which was published by us at the end of September.
Database
Introduction
To record the standard circuits, we set up a database. The information and format follow strictly the RFC 97 (version 2.0). And this database is open and dynamic. You can upload your circuits into the database and download information from it. We also provide APIs that allow developers to use the information of the database for other software.
Structure
So far, we’ve collected a number of valuable information from iGEM wikis and the journals about their respective gene circuits. And we set up a central database which can store all these useful information. Referring to the RFC document, all the information of a circuit can be separated into following parts:
I.Classification
Each circuit should declare their first classification and the secondary classification based on functions. A circuit should also be attached with some key words which can search and classify easily. Furthermore, the circuit should also be attached with the tags in Mind Map so that the circuit can be found in it.
II.Basic information
In part I, we store the name, the authors (or the team name), the id, the tags, the classification, the reference (wiki link or ISSN) as well as the description and applications about the gene circuit. Also, it contains the chassis (where the circuit functions), plasmids (the vector, may have more than one plasmid), the input and output of the gene circuit and the result of the circuits. Through this part, you can generally have a concept of what’s the functions of the circuits.
III.Circuit Structure
Based on the Technique standard, we build up a plug-in named Logical Genetic Diagram. The LGD can dynamically illustrate the structure of a genetic circuit. So we need several data to build up the structure. The database record the information of the coding-frame which is the subpart of genetic circuit. The information is composed of the output, input as well as the state (E.g Is this coding-frame constitutively express or it will just activated by some specific substance) and the sequence. The database also stores the biobrick assembly to coding-frame, which gives the assembling order of the biobricks and some detailed information of these biobricks. What’s more, all the regulation information (such as the gene expression, the external stimulation and the combination and degration of the substance) has been recorded in the database so that LGD (Logic Genetic Diagram) can show them.
All the data of a genetic circuit that is mentioned above can be completely stored in the central database. Mind map, Logic Genetic Diagram as well as the registry— ‘Circuit+’ is set up based on it. The central database also store the user’s information. What’s more, the database is dynamic. User can upload new genetic circuit into our database. After the data is approved by an advanced user, the data will be stored into the database.