diff --git a/docs/guide/standard-tuning.md b/docs/guide/standard-tuning.md index d845bce..86c2832 100644 --- a/docs/guide/standard-tuning.md +++ b/docs/guide/standard-tuning.md @@ -134,6 +134,8 @@ pd.DataFrame({"rxn": tuned.rxns, "enzymes": tuned.enzymes, The output (`tunedKcats`, Python `TunedKcatsResult`) has one entry per tuned reaction: `rxns`, `rxnNames` (Python `rxn_names`), `enzymes` (joined by `;`), `oldKcat` and `newKcat` (Python `old_kcat`, `new_kcat`), and `source`, the kcat source before tuning. `ec.source` of a tuned reaction keeps its origin and detail and gets the tuning status, for example `brenda (wc=0, origin=1) | tuned=sensitivity (prior=0.05)`, where the prior is the kcat before the first tuning (see [Provenance of a kcat](../gecko4-kcat-assignment.md#provenance-of-a-kcat)). A reaction that an earlier run already tuned keeps the prior of that run. In a light ecModel, every ec row of the tuned reaction gets the status. `ec.notes` does not change. In Python, `tuned.corrections()` returns the changes as a list of `Correction` rows, ordered by fold change. +When two enzymes, or two reactions of the selected enzyme, have equal values (within a relative $10^{-9}$), the one that is first in the model is selected, so MATLAB and Python select the same kcats. + ## Lower sigma after the tuning `sensitivityTuning` multiplies a kcat by `foldChange` in each step, so the growth rate after tuning is often above the target. A kcat tuning only raises kcats, so it cannot correct this; `sigmaFitter` (Python `fit_sigma`) then selects a $\sigma$ lower than the adapter value at which the growth rate matches the target, and sets the protein pool with that value. Fit $\sigma$ only when the growth rate is above the target: when the tuning stopped below the target (see [Troubleshooting](#troubleshooting)), `sigmaFitter` would raise $\sigma$ and make the pool compensate for kcats that are too low ([Sigma and kcat tuning](protein-pool.md#sigma-and-kcat-tuning)).