Team:OUC-China/Modeling/ParameterSweep
From 2012.igem.org
(3 intermediate revisions not shown) | |||
Line 6: | Line 6: | ||
<link rel="stylesheet" href="http://1.oucigem.sinaapp.com/down-icon.css"><!--download pdf css--> | <link rel="stylesheet" href="http://1.oucigem.sinaapp.com/down-icon.css"><!--download pdf css--> | ||
<style> | <style> | ||
+ | #back-top { | ||
+ | position: fixed; | ||
+ | bottom: 60px; | ||
+ | margin-left: 1160px; | ||
+ | } | ||
+ | #back-top a { | ||
+ | width:85px; | ||
+ | display: block; | ||
+ | text-align: center; | ||
+ | font: 11px/100% Arial, Helvetica, sans-serif; | ||
+ | text-transform: uppercase; | ||
+ | text-decoration: none; | ||
+ | color: #bbb; | ||
+ | -webkit-transition: 1s; | ||
+ | -moz-transition: 1s; | ||
+ | transition: 1s; | ||
+ | } | ||
+ | #back-top a:hover { | ||
+ | color: #000; | ||
+ | } | ||
+ | #back-top span { | ||
+ | width: 85px; | ||
+ | height: 85px; | ||
+ | display: block; | ||
+ | margin-bottom: 7px; | ||
+ | background: #B9B7B7 url(https://static.igem.org/mediawiki/2012/5/5e/Ouc-2012-up-arrow.png) no-repeat center center; | ||
+ | -webkit-border-radius: 15px; | ||
+ | -moz-border-radius: 15px; | ||
+ | border-radius: 15px; | ||
+ | -webkit-transition: 1s; | ||
+ | -moz-transition: 1s; | ||
+ | transition: 1s; | ||
+ | } | ||
+ | #back-top a:hover span { | ||
+ | background-color: #777; | ||
+ | } | ||
*{ | *{ | ||
margin:0; | margin:0; | ||
Line 394: | Line 430: | ||
<h1 style="border-bottom:none;">Parameter sweep</h1> | <h1 style="border-bottom:none;">Parameter sweep</h1> | ||
<br/> | <br/> | ||
- | <p><strong>Aim:</strong>To discover the optimized ranges of important parameters. | + | <p><strong>Aim:</strong>To discover the optimized ranges of important parameters and get specific directions from simulation heatmap. |
<br/> | <br/> | ||
<p><strong>Steps:</strong> | <p><strong>Steps:</strong> | ||
Line 482: | Line 518: | ||
</div> | </div> | ||
</div> | </div> | ||
+ | <p id="back-top"> | ||
+ | <a href="#top"><span></span>Back to Top</a> | ||
+ | </p> | ||
</body> | </body> | ||
+ | <script> | ||
+ | $(document).ready(function(){ | ||
+ | // hide #back-top first | ||
+ | $("#back-top").hide(); | ||
+ | |||
+ | // fade in #back-top | ||
+ | $(function () { | ||
+ | $(window).scroll(function () { | ||
+ | if ($(this).scrollTop() > 100) { | ||
+ | $('#back-top').fadeIn(); | ||
+ | } else { | ||
+ | $('#back-top').fadeOut(); | ||
+ | } | ||
+ | }); | ||
+ | |||
+ | // scroll body to 0px on click | ||
+ | $('#back-top a').click(function () { | ||
+ | $('body,html').animate({ | ||
+ | scrollTop: 0 | ||
+ | }, 800); | ||
+ | return false; | ||
+ | }); | ||
+ | }); | ||
+ | }); | ||
+ | </script> | ||
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"> | <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"> | ||
</script> | </script> |
Latest revision as of 01:51, 27 October 2012
Parameter sweep
Aim:To discover the optimized ranges of important parameters and get specific directions from simulation heatmap.
Brief Result:We determined the optimal parameter ranges for the ternary system, and selected a best parameter set for noise analysis.
Why choose slope as an indicator?
Slope is given by : Slope= Δ[m]steady/Δratio=2* ([m]steady1:1 - [m]steady1:2)
Also slope is not the only candidate indicator, the other indicator candidates weeded out are given below:
‘Sensitive’ does not means ‘important’
Sensitive does not means important, for sensitive parameters are fixed inherently and are not adjustable, always.
We swept 4 parameters for the reasons given below:
Establish parameter sweep database (4 parameters at the same time)
We swept km,βm,αm, ks at the same time and collected 120,000 3-ODE steady-state datapoints by mass computation.
For the database is a collection of 5-Dimensional data points, it’s rational to show the result in the format of projection on 2-D surface to indicate the relationship between slope and arbitrary 2 parameters we swept
Comparator(slope vs. arbitrary 2 parameters)
Ratio Senor(slope vs. arbitrary 2 parameters)
Determine optimal parameter range
We screened the database to get rid of unreasonable datapoints with restrictions:
We will use the best parameter set to perform noise analysis.