Team:Groningen/Modeling
From 2011.igem.org
(→Modeling blog) |
|||
Line 8: | Line 8: | ||
*[[Team:Groningen/Modeling/Matlab with SimBiology|Matlab with SimBiology]] | *[[Team:Groningen/Modeling/Matlab with SimBiology|Matlab with SimBiology]] | ||
- | + | Although COPASI and SimBiology seemed really nice (be sure to look at it when in doubt) we decided to go with matlab for the following reasons: | |
* Freedom of programming: Although the matlab programming syntax is rather cumborsome (espcially when using OOP) we are sure it can produce anything we want. | * Freedom of programming: Although the matlab programming syntax is rather cumborsome (espcially when using OOP) we are sure it can produce anything we want. | ||
* Popularety: There is a very large userbase for matlab and plenty of support for it. Many other iGEM teams use it so it will be easy to share our finings and models. | * Popularety: There is a very large userbase for matlab and plenty of support for it. Many other iGEM teams use it so it will be easy to share our finings and models. | ||
* Great plotting and visalisation option: this will allow us to see what is going on without the hassle of exporting and importing the data to other packages. | * Great plotting and visalisation option: this will allow us to see what is going on without the hassle of exporting and importing the data to other packages. | ||
* Familiarety of the team: Not having to learn using a program from the beginning is a big advantage. Some of our members have years of experience with matlab and have no problem implementing anything in matlab. | * Familiarety of the team: Not having to learn using a program from the beginning is a big advantage. Some of our members have years of experience with matlab and have no problem implementing anything in matlab. | ||
+ | |||
+ | ==Library== | ||
+ | We are currently developing our own modeling library and hopefully we will be able to finish it in time for other teams to use it. It will be geared towards beginning/intermediate matlab users who want to model single cell processes. | ||
==Modules== | ==Modules== |
Revision as of 08:17, 24 May 2011
Because of the device-like nature of out project modeling plays a big part. This page gives an overview of some of our organistional considerations and provides links to the more practical aspects. A big consideration is that our modeling team comes from the local AI department and has significant experience in modeling in matlab.
Contents |
Methods
First of all we have to decide in what enviorment we want to model in. There is a lot of different software out there. Our 2009 team did a large survey on modeling packages used in Igem [1]. Our whitebook also included several biomodeling packages that we should look at:
Although COPASI and SimBiology seemed really nice (be sure to look at it when in doubt) we decided to go with matlab for the following reasons:
- Freedom of programming: Although the matlab programming syntax is rather cumborsome (espcially when using OOP) we are sure it can produce anything we want.
- Popularety: There is a very large userbase for matlab and plenty of support for it. Many other iGEM teams use it so it will be easy to share our finings and models.
- Great plotting and visalisation option: this will allow us to see what is going on without the hassle of exporting and importing the data to other packages.
- Familiarety of the team: Not having to learn using a program from the beginning is a big advantage. Some of our members have years of experience with matlab and have no problem implementing anything in matlab.
Library
We are currently developing our own modeling library and hopefully we will be able to finish it in time for other teams to use it. It will be geared towards beginning/intermediate matlab users who want to model single cell processes.
Modules
We decided to build our model in the samen modules as the cloners will use. Because of the fragilety of the by stable switches these should be modeled first.
Modeling blog
You can check our modeling progress on our modeling blog. This will contain weekly updates of our progress and some highligths of our results.
Home | Team | Official Team Profile | Project | Parts Submitted to the Registry | Modeling | Notebook | Safety | Attributions |
---|