Team:SYSU-Software/Design

From 2014.igem.org

(Difference between revisions)
(Created page with "<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn...")
 
(19 intermediate revisions not shown)
Line 14: Line 14:
}
}
.myContainer {
.myContainer {
-
   min-height: 3000px;
+
   min-height: 6600px;
}
}
.bigFather {
.bigFather {
-
   height: 2700px;
+
   height: 6300px;
}
}
#address1{
#address1{
Line 24: Line 24:
.mC1,.mC2,.mC3,.mC4{
.mC1,.mC2,.mC3,.mC4{
font-size: 14px;
font-size: 14px;
 +
}
 +
h2{
 +
font-size: 30px;
 +
font-weight: bold;
 +
}
 +
h4, h5 {
 +
  float:left;
 +
  width:100%;
 +
}
 +
 +
img.software {
 +
max-width:800px;
}
}
</style>
</style>
Line 34: Line 46:
</a>
</a>
   <div class="navigation1" id="nav">
   <div class="navigation1" id="nav">
-
<div onclick="location.href='https://2014.igem.org/Team:SYSU-Software';" class="home"></div>
+
<div onclick="location.href='https://2014.igem.org/Team:SYSU-Software#4';" class="home"></div>
     <div class="item project">
     <div class="item project">
  <img src="https://static.igem.org/mediawiki/2014/4/41/SYSU-Software_Mbigger.png" alt="Project" class="circle"/>
  <img src="https://static.igem.org/mediawiki/2014/4/41/SYSU-Software_Mbigger.png" alt="Project" class="circle"/>
       <a href="#" class="icon"></a>
       <a href="#" class="icon"></a>
-
       <ul style="top: 25px;">
+
       <ul style="top: 8px;">
         <li><a href="https://2014.igem.org/Team:SYSU-Software/Overview">Overview</a></li>
         <li><a href="https://2014.igem.org/Team:SYSU-Software/Overview">Overview</a></li>
         <li><a href="https://2014.igem.org/Team:SYSU-Software/Design">Design</a></li>
         <li><a href="https://2014.igem.org/Team:SYSU-Software/Design">Design</a></li>
         <li><a href="https://2014.igem.org/Team:SYSU-Software/Validation">Validation</a></li>
         <li><a href="https://2014.igem.org/Team:SYSU-Software/Validation">Validation</a></li>
 +
<li><a href="https://2014.igem.org/Team:SYSU-Software/Demo">Demo</a></li>
<li><a href="https://2014.igem.org/Team:SYSU-Software/Download">Download</a></li>
<li><a href="https://2014.igem.org/Team:SYSU-Software/Download">Download</a></li>
       </ul>
       </ul>
Line 50: Line 63:
           <img src="https://static.igem.org/mediawiki/2014/4/41/SYSU-Software_Mbigger.png" alt="Documents" class="circle"/>  
           <img src="https://static.igem.org/mediawiki/2014/4/41/SYSU-Software_Mbigger.png" alt="Documents" class="circle"/>  
  <a href="#" class="icon"></a>
  <a href="#" class="icon"></a>
-
       <ul style="top: 35px;">
+
       <ul style="top: 25px;">
    <li><a href="https://2014.igem.org/Team:SYSU-Software/Tutorial">Tutorial</a></li>
    <li><a href="https://2014.igem.org/Team:SYSU-Software/Tutorial">Tutorial</a></li>
         <li><a href="https://2014.igem.org/Team:SYSU-Software/Model">Models</a></li>
         <li><a href="https://2014.igem.org/Team:SYSU-Software/Model">Models</a></li>
         <li><a href="https://2014.igem.org/Team:SYSU-Software/Notebook">Notebook</a></li>
         <li><a href="https://2014.igem.org/Team:SYSU-Software/Notebook">Notebook</a></li>
 +
<li><a href="https://2014.igem.org/Team:SYSU-Software/Documentation">Documentation</a></li>
       </ul>
       </ul>
     </div>
     </div>
Line 82: Line 96:
         <li><a href="https://2014.igem.org/Team:SYSU-Software/Member">Members</a></li>
         <li><a href="https://2014.igem.org/Team:SYSU-Software/Member">Members</a></li>
<li><a href="https://2014.igem.org/Team:SYSU-Software/Attribution">Attribution</a></li>
<li><a href="https://2014.igem.org/Team:SYSU-Software/Attribution">Attribution</a></li>
 +
  <li><a href="https://2014.igem.org/Team:SYSU-Software/Ackmt">Acknowledgement</a></li>
         <li><a href="https://2014.igem.org/Team:SYSU-Software/Sponsor">Sponsors</a></li>
         <li><a href="https://2014.igem.org/Team:SYSU-Software/Sponsor">Sponsors</a></li>
-
        <li><a href="https://2014.igem.org/Team:SYSU-Software/Ackmt">Ackmt</a></li>
+
   
       </ul>
       </ul>
     </div>
     </div>
Line 100: Line 115:
<div id="bgContent">
<div id="bgContent">
  <div id="myArticle" name="myArticle">
  <div id="myArticle" name="myArticle">
 +
    <div style="height: 20px;"></div>
<h1 style="text-align: center; font-size: 40px; font-weight: bold; font-family: verdana;">Design</h1><br/>
<h1 style="text-align: center; font-size: 40px; font-weight: bold; font-family: verdana;">Design</h1><br/>
-
<div style="height: 40px;"></div>
+
<div style="height: 20px;"></div>
<h2 id="myPage1" name="myPage1" style="text-align: center;">Overall Mechanism</h2><br/>
<h2 id="myPage1" name="myPage1" style="text-align: center;">Overall Mechanism</h2><br/>
-
<p>We were so accustomed to designing synthetic circuits in a traditional way (i.e. to build a circuit by concatenating different biobricks together) that we even believe this is all about synthetic biology.</p>
+
<p>We are so accustomed to designing synthetic circuits in a traditional way (i.e., to build a circuit by concatenating different biobricks together) that we even believe this is all about synthetic biology. However, with the advent of the second wave of synthetic biology<sup>[1]</sup>, larger circuits, systems and even circuit networks are being designed. Traditional methods are increasingly incompatible with trends in synthetic biology.</p>
-
<br/>
+
<p>So FLAME might change the way we view softwares for synthetic biology. Instead of choosing each biobrick we need in order to construct a circuit, FLAME utilizes frameworks as design prototype. Users choose the inputs (e.g., IPTG, aTc, etc.), outputs (e.g., GFP) and the topologies of circuits, and FLAME can automatically finish the construction. Then users are able to tune the details of the circuits (for example, change a RBS for higher expression efficiency).</p>
-
<p>However, with the advent of the second wave of synthetic biology[1], larger circuits, systems and even circuit networks are being designed. Traditional methods are increasingly more incompatible with trends in synthetic biology.</p>
+
<p>How can FLAME achieve all these? It adopts the following three mechanisms.</p>
-
<br/>
+
<p><b>1. Input-Receptor-Promoter Relationships</b></p>
-
<p>So FLAME might change the way we view softwares for synthetic biology. Instead of choosing each biobrick we need to construct a circuits, FLAME utilizes frameworks as design prototype. Users choose the inputs (e.g., IPTG, aTc, etc.), outputs (e.g., GFP) and the topologies of circuits, and FLAME can automatically construct a circuit. Then users are able to tune the details of the circuits (for example, change a RBS for higher expression efficiency).</p>
+
<p>At the beginning, users should choose the inputs, outputs and the topology for his/her circuits. Thus far, synthetic biologists have constructed most circuits from a limited number of commonly used parts (e.g., LacI, TetR and lambda repressor protein)<sup>[2]</sup>, which makes possible the automatic design of genetic circuits. Through the choice of inputs, FLAME can determine what parts (for example, promoters) should be used.</p>
-
<br/>
+
<p>For instance, when users choose IPTG as the input of the circuits, FLAME will then select LacI as the receptor protein of IPTG. In the absence of IPTG, LacI will repress the expression from lac promoter (P<sub>lac</sub>), and the binding of IPTG with LacI abolishes the repression imposed by LacI. Then an “IPTG-LacI-P<sub>lac</sub>” relationship is determined for further use.</p>
-
<p>How can FLAME achieve all these? FLAME adopts the following three mechanisms.</p><br/>
+
<img src="https://static.igem.org/mediawiki/2014/0/06/SYSU-Software_ds1.png">
-
+
<p><b>Figure 1</b> LacI represses the expression from P<sub>lac</sub>, and binding of IPTG with LacI abolishes this repression.</p>
-
<h4>1. Input-Receptor-Promoter Relationships</h4><br/>
+
<p><b>2. Framework-Based Design</b></p>
-
<p>At the beginning, users should choose the inputs, outputs and the topology for his/her circuits. Thus far, synthetic biologists have constructed most circuits from a limited number of commonly used parts (e.g., LacI, TetR and lambda repressor protein)[2], which makes possible the automatic design of genetic circuits. Through the choice of inputs, FLAME can determine what parts should be used.</p><br/>
+
<p>Next, frameworks help the automatic design. What are the functions of frameworks?</p>
-
<p>For instance, when users choose IPTG as the input of the circuits, FLAME will then select LacI as the receptor protein of IPTG. In the absence of IPTG, LacI will repress the expression from lac promoter (Plac), and the binding of IPTG with LacI abolishes the repression imposed by LacI.</p><br/>
+
<p>Supposing that a synthetic circuit was reported in literature (like toggle switch, see <b>Figure 2</b>), and we want to improve its performance or design a better one with desired performance, the easiest way may be that we would refer to this reported circuits and try to change its components or its topologies.</p>
-
+
<p>So, the reported circuits are there to provide the necessary information about how to arrange the parts in place to construct a functional circuit. For example, there must be at least one promoter, one RBS, one protein coding sequence and one terminator in a circuit, and the order of all these parts is: promoter-RBS-protein coding sequence-terminator. The primary function of frameworks is to make sure that the constructed circuit contains the necessary parts in a correct, functional order.</p>
-
<h4>2. Framework-Based Design</h4><br/>
+
<p>But that is not enough. Frameworks can help users with automatic design of circuits, system and ever larger networks. With the help of frameworks, users can think of design as putting circuits in place to construct a system or network, rather than a bottom-up method starting from every biobrick.</p>
-
<p>Next, frameworks helps the automatic design. What is the function of frameworks?</p><br/>
+
<img src="https://static.igem.org/mediawiki/2014/7/7b/SYSU-Software_ds2.png">
-
<p>Supposing that a synthetic circuit was reported in literature, and we want to improve its performance or even design a better one, the easiest way may be that we would refer to this reported circuits and try to change its components or even its topologies.</p><br/>
+
<p><b>Figure 2</b> Frameworks can help users with easy designs. For instance, Gardner et al.<sup>[3]</sup> reported a toggle switch design in 2000. This design can be used as a “frame”, or a guide to users for designing toggle switches using different biological parts (Adapted from Gardner et al., 2000).</p>
-
<p>So, the reported circuits are there to provide the necessary information about how to arrange the parts in place to construct a functional circuit. For example, there must be at least one promoter, one RBS, one protein coding sequence and one terminator in a circuit, and the order of all these parts is: promoter-RBS-protein coding sequence-terminator. The primary function of frameworks is to make sure that the constructed circuit contains the necessary parts in a correct, functional order. </p><br/>
+
<p><b>3. Biobricks Still Matter</b></p>
-
<p>But this is not enough. Frameworks can also help users with automatic design of circuits, system and ever larger networks. With the help of frameworks, users can think of design as putting circuits in place to construct a system or network, rather than a bottom-up method starting from every biobrick.</p><br/>
+
<p>It is of note that FLAME is still based on biobricks. Biobricks are “bricks” for construction of large “buildings”--circuits, systems or even networks in synthetic biology. As mentioned above, we must place the necessary parts in a “promoter-RBS-protein coding sequence-terminator” order to construct a functional circuit. The utilization of characterized and standardized biobricks guarantees this framework-based automatic method adopted by FLAME.</p>
-
+
<h2 id="myPage2" name="myPage2" style="text-align: center;">WORK FLOW</h2>
-
<h4>3. Biobricks Still Matter</h4><br/>
+
<p>After introduction to the mechanisms of FLAME, we will briefly introduce the work flow of our software. There are four modules: Design, Display, Simulation and Experiment.</p>
-
<p>It is of note that FLAME is still based on biobricks. Biobricks are “bricks” for construction of large “buildings”--circuits, systems or even networks. As mentioned above, we must place the necessary parts in a “promoter-RBS-protein coding sequence-terminator” order to construct a functional circuit. The utilization of characterized and standardized biobricks guarantee this framework-based automatic method adopted by FLAME.</p><br/>
+
<p><b>1. DESIGN</b></p>
-
<div style="height: 40px;"></div>
+
<img class="software" src="https://static.igem.org/mediawiki/2014/a/a0/SYSU-Software_ds3.png">
-
+
<p>This is the first module of FLAME, and also the beginning of circuit designs. This module is aimed at getting FLAME ready for automatic design. FLAME offers users with two methods of starting a circuit design.</p>
-
<h2 id="myPage2" name="myPage2" style="text-align: center;">Work Flow</h2><br/>
+
<p>1) Users choose the input, output and then set the logic between them (that is, the topologies of the circuits). After that, FLAME goes on with the obtained information.</p>
-
 
+
<p>2) Users can also design a circuit with the help of a truth table if they are not clear what design frameworks they should choose. At first, users are required to select inputs and outputs. Then they can fill in the truth table. Users are not required to finish the entire table, which means they just need to complete a few lines. Then FLAME will recommend the topologies of circuits that are in accordance with the truth table.</p>
-
<p>After introduction to the mechanisms of FLAME, we will briefly introduce the work flow of our software, FLAME. There are four modules: Design, Display, Simulation and Experiment.</p><br/>
+
<p><b>2. DISPLAY</b></p>
-
<h4>1. DESIGN</h4><br/>
+
<p>Users can examine and tune their designed circuits at a variety of levels in the Display module. According to synthetic biologists and iGEMers’ usual practice, there are four sub-modules in Display module: Device, Parts, DNA and Vector. They are in the order of their scales.</p>
-
<p>This is the first module of FLAME, and also the beginning of circuit designs. This page is aimed at getting FLAME ready for automatic design. FLAME offers users with two methods of circuit design.</p><br/>
+
<p><b>Device</b></p>
-
<p>1) Users choose the input, output and then set the logic between them, that is the topologies of the circuits. After that, FLAME go on working with the obtained information.</p><br/>
+
<img class="software" src="https://static.igem.org/mediawiki/2014/7/70/SYSU-Software_ds4.png">
-
<p>2) Users can also design a circuit with the help of the truth table, if they are not clear what design frames they should choose. At first, users are required to select inputs and outputs. Then they can fill in the truth table we provide. Users are not required to finish the entire table, which means they just need to complete a few lines. According to the truth table, FLAME will recommend the topologies of circuits that are compatible with it.</p><br/>
+
<p>Detailed information (e.g., which Biobricks have been automatically selected for this circuit) will be displayed in this page. You can change the performance of the circuit via switching a promoter, altering an RBS, etc. In this way, you can make subtle adjustments so that our recommendation will fit your desires.</p>
-
+
<p><b>Parts</b></p>
-
<h4>2. DISPLAY</h4><br/>
+
<img class="software" src="https://static.igem.org/mediawiki/2014/2/25/SYSU-Software_ds5.png">
-
<p>According to synthetic biologists and iGEMers’ usual practice, there are four sub-modules in Display module: Device, Parts, DNA and Vector. They are in the order of their scales.</p><br/>
+
<p>This sub-module provides users with another dimension of the circuits, that is, a view of Biobricks. If you want to know the specific length of any Biobrick or of the material connecting them, just visit this page. In this page you can also make small changes to your circuit like that in Device page.</p>
-
<p style="font-weight:bold;">Device</p><br/>
+
<p><b>Vector</b></p>
-
<p>Detailed information (e.g., which Biobricks have been automatically selected for this circuit) will be displayed in this page. You can fine tune the performance of the circuit via switching a promoter, altering an RBS, etc. In this way, you can make subtle adjustments so that our recommendation fits your ideal circuit.</p><br/>
+
<img class="software" src="https://static.igem.org/mediawiki/2014/7/78/SYSU-Software_ds6.png">
-
<p style="font-weight:bold;">Parts</p><br/>
+
<p>Plasmid is the vector of parts. In this page you can get an overall view of the vector. Furthermore, Vector sub-module will also show you the restriction sites on plasmids.</p>
-
<p>This sub-module provides users with another dimension of the circuits, that is, a view of Biobricks. If you want to know the specific length of any Biobrick or of the material connecting them, just visit this page. In this page you can also make small changes to your circuit like that in Device page.</p><br/>
+
<p><b>DNA</b></p>
-
<p style="font-weight:bold;">DNA</p><br/>
+
<img class="software" src="https://static.igem.org/mediawiki/2014/4/47/SYSU-Software_ds7.png">
-
<p>Small changes in DNA sequence can be made in this DNA page. In additon to the DNA sequence of every parts, you can also know about the position of restriction sites in the sequence. In short, the DNA sub-module offers you with information on the DNA level.</p><br/>
+
<p>Small changes in DNA sequence can be made in this DNA page. In addition to the DNA sequence of every parts, you can also know about the position of restriction sites in the sequence. In short, the DNA sub-module offers you with information on the DNA level.</p>
-
<p style="font-weight:bold;">Vector</p><br/>
+
<p><b>3. SIMULATION</b></p>
-
<p>Plasmid is the vector of parts. In this page you can get an overall view of the vector. Furthermore, Vector sub-module will also show you the restriction sites on plasmid.</p><br/>
+
<img class="software" src="https://static.igem.org/mediawiki/2014/9/90/SYSU-Software_ds8.png">
-
+
<p>After a long work of design, users may want to know how it works in reality. In the Simulation module, FLAME will not only provide you two types of curve graphs, Static Performance and Dynamic Performance, to inform you with the possible performance of the circuit, but also help you find the perfect RBS that best function in the circuit.</p>
-
<h4>3. SIMULATION</h4><br/>
+
<p><b>4. EXPERIMENT</b></p>
-
<p>After a long work of design, users may want to know how it works in reality. In the Simulation module, FLAME will not only provide you two types of curve graphs, Static Performance and Dynamic Performance, to inform you with the possilbe performance of the circuit, but also help you find the perfect RBS that best function in the circuit.</p><br/>
+
<img class="software" src="https://static.igem.org/mediawiki/2014/2/24/SYSU-Software_ds9.png">
-
<h4>4. EXPERIMENT</h4><br/>
+
<p>For researchers aiming to bring their design into reality(e.g., go into a lab and turn their design into a vector), FLAME can offer you a general procedure of your wetlab experiments.</p>
-
<p>For researchers aiming to bring their design into reality(e.g., go into a lab and turn their design into a vector), FLAME can offer you a general procedure of your wetlab experiments. In addition, a final preview of your design will be offered. Furthermore, the “Experiment Record” endows you with the abilities to record, retrieve and improve the experimental protocols.</p><br/>
+
<br>
-
+
<p>[1] Purnick, P.E.M. & Weiss, R. The second wave of synthetic biology: from modules to systems. Nat Rev Mol Cell Bio 10, 410-422 (2009).<p>
 +
<p>[2] Lu, T.K., Khalil, A.S. & Collins, J.J. Next-generation synthetic gene networks. Nat Biotechnol 27, 1139-1150 (2009).</p>
 +
<p>[3] Gardner, T.S., Cantor, C.R. & Collins, J.J. Construction of a genetic toggle switch in Escherichia coli. Nature 403, 339-342 (2000)</p>
  </div>
  </div>

Latest revision as of 23:30, 17 October 2014

Team:SYSU-Software

Design


Overall Mechanism


We are so accustomed to designing synthetic circuits in a traditional way (i.e., to build a circuit by concatenating different biobricks together) that we even believe this is all about synthetic biology. However, with the advent of the second wave of synthetic biology[1], larger circuits, systems and even circuit networks are being designed. Traditional methods are increasingly incompatible with trends in synthetic biology.

So FLAME might change the way we view softwares for synthetic biology. Instead of choosing each biobrick we need in order to construct a circuit, FLAME utilizes frameworks as design prototype. Users choose the inputs (e.g., IPTG, aTc, etc.), outputs (e.g., GFP) and the topologies of circuits, and FLAME can automatically finish the construction. Then users are able to tune the details of the circuits (for example, change a RBS for higher expression efficiency).

How can FLAME achieve all these? It adopts the following three mechanisms.

1. Input-Receptor-Promoter Relationships

At the beginning, users should choose the inputs, outputs and the topology for his/her circuits. Thus far, synthetic biologists have constructed most circuits from a limited number of commonly used parts (e.g., LacI, TetR and lambda repressor protein)[2], which makes possible the automatic design of genetic circuits. Through the choice of inputs, FLAME can determine what parts (for example, promoters) should be used.

For instance, when users choose IPTG as the input of the circuits, FLAME will then select LacI as the receptor protein of IPTG. In the absence of IPTG, LacI will repress the expression from lac promoter (Plac), and the binding of IPTG with LacI abolishes the repression imposed by LacI. Then an “IPTG-LacI-Plac” relationship is determined for further use.

Figure 1 LacI represses the expression from Plac, and binding of IPTG with LacI abolishes this repression.

2. Framework-Based Design

Next, frameworks help the automatic design. What are the functions of frameworks?

Supposing that a synthetic circuit was reported in literature (like toggle switch, see Figure 2), and we want to improve its performance or design a better one with desired performance, the easiest way may be that we would refer to this reported circuits and try to change its components or its topologies.

So, the reported circuits are there to provide the necessary information about how to arrange the parts in place to construct a functional circuit. For example, there must be at least one promoter, one RBS, one protein coding sequence and one terminator in a circuit, and the order of all these parts is: promoter-RBS-protein coding sequence-terminator. The primary function of frameworks is to make sure that the constructed circuit contains the necessary parts in a correct, functional order.

But that is not enough. Frameworks can help users with automatic design of circuits, system and ever larger networks. With the help of frameworks, users can think of design as putting circuits in place to construct a system or network, rather than a bottom-up method starting from every biobrick.

Figure 2 Frameworks can help users with easy designs. For instance, Gardner et al.[3] reported a toggle switch design in 2000. This design can be used as a “frame”, or a guide to users for designing toggle switches using different biological parts (Adapted from Gardner et al., 2000).

3. Biobricks Still Matter

It is of note that FLAME is still based on biobricks. Biobricks are “bricks” for construction of large “buildings”--circuits, systems or even networks in synthetic biology. As mentioned above, we must place the necessary parts in a “promoter-RBS-protein coding sequence-terminator” order to construct a functional circuit. The utilization of characterized and standardized biobricks guarantees this framework-based automatic method adopted by FLAME.

WORK FLOW

After introduction to the mechanisms of FLAME, we will briefly introduce the work flow of our software. There are four modules: Design, Display, Simulation and Experiment.

1. DESIGN

This is the first module of FLAME, and also the beginning of circuit designs. This module is aimed at getting FLAME ready for automatic design. FLAME offers users with two methods of starting a circuit design.

1) Users choose the input, output and then set the logic between them (that is, the topologies of the circuits). After that, FLAME goes on with the obtained information.

2) Users can also design a circuit with the help of a truth table if they are not clear what design frameworks they should choose. At first, users are required to select inputs and outputs. Then they can fill in the truth table. Users are not required to finish the entire table, which means they just need to complete a few lines. Then FLAME will recommend the topologies of circuits that are in accordance with the truth table.

2. DISPLAY

Users can examine and tune their designed circuits at a variety of levels in the Display module. According to synthetic biologists and iGEMers’ usual practice, there are four sub-modules in Display module: Device, Parts, DNA and Vector. They are in the order of their scales.

Device

Detailed information (e.g., which Biobricks have been automatically selected for this circuit) will be displayed in this page. You can change the performance of the circuit via switching a promoter, altering an RBS, etc. In this way, you can make subtle adjustments so that our recommendation will fit your desires.

Parts

This sub-module provides users with another dimension of the circuits, that is, a view of Biobricks. If you want to know the specific length of any Biobrick or of the material connecting them, just visit this page. In this page you can also make small changes to your circuit like that in Device page.

Vector

Plasmid is the vector of parts. In this page you can get an overall view of the vector. Furthermore, Vector sub-module will also show you the restriction sites on plasmids.

DNA

Small changes in DNA sequence can be made in this DNA page. In addition to the DNA sequence of every parts, you can also know about the position of restriction sites in the sequence. In short, the DNA sub-module offers you with information on the DNA level.

3. SIMULATION

After a long work of design, users may want to know how it works in reality. In the Simulation module, FLAME will not only provide you two types of curve graphs, Static Performance and Dynamic Performance, to inform you with the possible performance of the circuit, but also help you find the perfect RBS that best function in the circuit.

4. EXPERIMENT

For researchers aiming to bring their design into reality(e.g., go into a lab and turn their design into a vector), FLAME can offer you a general procedure of your wetlab experiments.


[1] Purnick, P.E.M. & Weiss, R. The second wave of synthetic biology: from modules to systems. Nat Rev Mol Cell Bio 10, 410-422 (2009).

[2] Lu, T.K., Khalil, A.S. & Collins, J.J. Next-generation synthetic gene networks. Nat Biotechnol 27, 1139-1150 (2009).

[3] Gardner, T.S., Cantor, C.R. & Collins, J.J. Construction of a genetic toggle switch in Escherichia coli. Nature 403, 339-342 (2000)

Email: sysusoftware@126.com

Address: 135# Xingang Rd(W.), Sun Yat-sen University, Guangzhou, China