|
Size: 2415
Comment:
|
Size: 3191
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| === Preliminaries === | |
| Line 12: | Line 13: |
| 1. This should result in two new directories: "Model" and "Analysis". Note the strict seperation of the model definition components and the analysis components. This ensures (amongst other things) that an identical analysis could be performed on any other model, as long as naming conventions for the transport steps is mainitained. | 1. This should result in two new directories: "Model" and "Analysis". Note the strict seperation of the model definition components and the analysis components. This ensures (amongst other things) that an identical analysis could be performed on any other model, as long as naming conventions for the trans port steps is mainitained. |
| Line 18: | Line 19: |
| 1. Briefly familiarise yourself with the contents of the model, and make sure you can identify the various transport steps. | 1. Briefly familiarise yourself with the contents of the model, and make sure you can identify the various transport steps.Note that some of these are commented out reflecting what we may or may not expect to be imported from or exported to, the media. |
| Line 21: | Line 22: |
Having done all this we are now in a position to start analysing the model. The python code you need can be found in the "!O2LimScan" module in the Analysis directory. You can open this from the "File/Open" menu item. All the work is done with the "!O2Scan" function, by now you should be able to interpret ''what'' this function is doing (don't worry about ''how'' it does it). Note that the module cannot be imported until the model is loaded (steps 1--7) above. Ask a demonstrator if you want to know why this should be the case. === Analysis === 1. Import the "!O2LimScan" module: {{{ >>> import O2LimScan}}} |
Practical 7
The effect of varying oxygen availabilty on Geobacillus
In this practical we will be investigating the the potential effects of limiting oxygen availability to a model of the organism Geobacillus thermoglucosidasius described here. In order to do this, we will be using the constraint scanning approach described in lecture 7. Geobacillus is a facultative aerobe this has been demonstrated experimentally and in the paper linked above we investigated aerobic and anaerobic metabolism. What we did not investigate is the situation in which oxygen is reduced but not completely absent, so, as well as being a new practical, this is also a new investigation - results generated here will be genuinely new - no-one will ever have seen them before!
In order to perform the analysis we will be introducing a new class of object from ScrumPy, the DataSet. As the name implies, it's purpose is to store and maniplulate data either generated from models, from external source, or from both. It has many of the same properties of a matrix, but in addition is capable of simple graph plotting and statistical analysis. In this exercise it will be used to store a set of lp solutions generated over a range of constraints imposed on the oxygen uptake rate.
Preliminaries
Download the file P7.tgz into the area in whch you have been using for your other practicals.
- This is a compressed archive file and you will need to extract the files before they can be used:
$ tar -zxf P7.tgz
- This should result in two new directories: "Model" and "Analysis". Note the strict seperation of the model definition components and the analysis components. This ensures (amongst other things) that an identical analysis could be performed on any other model, as long as naming conventions for the trans port steps is mainitained.
Change directory to the Analysis directory: $ cd Analysis
Start ScrumPy and load the model "MetaGeo.spy" located in the Model directory.
- Briefly familiarise yourself with the contents of the model, and make sure you can identify the various transport steps.Note that some of these are commented out reflecting what we may or may not expect to be imported from or exported to, the media.
- Having several windows open for one model can be inconvenient, the "!ScrumPy/Hide children" menu option will minimise all except for the top level module window.
Having done all this we are now in a position to start analysing the model. The python code you need can be found in the "O2LimScan" module in the Analysis directory. You can open this from the "File/Open" menu item. All the work is done with the "O2Scan" function, by now you should be able to interpret what this function is doing (don't worry about how it does it). Note that the module cannot be imported until the model is loaded (steps 1--7) above. Ask a demonstrator if you want to know why this should be the case.
Analysis
Import the "O2LimScan" module: >>> import O2LimScan