Team:USTC-Software/parameter
From 2011.igem.org
(Created page with "__NOTOC__ {{:Team:USTC-Software/temp}} <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>Team:USTC...") |
|||
Line 48: | Line 48: | ||
#header #site_title { | #header #site_title { | ||
float: left; | float: left; | ||
- | width: | + | width: 180px; |
padding: 33px 0; | padding: 33px 0; | ||
} | } | ||
Line 326: | Line 326: | ||
</div> | </div> | ||
- | + | <!-- navigation --> | |
- | + | <ul id="nav"> | |
- | + | <li><a href="https://2011.igem.org/Team:USTC-Software">Home</a></li> | |
- | + | ||
- | + | <li><a href="https://2011.igem.org/Team:USTC-Software/project">Project</a> | |
- | + | <ul> | |
- | + | <li><a href="https://2011.igem.org/Team:USTC-Software/parameter">Parameter section</a></li> | |
- | + | <li><a href="#">TBD_2</a></li> | |
- | + | <li><a href="#">TBD_3</a> | |
- | + | <ul> | |
- | + | <li><a href="#">TBD_3_1</a></li> | |
- | + | <li><a href="#">TBD_3_2</a></li> | |
- | + | <li><a href="#">TBD_3_3</a></li> | |
- | + | </ul> | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
</li> | </li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | |||
+ | <li><a href="https://2011.igem.org/Team:USTC-Software/download">Download</a></li> | ||
+ | |||
+ | <li><a class="on" 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/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/collaboration">collaboration</a></li> | ||
<li><a href="https://2011.igem.org/Team:USTC-Software/attribution">attribution</a></li> | <li><a href="https://2011.igem.org/Team:USTC-Software/attribution">attribution</a></li> | ||
<li><a href="https://2011.igem.org/Team:USTC-Software/acknowledgements">acknowledgements</a></li> | <li><a href="https://2011.igem.org/Team:USTC-Software/acknowledgements">acknowledgements</a></li> | ||
- | + | </ul> | |
</li> | </li> | ||
- | + | <li><a class="last"href="https://2011.igem.org/Team:USTC-Software/human practice">Human practice</a> <!--current page--> | |
- | + | <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> | </ul> | ||
- | + | </li> | |
+ | </ul> | ||
+ | <!-- // navigation --> | ||
- | + | <div class="cleaner"></div> | |
</div> <!-- end of header --> | </div> <!-- end of header --> | ||
Revision as of 12:46, 29 September 2011
USTC-Software
Parameter section
Background
A most ideal tool that already exist in electronics: User provide the part’s name, the software fetch the standard model and its associated parameter, and return a complete mathematical model with all the parameters known (for instance, the PROTEL-software can easily get the released device from the NI company with all the response parameters standardized from a device library).
But temporally, the knowledge and cognition level of synthetic biology do not support this:
Most parts do not have a standard model associated with it. Some parameters of the parts haven’t been measured yet. For some parts with quantitative parameter value, which is highly context dependent, is hard to transfer with defined parameter across different hosts.
More consideration
Why do we try automatic parameter fitting(or estimation, adjustment)?
I.If it’s a big network with too many parameters undefined, it would get the user exhausted adjusting all the empty parameters by hand according to his/her experience and web resource. Networks generated by rule based modeling is ordinarily large.
II.Compared to manually parameter adjustment, in silicon auto parameter adjustment is more convenient. It gives an estimation of the interest parameter value according to wet lab data, thus free the user from spending too much time on estimating a good parameter.
Successful examples
We adopted a demo from a Tinkercell tutorial website on implementing a simple repressilator. After the network is generated by hand, the parameters are left behind to the user to adjust themselves. But as you can see from the following four figures, the process is tough and time consuming. ( more snapshots of the process are eliminated )
add figures here... add figures here... add figures here... add figures here... add figures here...The four figures above show a difficult parameter adjustment process by hand.
By contrast, parameters estimated by our approach in silicon can be done in a timely fashion. It’s fast and convenient. (see figure below)
add figures here... add figures here... add figures here... add figures here... add figures here...Algorithm
PSO, SA(To be filled more content in several days)