|
Size: 312
Comment:
|
Size: 2011
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = ScrumPy Manual = | ## page was renamed from Software/ScrumPy/Doc = ScrumPy - Metabolic Modelling in Python = <<TableOfContents>> |
| Line 3: | Line 6: |
| === Metabolic Modelling === === 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. |
|
| Line 4: | Line 10: |
| === Why Python ? === | 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 - |
| Line 6: | Line 12: |
| 'cause it's great. | 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. === Python === [[ScrumPy/Doc/PyNotes|Python notes]] == ScrumPy Model Description Language == [[SpyMDL#Overview|Overview]] [[SpyMDL#Identifiers|Identifiers]] [[SpyMDL#Reactions|Reactions]] [[SpyMDL#Directives|Directives]] == Analysis of Models With ScrumPy == === The ScrumPy Modelling Environment === [[ScrumPy/Doc/ModEnv#RunSpy | Running ScrumPy]] |
| Line 9: | Line 32: |
| === What ScrumPy Is === | [[ScrumPy/Doc/ModEnv#LoadSpy | Loading Models]] |
| Line 11: | Line 34: |
| === What ScrumPy Isn't === | [[ScrumPy/Doc/StruMod | Structural Modelling ]] |
| Line 13: | Line 36: |
| === Quick examples === | [[ScrumPy/Doc/LinProg | Linear Programming ]] |
| Line 15: | Line 38: |
| [[ScrumPy/Doc/KinMod | Kinetic Modelling ]] | |
| Line 16: | Line 40: |
| == ScrumPy model format == == Structural Analysis of Models == == Kinetic Analysis of Models == |
== Secondary Analysis of Model Results == === Data sets === === Fitting and Optimisation === == Automatic Model Building == |
| Line 23: | Line 45: |
| == The Utility Package == === Dynamic Matrices === |
ScrumPy - Metabolic Modelling in Python
Contents
Introduction
Metabolic Modelling
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.
Python
ScrumPy Model Description Language
Analysis of Models With ScrumPy
The ScrumPy Modelling Environment
Secondary Analysis of Model Results
Data sets
Fitting and Optimisation
Automatic Model Building
Bioinformatics Functions
The Utility Package