-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: update general kcat database #157
Comments
I'm not totally sure on the scope of the issue: is it about creating a local kcat file or about how that file is used by GECKO? Perhaps it would be easier to discuss verbally and write up conclusions. |
Both about the actual file and how it is used. But it sounds like GotEnzymes will also be able to provide such a file (did not know this when opening this issue), so this issue will most likely be addressed when GECKO and GotEnzymes can work together. |
Does not strictly have to be JSON, but it should be flat-text so that it is diff-able. |
For reference, this is what GotEnzymes output looks like (showing only the first 28 lines here):
|
Just a note, the above is without having exposed a purpose-built API. Therefore, my recommendation would be to see that as a foundation to build a more compact and potentially more usable response. |
Here is the link to the promised API https://metabolicatlas.org/api/v2/#/GotEnzymes |
Description of the new feature:
By repurposing some of the DLKcat code, construct a JSON file similar as in DLKcat. This JSON contains kcat values from BRENDA and SABIO-RK databases, and could be run every 6-12 months.
In contrast to the current DLKcat code, some filtering steps should be skipped, to (a) keep specific activities; (b) keep cases where no amino acid sequence could be assigned to. By doing so, this kcat database can be used in GECKO's fuzzy matching approach. The file thereby replaces the
max_Kcat
andmax_SA
files that GECKO currently uses.This JSON file should be loaded into MATLAB, to be used in GECKO fuzzy matching (which is refactored in a separate Issue).
However, if the purpose of this file is only used for GECKO's fuzzy matching, then we might as well stick with the existing
max_Kcat
andmax_SA
files? Let's keep this Issue on hold for now.The text was updated successfully, but these errors were encountered: