|
Size: 1223
Comment:
|
Size: 2052
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: |
| ==== 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 17: | Line 18: |
| === Overview === === Identifiers === === Reactions === === Directives === |
[[SpyMDL#Overview|Overview]] |
| Line 22: | Line 20: |
| [[SpyMDL#Identifiers|Identifiers]] [[SpyMDL#Reactions|Reactions]] [[SpyMDL#Directives|Directives]] |
|
| Line 25: | Line 28: |
[[ScrumPy/Doc/ModEnv#RunSpy | Running ScrumPy]] |
|
| Line 27: | Line 33: |
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
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
Secondary Analysis of Model Results
Data sets
Fitting and Optimisation
Automatic Model Building
Bioinformatics Functions
The Utility Package