Team:SYSU-Software/overview

From 2014.igem.org

(Difference between revisions)
 
(5 intermediate revisions not shown)
Line 8: Line 8:
<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/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/semantic.min.css?action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css" />
-
<link href="https://2014.igem.org/Team:SYSU-Software/BBO.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" />
-
<style 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" />
-
#bgMenu, #bgToTop, #bgContent{
+
<link href="" rel="stylesheet" type="text/css" />
-
height: 1360px;
+
<style type="text/css">
-
}
+
#bgContent{
-
 
+
background-color: #f5f0d3;
-
#flameBottom{
+
min-height: 1520px;
-
position: relative;
+
}
-
text-align: center;
+
#flameTop{
-
top: 200px;
+
background-color: #f5f0d3;
-
margin: 0px auto;
+
height: 132px;
-
}
+
}
-
 
+
#flameMiddle{
-
p{
+
position: relative;
-
font-size: 20px;
+
}
-
font-family: Arial, Helvetica, Microsoft Sans Serif;
+
#flameBottom{
-
text-align: left;
+
background-color: #f5f0d3;
-
margin: .6em 0 .6em 0;
+
top: 150px;
-
line-height: 1.5em;
+
}
-
}
+
#bgToTop{
-
</style>
+
min-height: 1520px;
 +
max-height: 16000px;
 +
}
 +
#bgMenu{
 +
min-height: 1520px;
 +
max-height: 16000px;
 +
}
 +
p{
 +
  font-size: 20px;
 +
  font-family: Arial, Helvetica, Microsoft Sans Serif;
 +
  text-align: left;
 +
}
 +
h2{
 +
  font-size: 22px;
 +
  font-family: Arial, Helvetica, Microsoft Sans Serif;
 +
  font-weight: bold;
 +
  text-align: left;
 +
}
 +
</style>
</head>
</head>
<body>
<body>
-
<div id="top2"></div>
+
<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 class="bigFather">
Line 49: Line 71:
<div style="height:10px;"></div>
<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/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/design">Design</a></div>  
-
<div class='card-content'><a href='https://2014.igem.org/Team:SYSU-Software/wetlab'>Wetlab </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 class='card-content'><a href="https://2014.igem.org/Team:SYSU-Software/download">Download</a></div>
</div>
</div>
   
   
Line 60: Line 82:
<div class='card' id="bg-02">
<div class='card' id="bg-02">
    <div style="height:20px;"></div>
    <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/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/model"> Models </a></div>
-
<div class='card-content'><a href='https://2014.igem.org/Team:SYSU-Software/notebook'> Notebook </a></div>
+
<div class='card-content'><a href="https://2014.igem.org/Team:SYSU-Software/notebook"> Notebook </a></div>
</div>
</div>
Line 70: Line 92:
<div class='card' id="bg-03">
<div class='card' id="bg-03">
    <div style="height:20px;"></div>
    <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/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/safety"> Safety </a></div>
-
<div class='card-content'><a href='https://2014.igem.org/Team:SYSU-Software/collaboration'> Collaboration </a></div>
+
<div class='card-content'><a href="https://2014.igem.org/Team:SYSU-Software/collaboration"> Collaboration </a></div>
</div>
</div>
Line 80: Line 102:
<div class='card' id="bg-04">
<div class='card' id="bg-04">
    <div style="height:28px;"></div>
    <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/meetup"> Meetups </a></div>
<div class='card-content'><a href='https://2014.igem.org/Team:SYSU-Software/BBO'> BBO </a></div>
<div class='card-content'><a href='https://2014.igem.org/Team:SYSU-Software/BBO'> BBO </a></div>
</div>
</div>
Line 88: Line 110:
</div>
</div>
<div class='card' id="bg-05">
<div class='card' id="bg-05">
-
    <div style="height:20px;"></div>
+
    <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/member"> Members </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/attribution">Attribution</a></div>
-
<div class='card-content'><a href='https://2014.igem.org/Team:SYSU-Software/ackmt'> Ackmt </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>
Line 99: Line 122:
<div id="bgContent">
<div id="bgContent">
 +
<div id="flameTop">
<div id="flameTop">
-
<img id="" src="https://static.igem.org/mediawiki/2014/f/fb/SYSU-Software_FLAME.png">
+
<img id="" src="https://static.igem.org/mediawiki/2014/b/b5/SYSU-Software_project.png">
</div>
</div>
-
+
-
<div class="ui piled segment" style="top: 100px; width: 854px; margin:0px auto;">
+
<div class="flameMiddle">
-
+
<div style="height: 40px;"></div>
-
<br/>
+
<h1 style="text-align: center; font-size: 45px; font-weight: bold; font-family: cursive;">Overview</h1><br/>
-
<p>Softwares used for genetic circuit designs in synthetic biology (what we called “Synthetic Biology Operating System”, SBOS) can be divided into three catogaries: SBOS 1.0, SBOS 2.0 and SBOS 3.0.
+
<div class="ui piled segment" style="top: 40px; width: 854px; margin:0px auto;">
-
</p>
+
-
<br/>
+
<br/>
-
<p>SBOS 1.0 is for designs starting from parts to modules. Based on a framework from which users choose the suitable promoters, RBS (ribosome binding sites), coding sequences and terminators to construct a module so called ”biobrick”. For SBOS 2.0, once users specify logic relationships between modules (Biobricks) to construct a system, SBOS 2.0 (such as CAST created by our team SYSU-Software last year) helps to characterize the behaviour of the system.
+
<p>Softwares used for genetic circuit designs in synthetic biology (what we called “Synthetic Biology Operating System”, SBOS) can be divided into three catogaries: SBOS 1.0, SBOS 2.0 and SBOS 3.0.
-
</p>
+
</p>
-
<br/>
+
<br/>
-
<p>However, SBOS 2.0 hardly tackle tow major problems. One is that SBOS 2.0 need much mannual work. Users have to “link” the chosen parts and modules in order to make a system, making users confused about what hundreds of thousands of parts and mudules are for. SBOS 2.0 has a second problem that is great enough to make its applications limited to simple designs. The problem is that user-designs do not mean usable. Due to wide range of imcompatiblities among parts and modules, the designed system may not run well.
+
<p>SBOS 1.0 is for designs starting from parts to modules. Based on a framework from which users choose the suitable promoters, RBS (ribosome binding sites), coding sequences and terminators to construct a module so called ”biobrick”. For SBOS 2.0, once users specify logic relationships between modules (Biobricks) to construct a system, SBOS 2.0 (such as CAST created by our team SYSU-Software last year) helps to characterize the behaviour of the system.
-
</p><br/>
+
</p>
-
<p> So, SBOS 3.0 can help you! Based on principles of design frameworks, this software provides you with smarter, more automatic designs. With standardized biobricks and databases, the software automatically joins parts and modules and consequently a system come into being. That is, after you define the inputs, outputs and logic between them, our software offers you with different solutions (that is, different mechanisms for the same effect) , the performance of each can be visible via a rader map. The built-in databases are abstracted from papers of considerable values of reference. </p><br/>
+
<br/>
 +
<p>However, SBOS 2.0 hardly tackle tow major problems. One is that SBOS 2.0 need much mannual work. Users have to “link” the chosen parts and modules in order to make a system, making users confused about what hundreds of thousands of parts and mudules are for. SBOS 2.0 has a second problem that is great enough to make its applications limited to simple designs. The problem is that user-designs do not mean usable. Due to wide range of imcompatiblities among parts and modules, the designed system may not run well.
 +
</p><br/>
 +
<p> So, SBOS 3.0 can help you! Based on principles of design frameworks, this software provides you with smarter, more automatic designs. With standardized biobricks and databases, the software automatically joins parts and modules and consequently a system come into being. That is, after you define the inputs, outputs and logic between them, our software offers you with different solutions (that is, different mechanisms for the same effect) , the performance of each can be visible via a rader map. The built-in databases are abstracted from papers of considerable values of reference. </p><br/>
-
<p>It is far from finishing a design when a system comes out. Our software can mathematically simulate three major characteristics that describe the behaviour of the system: static performance, dynamic performance and expression efficiency, which might help you determine the performance of your designed system.</p><br/>
+
<p>It is far from finishing a design when a system comes out. Our software can mathematically simulate three major characteristics that describe the behaviour of the system: static performance, dynamic performance and expression efficiency, which might help you determine the performance of your designed system.</p><br/>
</div>
</div>
-
 
+
 +
</div>
 +
<div id="flameBottom">
<div id="flameBottom">
<img id="" src="https://static.igem.org/mediawiki/2014/5/56/SYSU-Software_footer.png">
<img id="" src="https://static.igem.org/mediawiki/2014/5/56/SYSU-Software_footer.png">
Line 126: Line 155:
     <div id="bgToTop">
     <div id="bgToTop">
-
<div class='rightCircle'></div>
+
<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>
</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>
</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://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/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&amp;ctype=text/css"></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>
</html>

Latest revision as of 14:51, 10 October 2014

Team:SYSU-Software

Overview



Softwares used for genetic circuit designs in synthetic biology (what we called “Synthetic Biology Operating System”, SBOS) can be divided into three catogaries: SBOS 1.0, SBOS 2.0 and SBOS 3.0.


SBOS 1.0 is for designs starting from parts to modules. Based on a framework from which users choose the suitable promoters, RBS (ribosome binding sites), coding sequences and terminators to construct a module so called ”biobrick”. For SBOS 2.0, once users specify logic relationships between modules (Biobricks) to construct a system, SBOS 2.0 (such as CAST created by our team SYSU-Software last year) helps to characterize the behaviour of the system.


However, SBOS 2.0 hardly tackle tow major problems. One is that SBOS 2.0 need much mannual work. Users have to “link” the chosen parts and modules in order to make a system, making users confused about what hundreds of thousands of parts and mudules are for. SBOS 2.0 has a second problem that is great enough to make its applications limited to simple designs. The problem is that user-designs do not mean usable. Due to wide range of imcompatiblities among parts and modules, the designed system may not run well.


So, SBOS 3.0 can help you! Based on principles of design frameworks, this software provides you with smarter, more automatic designs. With standardized biobricks and databases, the software automatically joins parts and modules and consequently a system come into being. That is, after you define the inputs, outputs and logic between them, our software offers you with different solutions (that is, different mechanisms for the same effect) , the performance of each can be visible via a rader map. The built-in databases are abstracted from papers of considerable values of reference.


It is far from finishing a design when a system comes out. Our software can mathematically simulate three major characteristics that describe the behaviour of the system: static performance, dynamic performance and expression efficiency, which might help you determine the performance of your designed system.


Retrieved from "http://2014.igem.org/Team:SYSU-Software/overview"