Team:SUSTC-Shenzhen-B/standard.html

From 2013.igem.org

(Difference between revisions)
Line 67: Line 67:
           <div class="menu">
           <div class="menu">
             <a href="https://2013.igem.org/Main_Page" class="item">iGEM homepage</a>
             <a href="https://2013.igem.org/Main_Page" class="item">iGEM homepage</a>
-
             <a href="/wiki/index.php?title=Team:SUSTC-Shenzhen-B/clotho.html&amp;action=edit" class="item">Edit</a>
+
             <a href="/wiki/index.php?title=Team:SUSTC-Shenzhen-B/standard.html&amp;action=edit" class="item">Edit</a>
           </div>
           </div>
         </div>
         </div>
-
         <a href="Team:SUSTC-Shenzhen-B/project.html" class="item">Overview</a>
+
         <a href="project.html" class="item">Overview</a>
-
         <a href="Team:SUSTC-Shenzhen-B/standard.html" class="item">Standard and database</a>
+
         <a href="standard.html" class="item active">Standard and database</a>
         <div href="/Team:SUSTC-Shenzhen-B/Project" class="ui dropdown link item">
         <div href="/Team:SUSTC-Shenzhen-B/Project" class="ui dropdown link item">
           Software
           Software
           <span class="white caret"></span>
           <span class="white caret"></span>
           <div class="menu">
           <div class="menu">
-
             <a href="Team:SUSTC-Shenzhen-B/circuitplus.html" class="item">Circuit+</a>
+
             <a href="circuitplus.html" class="item">Circuit+</a>
-
             <a href="Team:SUSTC-Shenzhen-B/feature.html" class="item">Feature</a>
+
             <a href="feature.html" class="item">Feature</a>
-
             <a href="Team:SUSTC-Shenzhen-B/tutorial.html" class="item">Tutorial</a>
+
             <a href="tutorial.html" class="item">Tutorial</a>
-
             <a href="Team:SUSTC-Shenzhen-B/safety.html" class="item">Safety</a>
+
             <a href="safety.html" class="item">Safety</a>
-
             <a href="Team:SUSTC-Shenzhen-B/APIs.html" class="item">APIs</a>
+
             <a href="APIs.html" class="item">APIs</a>
-
             <a href="Team:SUSTC-Shenzhen-B/feedback.html" class="item">Feedback</a>
+
             <a href="feedback.html" class="item">Feedback</a>
-
             <a href="Team:SUSTC-Shenzhen-B/future.html" class="item">Future</a>
+
             <a href="future.html" class="item">Future</a>
           </div>
           </div>
         </div>
         </div>
-
         <a href="Team:SUSTC-Shenzhen-B/clotho.html" class="item">Clotho</a>
+
         <a href="clotho.html" class="item">Clotho</a>
-
         <a href="Team:SUSTC-Shenzhen-B/lab.html" class="item">Lab management</a>
+
         <a href="lab.html" class="item">Lab management</a>
         <div href="/Team:SUSTC-Shenzhen-B/Project" class="ui dropdown link item">
         <div href="/Team:SUSTC-Shenzhen-B/Project" class="ui dropdown link item">
           Human practice
           Human practice
           <span class="white caret"></span>
           <span class="white caret"></span>
           <div class="menu">
           <div class="menu">
-
             <a href="Team:SUSTC-Shenzhen-B/workshop.html" class="item">Workshop meeting</a>
+
             <a href="workshop.html" class="item">Workshop meeting</a>
-
             <a href="Team:SUSTC-Shenzhen-B/publicity.html" class="item">Publicity</a>
+
             <a href="publicity.html" class="item">Publicity</a>
           </div>
           </div>
         </div>
         </div>
Line 99: Line 99:
           <span class="white caret"></span>
           <span class="white caret"></span>
           <div class="menu">
           <div class="menu">
-
             <a href="Team:SUSTC-Shenzhen-B/about.html" class="item">About us</a>
+
             <a href="about.html" class="item">About us</a>
-
             <a href="Team:SUSTC-Shenzhen-B/achievement.html" class="item">Achievement</a>
+
             <a href="achievement.html" class="item">Achievement</a>
-
             <a href="Team:SUSTC-Shenzhen-B/notebook.html" class="item">Notebook</a>
+
             <a href="notebook.html" class="item">Notebook</a>
-
             <a href="Team:SUSTC-Shenzhen-B/acknowledgement.html" class="item">Acknoledgement</a>
+
             <a href="acknowledgement.html" class="item">Acknoledgement</a>
           </div>
           </div>
         </div>
         </div>
         <a href="/Team:SUSTC-Shenzhen-B/Desktop" class="desktop item">Only Desktop visible</a>
         <a href="/Team:SUSTC-Shenzhen-B/Desktop" class="desktop item">Only Desktop visible</a>
 +
      </div>
 +
    </div>
 +
    <div class="header">
 +
      <div class="segment">
 +
        <div id="overview" class="container">
 +
          <div class="introduction">
 +
            <h1 class="ui dividing header">Standard and databse</h1>
 +
            <p class="lead">This page will tell you about technical standard and databse</p>
 +
          </div>
 +
        </div>
       </div>
       </div>
     </div>
     </div>
     <div class="main container page">
     <div class="main container page">
-
       <p>Welcome to our wiki!</p>
+
       <div class="peek">
-
       <p>This year, we have developed Circuit+. Circuit+ as an onlin registry of standard gene circuits. More details can be seen in wiki's "software" part.</p>
+
        <div class="ui vertical pointing secondary menu">
-
      <p>Click to enter Circuit+</p>
+
          <div class="active link item">Technical standard
-
      <p>We also have developed Circuit List and TTEC on Clotho and synthetic biology lab manager. See "Clotho" and "lab" for detail.</p>
+
            <div class="menu">
 +
              <a class="item">Introduction</a>
 +
              <a class="item">RFC 101</a>
 +
              <a class="item">RFC 102</a>
 +
              <a class="item">Synthetic biology laboratory management</a>
 +
              <a class="item">Human practice</a>
 +
            </div>
 +
          </div>
 +
          <div class="link item">Database
 +
            <div class="menu">
 +
              <a class="item">Introduction</a>
 +
              <a class="item">Structure</a>
 +
            </div>
 +
          </div>
 +
        </div>
 +
       </div>
 +
      <div class="page-container">
 +
        <h2 class="ui dividing header">Technical standard</h2>
 +
        <section id="standard"></section>
 +
        <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 gene circuit, especially for those that contain some logical regulatory modules like gene AND gate. As a result, a circuit is well defined and the relations of individual part in circuit can be definitely clear.</p>
 +
        <h3>RFC 101</h3>
 +
        <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 gene circuits that are corresponding to the concept in electronics.</p>
 +
        <h3>RFC 102</h3>
 +
        <p>The second technique, RFC 102: Logic Gene Circuit Standard (version 2.0), gives a more detailed and normative definition of a genetic circuit. A logic gene 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 101 for more information. This standard is an update of RFC 97: Logic Gene Circuit (version 1.0), which was published by us at the end of September.</p>
 +
 
 +
        <h2 class="ui dividing header">Database</h2>
 +
        <section id="actions"></section>
 +
        <h3>Introduction</h3>
 +
        <p>To record the standard circuits, we set up a database. The information and format follow strictly the RFC 102. 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>
 +
        <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 four parts:</p>
 +
        <h4>Basic information</h4>
 +
        <p>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.</p>
 +
        <h4>Circuit Structure</h4>
 +
        <p>Based on the Technique standard, we build up a plug-in named Logical Genetic Diagram. The LGD can dynamically illustrate the structure of a gene 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 gene 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.</p>
 +
 
 +
      </div>
     </div>
     </div>

Revision as of 05:19, 28 October 2013

SUSTC-ShenZhen-B

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 gene circuit, especially for those that contain some logical regulatory modules like gene AND gate. As a result, a circuit is well defined and the relations of individual part in circuit can be definitely clear.

RFC 101

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 gene circuits that are corresponding to the concept in electronics.

RFC 102

The second technique, RFC 102: Logic Gene Circuit Standard (version 2.0), gives a more detailed and normative definition of a genetic circuit. A logic gene 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 101 for more information. This standard is an update of RFC 97: Logic Gene Circuit (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 102. 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 four parts:

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.

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 gene 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 gene 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.