Team:Edinburgh/Modelling/Future
From 2010.igem.org
Line 122: | Line 122: | ||
<a name="Future1" id="Future1"></a><h2>Future Work: Refining the models</h2> | <a name="Future1" id="Future1"></a><h2>Future Work: Refining the models</h2> | ||
<br> | <br> | ||
- | <p> | + | |
+ | <p>Refine model with characterisation data - models not only as design and prototyping tools, but also as fundamental components of iterative process in which they help predict and influence biological decisions, and are in turn updated and improve understanding via the characterisation data obtained (draw parallels to software engineering - extreme programming, in which models are only made as needed (iGEM) vs. model-driven development, in which models form core of development process - both have advantages according to the situation, but would be good to promote the latter for longer projects).</p> | ||
+ | |||
+ | <p>Perform further analysis to try to answer relevant biological questions, increase scope of modelling (i.e. 3D structural modelling of proteins such as light receptors, energy-based modelling involving thermodynamics and kinetic states).</p> | ||
<br> | <br> | ||
<br> | <br> | ||
Line 128: | Line 131: | ||
<a name="Future2" id="Future2"></a><h2>Future Work: The "Virtual Registry"</h2> | <a name="Future2" id="Future2"></a><h2>Future Work: The "Virtual Registry"</h2> | ||
<br> | <br> | ||
- | <p> | + | |
+ | <p>Formalise Ty Thomson's unofficial framework for modelling BioBricks in Kappa, possibly by submitting as a RFC, along with developing an associated "Virtual Registry" of characterised parts, devices, and models.</p> | ||
<br> | <br> | ||
<br> | <br> |
Revision as of 16:04, 6 October 2010
Future Work: Refining the models
Refine model with characterisation data - models not only as design and prototyping tools, but also as fundamental components of iterative process in which they help predict and influence biological decisions, and are in turn updated and improve understanding via the characterisation data obtained (draw parallels to software engineering - extreme programming, in which models are only made as needed (iGEM) vs. model-driven development, in which models form core of development process - both have advantages according to the situation, but would be good to promote the latter for longer projects).
Perform further analysis to try to answer relevant biological questions, increase scope of modelling (i.e. 3D structural modelling of proteins such as light receptors, energy-based modelling involving thermodynamics and kinetic states).
Future Work: The "Virtual Registry"
Formalise Ty Thomson's unofficial framework for modelling BioBricks in Kappa, possibly by submitting as a RFC, along with developing an associated "Virtual Registry" of characterised parts, devices, and models.