Repository navigation
sensitivity_tuning: break ties by the order of the model - #97
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
sensitivity_tuningselects the enzyme with the largest usage flux and, of the reactions that consume it, the one with the largest consumption. When two enzymes or two reactions have equal values (within a relative 1e-9), the first in the model is selected, as insensitivityTuning(CompMetEng/GECKO#37).The reactions of the enzyme were read from an unordered set, so a tie could select another reaction than MATLAB. On the
full_ecModeltutorial, two reactions of P05375 consume the same amount of the enzyme: MATLAB tunedr_2500and Python tunedr_2508. Both now tuner_2500, and the tuned kcats of the two toolboxes are the same.