Files in the data folder#
The data folder of a GECKO 4 project holds the input data of the reconstruction, the kcat source files and the files of the kcat predictors. GECKO (MATLAB) and geckopy (Python) read and write the same files, so a data folder made with one toolbox is used by the other. Getting started describes the layout of a project and Project format 4 the folders outside data.
Databases and gene identifiers#
File |
Content |
Functions |
Page |
|---|---|---|---|
|
UniProt data for the organism: protein identifier, gene identifier, EC number, MW and sequence. |
|
|
|
KEGG data for the organism: UniProt protein ID, gene, KEGG gene ID, EC number, MW, pathway and sequence. |
|
|
|
Conversion table for models whose gene identifiers match no UniProt field. A header row, then the gene identifier and the UniProt identifier. A gene that is not listed keeps its identifier in geckopy and gets an empty UniProt identifier in MATLAB. Written by the user |
|
|
|
Optional. Reaction identifiers in the first column and reaction names, for reference, in the second. These reactions lose their gene association in |
||
|
Enzyme complex information from the Complex Portal |
|
|
|
SMILES for the metabolites of the ecModel, a cache of the PubChem queries |
|
Kcat source files and BRENDA data#
Path |
Content |
Functions |
Page |
|---|---|---|---|
|
One kcat source file per source: |
|
|
|
Optional. The BRENDA files of the project: |
|
|
|
Curated kcats in the format of GECKO 3, with the columns |
|
|
|
KEGG phylogenetic distances, which geckopy uses to match kcats of other organisms. Downloaded when it is missing. GECKO reads the corresponding file of RAVEN |
Predictor files#
File |
Content |
Functions |
Page |
|---|---|---|---|
|
Input of DLKcat and, after a run, its output |
|
|
|
The number of reactions that the last DLKcat run covered, when it covered a subset of the reactions |
|
|
|
Optional project copies of the lists of metabolites that are left out of the DLKcat and OKP input: names with SMILES, and pairs of currency metabolites. Without them, the files of the toolbox are used |
||
|
Input of an OpenKineticsPredictor job |
|
|
|
The job and the result of one OKP method |
|
|
|
The job and the result of a job that |
||
|
The API key of OpenKineticsPredictor, an alternative to the argument |
Proteomics, flux data and tuning data#
File |
Content |
Functions |
Page |
|---|---|---|---|
|
Protein abundance data from PaxDB for the f factor (the mass fraction of proteins accounted for in the ecModel). Header lines start with |
|
|
|
Measured protein levels (mg protein/gDCW) from one or more experiments: UniProt identifiers in the first column, protein levels from individual replicates in each subsequent column |
|
|
|
Experimental growth rate, protein content and carbon-source uptake, that constrain the ecModel during proteomics integration and in flux-variability comparisons. Exchange fluxes in mmol/gDCWh; uptake negative, excretion positive. Not required for the initial reconstruction |
|
|
|
Optional data of the kcat tuning with CMA-ES: flux data, maximum growth rates and exchange reactions with zero flux |
Spontaneous reactions#
The file that [spontaneous] file in model_adapter.toml names is a TSV with a header row. It lists reaction identifiers in the first column and, optionally, a second column in which 1 or true marks the spontaneous reactions. The path is relative to the project folder and the file name is free. See Model adapter parameters.
See also#
Getting started, where a project's
datafolder is created.Model adapter parameters, the parameters of
model_adapter.toml.Project format 4, the folder layout of a GECKO 4 project.