|
Size: 635
Comment:
|
Size: 2109
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| = ScrumPy Manual = | = ScrumPy - Metabolic Modelling in Python = <<TableOfContents>> |
| Line 6: | Line 8: |
| Scrumpy is unusual, but not unique, in that the primary user interface is a language (it is an oversimplification to refer to it as a command line interface) rather than a more conventional GUI. The underlying reason for this choice is a simple one: A GUI restricts the user to only those actions which the programmer mpredicted the user might wish to perform. In some contexts this is not a problem, simple text editing and web-browsing being examples. However, in metabolic modelling (and scietific/research contexts in general) it is much harder for the programmer to predict what a user may wish to do. MORE HERE - Furthermore, in the twenty or so years in which I have been involved in the field, I have lost count of the number of presentations I've listened to for software (not only modelling or scientific) making the claim that the software is intuitive and user friendly, to the extent that this has become a mantra to be uttered at the begining of every presentation. Most of it has been unconvincing at best. |
|
| Line 7: | Line 15: |
| [[ScrumPy/Doc/PyNotes|Python notes]] |
|
| Line 8: | Line 18: |
| [[SpyMDL#Overview|Overview]] [[SpyMDL#Identifiers|Identifiers]] [[SpyMDL#Reactions|Reactions]] [[SpyMDL#Directives|Directives]] |
|
| Line 10: | Line 28: |
[[ScrumPy/Doc/ModEnv#RunSpy | Running ScrumPy]] [[ScrumPy/Doc/ModEnv#LoadSpy | Loading Models]] === The Matrix Class === Fully described in utility section - enough here to understand SMs, datasets and monitors. |
|
| Line 18: | Line 47: |
| == Structural Analysis of Models == == Kinetic Analysis of Models == |
|
| Line 21: | Line 48: |
| == The Utility Package == === Dynamic Matrices === |
ScrumPy - Metabolic Modelling in Python
Contents
1. Introduction
1.1. Metabolic Modelling
1.2. Design Philosophy
Scrumpy is unusual, but not unique, in that the primary user interface is a language (it is an oversimplification to refer to it as a command line interface) rather than a more conventional GUI. The underlying reason for this choice is a simple one: A GUI restricts the user to only those actions which the programmer mpredicted the user might wish to perform. In some contexts this is not a problem, simple text editing and web-browsing being examples.
However, in metabolic modelling (and scietific/research contexts in general) it is much harder for the programmer to predict what a user may wish to do. MORE HERE -
Furthermore, in the twenty or so years in which I have been involved in the field, I have lost count of the number of presentations I've listened to for software (not only modelling or scientific) making the claim that the software is intuitive and user friendly, to the extent that this has become a mantra to be uttered at the begining of every presentation. Most of it has been unconvincing at best.
1.3. Python
2. ScrumPy Model Description Language
3. Analysis of Models With ScrumPy
3.1. The ScrumPy Modelling Environment
3.2. The Matrix Class
Fully described in utility section - enough here to understand SMs, datasets and monitors.
3.3. Anatomy of a ScrumPy Model
3.4. Kinetic Modelling
3.5. Structural Modelling
3.6. Linear Programming
4. Secondary Analysis of Model Results
4.1. Data sets
4.2. Fitting and Optimisation
5. Automatic Model Building
6. Bioinformatics Functions
7. The Utility Package