-
Notifications
You must be signed in to change notification settings - Fork 40
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
migrate CHEBI terms to pH 7.3 subset #23568
Comments
I think this was the case with the previous version of the file, so I'm not sure why these weren't flagged before. |
Hi @balhoff CHEBI:26116 phytochromobilin and CHEBI:33569 noradrenaline were not in the CHEBI imports; can they be removed from the other file where this data is coming from, to avoid we use these by mistake in the future? Thanks, Pascale |
For kaempferol 3-O-beta-D-glucoside I dont know how to find the corresponding pH 7.3 - @kaxelsen can you help ? Thanks, Pascale |
Go to www.rhea-db.org and search for the CHEBI ID of the compound you have (here CHEBI:30200) or for the compound name (kaempferol 3-O-beta-D-glucoside) |
Possible scaling and mapping issue (and possibly also a digression here) - my anecdotal sense, from working to align hundreds of Reactome reactions with their pH 7.3 RHEA counterparts, is that the correctly charged ChEBI instance often (maybe 10% of the time) lacks any comment to indicate that it is the predominant microspecies at pH 7.3. I can indeed check the various ChEBI instances to identify the one that is associated with RHEA reactions but that is slow. It would make our checking and new-curation work easier and more reliable if this information were reliably present in ChEBI entries. |
merge after CHEBI import has ran fixes #23568
@pgaudet we've still got a GO term phytochromobilin metabolic process referencing phytochromobilin. |
I'm trying to update the pH 7.3 mapping list in #23567, but the update reveals some terms used in GO that aren't currently in the pH 7.3 list, and don't have mappings there:
The text was updated successfully, but these errors were encountered: