|
Size: 1271
Comment:
|
Size: 2160
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| Line 5: | Line 4: |
| Line 8: | 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. === Tutorials === [[ScrumPy/Doc/Tutorial/PyIntro | Introduction to Python]] [[ScrumPy/Doc/Tutorial/ScrumPyIntro | Introduction to ScrumPy]] |
|
| Line 9: | Line 21: |
| ==== Knowing syntax vs programming ==== ==== Inbuilt types and classes ==== int, float, str, list and dict ==== Classes and sub-classes ==== ==== Repetiton and Decisions ==== ==== Functions ==== ==== Modules and Packages ==== ==== Standard libraries ==== Not all of them ! In practice math and random are the most commonly with {{{ScrumPy}}}. sys and os are also useful - any other suggestions ? |
[[ScrumPy/Doc/PyNotes|Python notes]] |
| Line 19: | Line 24: |
| === Overview === === Identifiers === === Reactions === === Directives === |
[[SpyMDL#Overview|Overview]] |
| Line 24: | Line 26: |
| [[SpyMDL#Identifiers|Identifiers]] [[SpyMDL#Reactions|Reactions]] [[SpyMDL#Directives|Directives]] |
|
| Line 27: | Line 34: |
| === The Matrix Class === Fully described in utility section - enough here to understand SMs, datasets and monitors. === Anatomy of a ScrumPy Model === === Kinetic Modelling === === Structural Modelling === === Linear Programming === |
[[ScrumPy/Doc/ModEnv#RunSpy | Running ScrumPy]] [[ScrumPy/Doc/ModEnv#LoadSpy | Loading Models]] [[ScrumPy/Doc/StruMod | Structural Modelling ]] [[ScrumPy/Doc/LinProg | Linear Programming ]] [[ScrumPy/Doc/KinMod | Kinetic Modelling ]] |
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. Tutorials
1.4. Python
2. ScrumPy Model Description Language
3. Analysis of Models With ScrumPy
3.1. The ScrumPy Modelling Environment
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