Team:USTC-Software/project

From 2011.igem.org

(Difference between revisions)
 
(6 intermediate revisions not shown)
Line 1: Line 1:
__NOTOC__
__NOTOC__
-
{{:Team:USTC-Software/temp}}
+
{{:Team:USTC-Software/header}}
-
 
+
<html xmlns="http://www.w3.org/1999/xhtml">
<html xmlns="http://www.w3.org/1999/xhtml">
-
<head>
 
-
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
 
-
<title>Team:USTC-Software - 2011.igem.org/project</title>
 
-
<meta name="description" content="project"/>
 
-
<meta name="keywords" content="USTC-Software,iGEM,synthetic biology"/>
 
-
<meta name="author" content="Ao Xu">
 
-
<meta name="copyright" content="Copyright (c) 2011 iGEM USTC Software" />
 
-
 
-
<style type="text/css">
 
-
 
-
body {
 
-
margin: 0;
 
-
padding: 0;
 
-
line-height: 1.5em;
 
-
font-family: Georgia, "Times New Roman", Times, serif;
 
-
font-size: 12px;
 
-
color: #555a4a;
 
-
    background: #a0c73f;
 
-
}
 
-
 
-
a:link, a:visited { color: #0683ab; text-decoration: none; font-weight: normal; }
 
-
a:active, a:hover { color: #0683ab; text-decoration: underline; }
 
-
 
-
img { margin: 0px; padding: 0px; border: none; }
 
-
 
-
#header_wrapper {
 
-
width: 100%;
 
-
height: 265px;
 
-
background: url(https://static.igem.org/mediawiki/2011/0/04/USTC_Software_header.jpg) no-repeat top center;
 
-
}
 
-
 
-
#header {
 
-
position: relative;
 
-
width: 980px;
 
-
height: 265px;
 
-
padding: 0 10px;
 
-
margin: 0 auto;
 
-
background: url(https://static.igem.org/mediawiki/2011/0/04/USTC_Software_header.jpg) no-repeat top center;
 
-
}
 
-
 
-
/* site title */
 
-
 
-
#header  #site_title {
 
-
float: left;
 
-
width: 180px;
 
-
padding: 33px 0;
 
-
}
 
-
 
-
#site_title h1 {
 
-
margin: 0;
 
-
padding: 3px;
 
-
font-family:"Times New Roman", Times, serif;
 
-
color:#000;
 
-
font-size:24px;
 
-
}
 
-
 
-
#site_title h1 a {
 
-
margin: 0px;
 
-
padding: 0px;
 
-
font-size: 30px;
 
-
color: #ffffff;
 
-
font-weight: bold;
 
-
text-decoration: none;
 
-
}
 
-
 
-
#site_title h1 a:hover {
 
-
font-weight: bold;
 
-
text-decoration: none;
 
-
}
 
-
 
-
#site_title h1 a span {
 
-
display: block;
 
-
margin-left: 2px;
 
-
font-size: 14px;
 
-
color: #416902;
 
-
font-weight: bold;
 
-
letter-spacing: 2px;
 
-
}
 
-
 
-
/* end of site title */
 
-
 
-
/* ---------- Navigation ---------- */
 
-
 
-
ul  {
 
-
      list-style-image: none;
 
-
}
 
-
 
-
#nav {
 
-
float: right;
 
-
font-family: Arial, Helvetica, sans-serif;
 
-
font-weight: bold;
 
-
font-size: 12px;
 
-
padding-top: 70px;
 
-
height: 43px;
 
-
}
 
-
 
-
#nav .last {
 
-
padding-right: 2px;
 
-
background-image:url(https://static.igem.org/mediawiki/2011/5/59/USTC_Software_nav_button_sep.jpg);
 
-
background-repeat:no-repeat;
 
-
background-position:right;
 
-
}
 
-
 
-
#nav, #nav ul{
 
-
margin:0;
 
-
padding:0;
 
-
list-style-type:none;
 
-
list-style-position:outside;
 
-
position:relative;
 
-
line-height:1.5em;
 
-
}
 
-
 
-
#nav .on {
 
-
color:#fff !important;
 
-
background-image: url(https://static.igem.org/mediawiki/2011/0/00/USTC_Software_nav_button_bg.jpg) !important;
 
-
background-position: bottom left !important;
 
-
}
 
-
 
-
#nav a:link, #nav a:active, #nav a:visited{
 
-
    display:block;
 
-
    padding: 14px 35px;
 
-
    color:#a5a5a5;
 
-
    text-decoration:none;
 
-
text-transform: uppercase;
 
-
background-image: url(https://static.igem.org/mediawiki/2011/0/00/USTC_Software_nav_button_bg.jpg);
 
-
background-position: top left;
 
-
}
 
-
 
-
#nav a:hover {
 
-
    color:#fff;
 
-
background-image: url(https://static.igem.org/mediawiki/2011/0/00/USTC_Software_nav_button_bg.jpg);
 
-
background-position: bottom left;
 
-
}
 
-
 
-
#nav li{
 
-
    float:left;
 
-
    position:relative;
 
-
 
-
}
 
-
 
-
#nav ul {
 
-
    position:absolute;
 
-
    width:13em;
 
-
    top:3.8em;
 
-
    display:none;
 
-
z-index: 1;
 
-
}
 
-
 
-
#nav li ul a {
 
-
    width:9em;
 
-
    float:left;
 
-
background-color: #2e2e2e;
 
-
background-image: none !important;
 
-
}
 
-
 
-
#nav li ul a:hover {
 
-
background-color: #292929;
 
-
}
 
-
 
-
#nav ul ul{
 
-
top:auto;
 
-
}
 
-
 
-
#nav li ul ul {
 
-
    left:12em;
 
-
    margin:0px 0 0 10px;
 
-
    }
 
-
 
-
#nav li:hover ul ul, #nav li:hover ul ul ul, #nav li:hover ul ul ul ul{
 
-
    display:none;
 
-
    }
 
-
 
-
#nav li:hover ul, #nav li li:hover ul, #nav li li li:hover ul, #nav li li li li:hover ul{
 
-
    display:block;
 
-
    }
 
-
 
-
/*end of nav*/
 
-
 
-
/* content_wrapper */
 
-
 
-
#content {
 
-
        background-color:#a0c73f;
 
-
        width:auto;
 
-
}
 
-
 
-
#content_wrapper {
 
-
width: 920px;
 
-
margin: 0 auto;
 
-
padding: 30px 40px;
 
-
background: url(https://static.igem.org/mediawiki/2011/b/bc/USTC_Software_content.jpg) repeat-y;
 
-
}
 
-
 
-
#content_wrapper h1 {
 
-
color: #3a5909;
 
-
font-size: 24px;
 
-
padding: 0 0 60px 20px;
 
-
background: url(https://static.igem.org/mediawiki/2011/4/4d/USTC_Software_header_bg.png) no-repeat bottom left;
 
-
}
 
-
 
-
 
-
#content_wrapper p {
 
-
font-family: Verdana, Arial;
 
-
font-size: 14px;
 
-
}
 
-
 
-
#intro p{
 
-
        font-family: Verdana, Arial;
 
-
font-size: 12px;
 
-
}
 
-
 
-
#content_wrapper_bottom {
 
-
width: 1000px;
 
-
height: 15px;
 
-
margin: 0 auto;
 
-
background: url(https://static.igem.org/mediawiki/2011/a/a5/USTC_Software_content_bottom.jpg) no-repeat;
 
-
    background-color: #a0c73f;
 
-
}
 
-
 
-
/* end of content_wrapper */
 
-
 
-
/* footer */
 
-
 
-
#mfooter {
 
-
width: 980px;
 
-
margin: 0 auto;
 
-
padding: 30px 10px;
 
-
text-align: center;
 
-
color: #333333;
 
-
    background-color: #a0c73f;
 
-
}
 
-
 
-
#mfooter a {
 
-
color:#000;
 
-
}
 
-
 
-
#mfooter .mfooter_menu {
 
-
margin: 0 0 10px 0;
 
-
padding: 0px;
 
-
list-style: none;
 
-
}
 
-
 
-
.mfooter_menu li {
 
-
margin: 0px;
 
-
padding: 0 20px;
 
-
display: inline;
 
-
border-right: 1px solid #000000;
 
-
}
 
-
 
-
.mfooter_menu .last_menu {
 
-
border: none;
 
-
}
 
-
 
-
#footer-box { background-color: transparent; border:none;} /*This is important!*/
 
-
 
-
#totop_box {
 
-
position:fixed;
 
-
width: 77px;
 
-
height: 75px;
 
-
bottom: 21px;
 
-
right: 15px;
 
-
}
 
-
 
-
#totop_box form {
 
-
width: 280px;
 
-
height: 27px;
 
-
margin: 0;
 
-
padding: 25px 0 0 0;
 
-
}
 
-
 
-
#to_org_box {
 
-
position:fixed;
 
-
width: 77px;
 
-
height: 75px;
 
-
bottom: 21px;
 
-
right: 105px;
 
-
}
 
-
 
-
#to_org_box form {
 
-
width: 280px;
 
-
height: 27px;
 
-
margin: 0;
 
-
padding: 25px 0 0 0;
 
-
}
 
-
/* end of footer*/
 
-
 
-
.ul_p{
 
-
font-family: Verdana, Arial;
 
-
font-size: 14px;
 
-
}
 
-
 
-
</style>
 
-
 
-
</head>
 
-
 
<body>
<body>
-
<div id="header_wrapper">
 
-
 
-
    <div id="header">
 
-
   
 
-
  <div id="site_title">
 
-
            <h1><img src="https://static.igem.org/mediawiki/2011/b/b8/USTC_Software_iGEM_logo.jpg" alt="iGEM" width="173" height="150" /> </br> </br> USTC-Software </h1>
 
-
        </div>
 
-
       
 
-
<!-- navigation -->
 
-
<ul id="nav">
 
-
<li><a href="https://2011.igem.org/Team:USTC-Software">Home</a></li>
 
-
 
-
    <li><a class="on" href="https://2011.igem.org/Team:USTC-Software/project">Project</a>
 
-
<ul>
 
-
<li><a href="https://2011.igem.org/Team:USTC-Software/documents">Documents Parser & Models </a></li>
 
-
<li><a href="#">Views</a>
 
-
                                  <ul>
 
-
                                      <li><a href="https://2011.igem.org/Team:USTC-Software/aview">Assembly View</a></li>
 
-
                                      <li><a href="https://2011.igem.org/Team:USTC-Software/bview">Behavior View</a></li>
 
-
                                      <li><a href="https://2011.igem.org/Team:USTC-Software/nview">Network View</a></li>                     
 
-
                                  </ul>
 
-
                                </li>
 
-
 
-
                                <li><a href="#">Technology & Algorithm</a>
 
-
                                  <ul>
 
-
                                    <li><a href="https://2011.igem.org/Team:USTC-Software/parameter">parameter analysis</a></li>
 
-
                                    <li><a href="https://2011.igem.org/Team:USTC-Software/model">MoDeL</a></li>
 
-
                                  </ul>
 
-
                                </li>
 
-
                                   
 
-
                                <li><a href="https://2011.igem.org/Team:USTC-Software/tutorial">Tutorial & Demo</a></li>
 
-
</ul>
 
-
</li>
 
-
 
-
                <li><a href="https://2011.igem.org/Team:USTC-Software/notebook">Notebook</a></li>
 
-
 
-
<li><a href="https://2011.igem.org/Team:USTC-Software/team">Team</a>
 
-
                        <ul>
 
-
                            <li><a href="https://2011.igem.org/Team:USTC-Software/members">members</a></li>
 
-
                            <li><a href="https://2011.igem.org/Team:USTC-Software/collaboration">collaboration</a></li>
 
-
                            <li><a href="https://2011.igem.org/Team:USTC-Software/attribution">attribution & contributions</a></li>
 
-
                            <li><a href="https://2011.igem.org/Team:USTC-Software/acknowledgements">acknowledgements</a></li>
 
-
                        </ul>
 
-
                </li>
 
-
 
 
-
  <li><a class="last"href="https://2011.igem.org/Team:USTC-Software/human practice">Human practice</a> 
 
-
<ul>
 
-
    <li><a href="https://2011.igem.org/Team:USTC-Software/safety">safety</a></li>
 
-
    <li><a href="https://2011.igem.org/Team:USTC-Software/meetup">meetup</a></li>
 
-
</ul>
 
-
</li> 
 
-
 
-
<li><a href="https://2011.igem.org/Team:USTC-Software/download">Download</a></li>           
 
-
</ul>
 
-
<!-- end of navigation -->
 
-
     
 
-
      <div class="cleaner"></div>
 
-
    </div> <!-- end of header -->
 
-
 
-
</div>
 
-
<!-- end of header_wrapper -->
 
<div id="content_wrapper">
<div id="content_wrapper">
Line 368: Line 12:
           <li><a href="#Introduction">Introduction</a></li>  
           <li><a href="#Introduction">Introduction</a></li>  
             <ul type="circle">
             <ul type="circle">
 +
            <!-- <li><a href="#Motivation">Motivation</a></li>-->
               <li><a href="#What is Lachesis?">What is Lachesis?</a></li>
               <li><a href="#What is Lachesis?">What is Lachesis?</a></li>
               <li><a href="#Available Features for Now">Available Features for Now</a></li>
               <li><a href="#Available Features for Now">Available Features for Now</a></li>
Line 384: Line 29:
                
                
</div>   
</div>   
-
 
+
<!--
-
<h2><a name="Introduction" id="Introduction"></a><strong>Motivation</strong></h2>
+
<h2><a name="Motivation" id="Motivation"></a><strong>Motivation</strong></h2>-->
-
<p>CAD tools in the field of electronic engineering has become a necessity, it saves the engineer a lot of time from simple trial and error.</p>
+
<!--<p>CAD tools in the field of electronic engineering has become a necessity, it saves the engineer a lot of time from simple trial and error.</p>
   <p>Design in silicon is flexible, and one can manage the complexity of a framework, and analyze the result easily.</p>
   <p>Design in silicon is flexible, and one can manage the complexity of a framework, and analyze the result easily.</p>
   <p>But in silicon design of gene circuit is far from mature. Pursuant to the goal of a user friendly tool, which can really give synthetic biologist some aids in designing gene circuit, the USTC SOFTWARE oriented in the following points:</p>
   <p>But in silicon design of gene circuit is far from mature. Pursuant to the goal of a user friendly tool, which can really give synthetic biologist some aids in designing gene circuit, the USTC SOFTWARE oriented in the following points:</p>
Line 394: Line 39:
<p>• Combine rational design and directed evolution with an assessment tool of the robustness of the circuit.</p>
<p>• Combine rational design and directed evolution with an assessment tool of the robustness of the circuit.</p>
<p>• Various criteria to access a design: robustness to parameter variation and stochastic noise.</p>
<p>• Various criteria to access a design: robustness to parameter variation and stochastic noise.</p>
-
 
+
-->
<h3><a name="What is Lachesis?" id="What is Lachesis?"></a>What is Lachesis?</h3>
<h3><a name="What is Lachesis?" id="What is Lachesis?"></a>What is Lachesis?</h3>
Line 435: Line 80:
<h3><a name="Future Plans" id="Future Plans"></a>Future Plans</h3>
<h3><a name="Future Plans" id="Future Plans"></a>Future Plans</h3>
-
<p>In the future version of our software, we plan to combine the reverse and forward engineering approach more closely, hoping to give users more guide to achieve better performance of the gene circuit. Probably from the following prospect:<br/>
+
<p>In the future version of our software, we plan to combine the reverse and forward engineering approach more closely, hoping to give users more guide to achieve better performance of the gene circuit. Probably from the following prospect:</p>
-
• Find a good algorithm to mutate the design automatically.<em>For example</em>, keep the backbone of the assembly, and change the “connections” of the parts, discover various combinations to get new features.<em>For example</em>, change the assembly Promoter1(gene1 repressed)-rbs-gene1-term1-promoter2(gene1 repressed)-rbs-gene2-term2  to Promoter1(gene2 activate)-rbs-gene1-term1-promoter2(gene1 repressed)-rbs-gene2-term2 would get a new behavior. We are inspired by many literatures and find this interesting. A fast such algorithm would help speed up the evolutionary process in silicon.<br/>
+
<p> • Find a good algorithm to mutate the design automatically.
-
•Integrate more Synthetic biology network analysis approach into our software.<br/>
+
Keep the backbone of the biobrick assembly, and change the “connections” of the parts, discover various combinations or connectivities of parts to get new behaviors of the circuit.
-
•We are even thinking that we already have an rule based modeling approach, why can’t we have a rule based evolutionary design approach?  Which is we devise a good set of rules to decide how to mutate the network?</p>
+
<em>For example</em>, change the assembly Promoter1(gene1 repressed)-rbs-gene1-term1-promoter2(gene1 repressed)-rbs-gene2-term2  to Promoter1(gene2 activate)-rbs-gene1-term1-promoter2(gene1 repressed)-rbs-gene2-term2 would get a new behavior.  
-
 
+
We are inspired by many literatures and find this interesting. A fast such algorithm would help speed up the evolutionary process in silicon.</p>
 +
We are even thinking that we already have an rule based modeling approach, why can’t we have a rule based evolutionary design approach?  Devise a good set of rules to decide how to mutate the network?
 +
<p> •Integrate more Synthetic biology network analysis approachs into our software. For example, introduce more sensitivity and robustness analysis algorithms into our software.</p>
 +
<p> •Make a dynamic network view which can show the process of rule based modelling approch.
 +
<p> •Provide a graphics view to the structure of species.
 +
<p> •Provide a 3d view to show the dose response curve of a circuit.
</div>
</div>

Latest revision as of 13:59, 28 October 2011


Team:USTC-Software - 2011.igem.org

What is Lachesis?

The project Lachesis aims at providing an integrated, easy-using and extensible CAD environment for the general purpose of Synthetic Biology.

To achieve this goal, Lachesis adopts plug-ins based structure. We provide the following three kinds of plug-ins:

  • Document parsers that handles various types of files, such as SBML and MoDeL.
  • Models that each represents a specific kind of synthetic biological model.
  • Views that present graphical user interface for users to work with biological models.


Available Features for Now

We have developed several useful plug-ins to justify our motivation as well as make Lachesis a powerful tool for designing and simulating Synthetic Biology models. Lachesis is coded with C++ and Qt. We welcome everyone to develop more helpful plug-ins for Lachesis.

Documents parsers

Currently, we provide support for .sbml file, .model file and various kinds of other file types.

Models

  • Reaction Network Model represents an biological reaction network,e.g. read from an .sbml file,
  • MoDeL model represents an model for the software MoDeL, which is an refactored and superior version of our last year's project iGaME.

Views

  • Assembly View provides an easy-using graphical interface for working with MoDeL,
  • Network View provides an graphical interface for editing biological reaction network,
  • Parameter fitting view(still under construction) can analysis synthetic biology models' behavior with respect to parameter changing, and tune parameters to give the desired behavior.

Technology & Algorithms

Chen Liao refactored iGaME to form the new software package MoDeL, which is a rule-based modeling approach for synthetic biology.

Xudong Sun designed an algorithm for parameter analyzing for biological reaction network. We currently working on re-implementing the algorithm to provide an efficient graphical interface and free users from mathematical details.

Future Plans

In the future version of our software, we plan to combine the reverse and forward engineering approach more closely, hoping to give users more guide to achieve better performance of the gene circuit. Probably from the following prospect:

• Find a good algorithm to mutate the design automatically. Keep the backbone of the biobrick assembly, and change the “connections” of the parts, discover various combinations or connectivities of parts to get new behaviors of the circuit. For example, change the assembly Promoter1(gene1 repressed)-rbs-gene1-term1-promoter2(gene1 repressed)-rbs-gene2-term2 to Promoter1(gene2 activate)-rbs-gene1-term1-promoter2(gene1 repressed)-rbs-gene2-term2 would get a new behavior. We are inspired by many literatures and find this interesting. A fast such algorithm would help speed up the evolutionary process in silicon.

We are even thinking that we already have an rule based modeling approach, why can’t we have a rule based evolutionary design approach? Devise a good set of rules to decide how to mutate the network?

•Integrate more Synthetic biology network analysis approachs into our software. For example, introduce more sensitivity and robustness analysis algorithms into our software.

•Make a dynamic network view which can show the process of rule based modelling approch.

•Provide a graphics view to the structure of species.

•Provide a 3d view to show the dose response curve of a circuit.