|
Size: 690
Comment:
|
Size: 2160
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| = ScrumPy Manual = | = ScrumPy - Metabolic Modelling in Python = <<TableOfContents>> |
| Line 4: | 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 5: | Line 10: |
| === Metabolic Modelling === | 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 7: | Line 12: |
| === Design Philosophy === | 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 9: | Line 14: |
| === Python === | === Tutorials === [[ScrumPy/Doc/Tutorial/PyIntro | Introduction to Python]] [[ScrumPy/Doc/Tutorial/ScrumPyIntro | Introduction to ScrumPy]] === Python === [[ScrumPy/Doc/PyNotes|Python notes]] |
| Line 12: | Line 24: |
| [[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 14: | Line 38: |
| [[ScrumPy/Doc/ModEnv#LoadSpy | Loading Models]] | |
| Line 15: | Line 40: |
| == Analysis of Models With ScrumPy == | [[ScrumPy/Doc/StruMod | Structural Modelling ]] |
| Line 17: | Line 42: |
| [[ScrumPy/Doc/LinProg | Linear Programming ]] | |
| Line 18: | Line 44: |
| === The ScrumPy Modelling Environment === === Anatomy of a ScrumPy Model === === Kinetic Modelling === === Structural Modelling === === Linear Programming === |
[[ScrumPy/Doc/KinMod | Kinetic Modelling ]] |
| Line 32: | Line 47: |
| Line 35: | Line 48: |
| Line 37: | Line 49: |
| Line 39: | Line 50: |
== Structural Analysis of Models == == Kinetic Analysis of Models == |
|
| Line 48: | Line 51: |
| == 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.
Tutorials
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