|
Size: 1333
Comment:
|
← Revision 23 as of 2013-11-06 14:23:12 ⇥
Size: 3032
Comment: Amplified the contents.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| #pragma section-numbers 2 | |
| Line 5: | Line 5: |
| Line 8: | Line 9: |
| === Python === ==== 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 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 === ==== Introduction to Python ==== [[ScrumPy/Doc/Tutorial/PyIntro | Introduction to Python]] ==== Introduction to ScrumPy ==== [[ScrumPy/Doc/Tutorial/ScrumPyIntro | Introduction to ScrumPy]] === Python Notes === [[ScrumPy/Doc/PyNotes|Python notes]] |
| Line 19: | Line 27: |
[[SpyMDL#Overview|Overview]] [[SpyMDL#Identifiers|Identifiers]] [[SpyMDL#Reactions|Reactions]] [[SpyMDL#Directives|Directives]] |
=== Overview === [[SpyMDL#Overview|Overview]] === Identifiers === [[SpyMDL#Identifiers|Identifiers]] === Reactions === [[SpyMDL#Reactions|Reactions]] === Directives === [[SpyMDL#Directives|Directives]] |
| Line 31: | Line 38: |
| === 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 === |
==== Running ScrumPy ==== [[ScrumPy/Doc/ModEnv#RunSpy | Running ScrumPy]] ==== Loading Models ==== [[ScrumPy/Doc/ModEnv#LoadSpy | ''Loading models'']] ==== Structural Modelling ==== [[ScrumPy/Doc/StruMod | ''Structural modelling'' ]] covers computations on the stoichiometry matrix of the model, including identification of orphan metabolites and dead reactions, conservation relationships, null space analysis and elementary modes. (Latter two to be added.) ==== Linear Programming ==== [[ScrumPy/Doc/LinProg | ''Linear Programming'' ]] is for finding optimal flux patterns in a metabolic network, also known as Flux Balance Analysis. ==== Kinetic Modelling ==== [[ScrumPy/Doc/KinMod | ''Kinetic Modelling'' ]] covers dynamic models where rate functions of the models are specified. Finding and examining steady states is covered as well as simulating time courses. ''??Control analysis here or as a separate section??'' |
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.3.1. Introduction to Python
1.3.2. Introduction to ScrumPy
1.4. Python Notes
2. ScrumPy Model Description Language
2.1. Overview
2.2. Identifiers
2.3. Reactions
2.4. Directives
3. Analysis of Models With ScrumPy
3.1. The ScrumPy Modelling Environment
3.1.1. Running ScrumPy
3.1.2. Loading Models
3.1.3. Structural Modelling
''Structural modelling'' covers computations on the stoichiometry matrix of the model, including identification of orphan metabolites and dead reactions, conservation relationships, null space analysis and elementary modes. (Latter two to be added.)
3.1.4. Linear Programming
''Linear Programming'' is for finding optimal flux patterns in a metabolic network, also known as Flux Balance Analysis.
3.1.5. Kinetic Modelling
''Kinetic Modelling'' covers dynamic models where rate functions of the models are specified. Finding and examining steady states is covered as well as simulating time courses. ??Control analysis here or as a separate section??
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