Closed edkerk closed 5 years ago
Ok, the drawback with this formalism is that the readability is much better with the current form. Is it an option to improve the GECKO-parser?
This is model specific, and certain GPRs should be manually inspected to ensure that they make sense. Regardless, I'll include swapping the GPR rules in the ecScoGEM script.
This is included in the preprocessModel
script in the GECKO submodule.
Please provide relevant information below:
Description of the issue:
There are various reactions with complex GPR relationships (nested 'and' and 'or' relationships), which increase the risk of mistakes. For instance, Gecko uses GPR rules to separate isoenzymes, such that correct GPR rules are crucial.
Expected feature/value/output:
If a current relationship is potentially written as:
ideally, all possible combinations should be written as:
Previously, the following RAVEN code was used to fix some of the reactions in Sco4:
Reproducing these results:
In RAVEN, problematic grRules (=GPR) can be identified using
standardizeGrRules
To do:
I hereby confirm that:
master
branch of the repository