Team:USTC-Software/model
From 2011.igem.org
Line 312: | Line 312: | ||
<li><a class="on" href="https://2011.igem.org/Team:USTC-Software/project">Project</a> | <li><a class="on" href="https://2011.igem.org/Team:USTC-Software/project">Project</a> | ||
<ul> | <ul> | ||
- | <li><a href="https://2011.igem.org/Team:USTC-Software/documents">Documents Parser | + | <li><a href="https://2011.igem.org/Team:USTC-Software/documents">Documents Parser & Models </a></li> |
- | + | ||
<li><a href="#">Views</a> | <li><a href="#">Views</a> | ||
<ul> | <ul> | ||
Line 322: | Line 321: | ||
</li> | </li> | ||
- | <li><a href="https://2011.igem.org/Team:USTC-Software/ | + | <li><a href="#">Technology & Algorithm</a></li> |
+ | <ul> | ||
+ | <li><a href="https://2011.igem.org/Team:USTC-Software/model">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> | <li><a href="https://2011.igem.org/Team:USTC-Software/tutorial">Tutorial & Demo</a></li> | ||
</ul> | </ul> |
Revision as of 09:14, 5 October 2011
Contents:
MoDeL
The Perl language is a powerful tool for dealing with regular expressions, and it manages to process complex problems in a timely way. For example, for a hash array with a few elements in the buckets almost get the same manipulating time with a big hash with millions of elements. This feature improves the speed of rule based modeling remarkably.
Dealing with regular expressions is also Perl's cup of tea. So the software can spend more running time saved by perl on providing a better user's interface, making it more convenient for users.
Our approach first realized by Liaochen and 2010igemers emphasize on the structure of the species.
Here is a detailed explanation to the input file of the rule based modeling approach There are four blocks, respectively lists the definition of parameters, the definition of compartments, seed species and events.
The definition of parameters consists of two items. The left side term is the name of the variable, to the right is the expression of that parameter. Note that variables in that expression must be defined by the user. But it makes no difference whether they are defined before the expression. This is to avoid redundant definition and no definition.
SYNTAX
The compartments definition is in this way:
[name ][outside][ruletable]{volume}{population}, where terms in the square brackets are mandatory, while terms in the curly braces are optional.
The default value of the volume is 1. The outside term means the compartment outside the compartment, which is usually the medium that held the compartment like the ecoli.
Ruletable is used to associate a rule in the data base with the compartment.
The third block, reads [compartment][name][structure][init_concentration]{const}, structure is the definition of the complex structure, const is optional since it's in the curly brace. If the substance has a const property, then after the substance, write a const. if not, leave it blank.
The last block is the events definition. The formats are [name][trigger_condition][event_assignments...] The name of the event is usr defined, trigger_condition is a bool expression, all the variables inside this bool expression must have been defined in one of the above three blocks. Event_assignments is a list of assignments, something like assignment1 assignment2 assignment3, with white space separated. There is no constraint on the number of assignments. Each assignment must be the format [variable]=[expression]
A general rule in the algorithm is that the name of the variable must be started by A-Z –z and other characters can be A-Z-a-z-0-9.
Technology
Detailed technology used by the re-build version of MoDeL is not available for now. Please refer to our previous year's website here. The basic ideas are the same, but the algorithms are re-designed to run hundreds times faster.