Team:SYSU-Software/design

<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:schemas-microsoft-com:office:office">

<head>

  <meta charset="UTF-8">

<title>Team:SYSU-Software</title>
<link href="https://2014.igem.org/Team:SYSU-Software/header.css?action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css" />
<link href="https://2014.igem.org/Team:SYSU-Software/semantic.min.css?action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css" />
<link href="https://2014.igem.org/Team:SYSU-Software/general.css?action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css" />
<link href="https://2014.igem.org/Team:SYSU-Software/toTop.css?action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css" />
<link href="" rel="stylesheet" type="text/css" />
	<style type="text/css">
		#bgContent{
			background-color: #f5f0d3;
			min-height: 4450px;
		}
		#flameTop{
			background-color: #f5f0d3;
			height: 132px;
		}
		#flameMiddle{
			position: relative;
		}
		#flameBottom{
			background-color: #f5f0d3;
			top: 160px;
		}
		#bgToTop, #bgMenu{
			min-height: 4450px;
			max-height: 16000px;
		}
		p{
		  font-size: 20px;
		  font-family: Arial, Helvetica, Microsoft Sans Serif;
		  text-align: left;
		}
		h2{
		  font-size: 28px;
		  font-family: Arial, Helvetica, Microsoft Sans Serif;
		  font-weight: bold;
		  text-align: left;
		}
		h3{
		  font-size: 23px;
		  font-family: Arial, Helvetica, Microsoft Sans Serif;
		  font-weight: bold;
		  text-align: left;
		}
	</style>
</head>

<body>
		<div id="top2"></div>
	
	<div id="pageName">
		<img style="position: relative; width: 55%;" id="" src="https://static.igem.org/mediawiki/2014/a/a8/SYSU-Software_project_02.png">
	</div>
	
<div class="bigFather">

	<div id="bgMenu">
	
		<div class='card-holder'>
		
			<div onclick="location.href='https://2014.igem.org/Team:SYSU-Software';" class='homeCard' id="bg-00" ></div>
			
			<div class="bigTitle" id="Proj" style="">
				<div style="position:absolute; display: inline-block; left: 14px;">Project</div>
			</div>
			<div class='card' id="bg-01">
				<div style="height:10px;"></div>
				 <div class='card-content'><a href='https://2014.igem.org/Team:SYSU-Software/overview'>Overview</a></div> 
				 <div class='card-content'><a href="https://2014.igem.org/Team:SYSU-Software/design">Design</a></div> 
				 <div class='card-content'><a href="https://2014.igem.org/Team:SYSU-Software/validation">Validation</a></div>
				 <div class='card-content'><a href="https://2014.igem.org/Team:SYSU-Software/download">Download</a></div>
			</div>
		  
		  
			<div class="bigTitle" id="Docu" style="">
				<div style="position:absolute; display: inline-block; left: 14px;">Documents</div>
			</div>
			<div class='card' id="bg-02">
			    <div style="height:20px;"></div>
				<div class='card-content'><a href="https://2014.igem.org/Team:SYSU-Software/tutorial">Tutorial </a></div>
				<div class='card-content'><a href="https://2014.igem.org/Team:SYSU-Software/model"> Models </a></div>
				<div class='card-content'><a href="https://2014.igem.org/Team:SYSU-Software/notebook"> Notebook </a></div>
			</div>
			
			<div class="bigTitle" id="Requ" style="">
				<div style="position:absolute; display: inline-block; left: 14px;">Requirements</div>
			</div>
			<div class='card' id="bg-03">
			    <div style="height:20px;"></div>
				<div class='card-content'><a href="https://2014.igem.org/Team:SYSU-Software/medal"> Medals </a></div>
				<div class='card-content'><a href="https://2014.igem.org/Team:SYSU-Software/safety"> Safety </a></div>
				<div class='card-content'><a href="https://2014.igem.org/Team:SYSU-Software/collaboration"> Collaboration </a></div>
			</div>
	
			<div class="bigTitle" id="Poli" style="">
				<div style="position:absolute; display: inline-block; left: 14px;">Policy & Practice</div>
			</div>
			<div class='card' id="bg-04">
			    <div style="height:28px;"></div>
				<div class='card-content'><a href="https://2014.igem.org/Team:SYSU-Software/meetup"> Meetups </a></div>
				<div class='card-content'><a href='https://2014.igem.org/Team:SYSU-Software/BBO'> BBO </a></div>
			</div>
			
			<div class="bigTitle" id="Team" style="">
				<div style="position:absolute; display: inline-block; left: 14px;">Team</div>
			</div>
			<div class='card' id="bg-05">
			    <div style="height:10px;"></div>
				<div class='card-content'><a href="https://2014.igem.org/Team:SYSU-Software/member"> Members </a></div>
				<div class='card-content'><a href="https://2014.igem.org/Team:SYSU-Software/attribution">Attribution</a></div>
				<div class='card-content'><a href="https://2014.igem.org/Team:SYSU-Software/sponsor"> Sponsors </a></div>
				<div class='card-content'><a href="https://2014.igem.org/Team:SYSU-Software/ackmt"> Ackmt </a></div>
			</div>
			
		</div>
		
	</div>
	
	<div id="bgContent">

		<div id="flameTop">
			<img id="" src="https://static.igem.org/mediawiki/2014/b/b5/SYSU-Software_project.png">
		</div>
			
		<div class="flameMiddle">
			<div style="height: 20px;"></div>
			<h1 style="text-align: center; font-size: 45px; font-weight: bold; font-family: cursive;">Design</h1><br/>
			<div style="height: 40px;"></div>
			<div  style="top: 40px; width: 854px; margin:0px auto;">
					<h2 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>
						<br/>
					<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>
						<br/>
					<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>
						<br/>
					<p>How can FLAME achieve all these? FLAME adopts the following three mechanisms.</p><br/>

					<h3>1. Input-Receptor-Promoter Relationships</h3><br/>
					<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>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/>
					
					<h3>2. Framework-Based Design</h3><br/>
					<p>Next, frameworks helps the automatic design. What is the function of frameworks?</p><br/>
					<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>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>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/>
					
					<h3>3. Biobricks Still Matter</h3><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. 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/>
					
					<div style="height: 40px;"></div>
					
					<h2 style="text-align: center;">WORK FLOW</h2><br/>
					<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/>
					<h3>1. DESIGN</h3><br/>
					<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>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/>
					<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/>
					
					<h3>2. DISPLAY</h3><br/>
					<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 style="font-weight:bold;">Device</p><br/>
					<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/>
					<p style="font-weight:bold;">Parts</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><br/>
					<p style="font-weight:bold;">DNA</p><br/>
					<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 style="font-weight:bold;">Vector</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 plasmid.</p><br/>
					
					<h3>3. SIMULATION</h3><br/>
					<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/>
					<h3>4. EXPERIMENT</h3><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. 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/>
			</div>
		</div>
		
		<div id="flameBottom">
			<img id="" src="https://static.igem.org/mediawiki/2014/5/56/SYSU-Software_footer.png">
		</div>
	</div>
	
    <div id="bgToTop">
		<a id="igemlogo" href="https://2014.igem.org/Main_Page" target="_blank" >
			<img src="https://static.igem.org/mediawiki/2014/7/73/SYSU-Software_igemlogo.png" alt="igemlogo">
		</a>
	</div>
	
</div>
<div style="display: none;" id="rocket-to-top">
		<div style="opacity:0;display: block;" class="level-2"></div>
		<div class="level-3"></div>
	</div>
</body>
<script type="text/javascript" src="https://2013.igem.org/Team:SYSU-Software/jquery-1.9.1.min.js?action=raw&ctype=text/javascript"></script>
<script type="text/javascript" src="https://2014.igem.org/Team:SYSU-Software/jquery.easing.1.3.js?action=raw&ctype=text/javascript"></script>
<script type="text/javascript" src="https://2014.igem.org/Team:SYSU-Software/allMenu.js?action=raw&ctype=text/javascript"></script>
<script type="text/javascript" src="https://2014.igem.org/Team:SYSU-Software/toTop.js?action=raw&ctype=text/javascript"></script>
</html>