-
Notifications
You must be signed in to change notification settings - Fork 9
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
WF Lookup: Gene - related_to - ChemicalSubstance (CHEBI:45783) #115
Comments
Isn't
For some reason, OpenPredict is responding to the gene node with diseases. |
@CaseyTa This question has come up with ARAGORN/COHD integration, too. "Chemical substance" is officially an alias of "small molecule" in the biolink model: https://github.com/biolink/biolink-model/blob/2.1.0/biolink-model.yaml#L7250. Does that mean that we should continue to accept it and treat it as synonymous with "small molecule"? Or do we ignore those aliases? Regardless, it would be convenient it servers could simply ignore categories that they do not recognize/support, rather than throwing an error. For example, it would be nice if nodes with |
@patrickkwang, we're validating the input categories using the Biolink Model Toolkit, so bmt is telling us that
If this issue is coming up often enough, we can make that change in COHD. Does this arise because we're trying to run a lot of old queries that were previously created under older Biolink versions? Or is this coming from different services running different versions of Biolink which support different categories? |
BTE returns the expected results with either |
@sierra-moxon is this something BMT should help with? ^^ |
My mistake, I meant to change this after the last standup. I've resubmitted with SmallMolecule |
Same issue with the SmallMolecule vs ChemicalSubstance for us Edit: thanks Mark, that ones works for us. |
The error has been fixed in ARAX (thanks @finnagin ) |
Query: workflow2.json
PK: bd5bba27-3d28-425f-a05d-6ff802833c4a (deprecated a0b7182c-d4fc-4d47-87b0-d84ac3861e1c)
Control:
Results Tracking Sheet
The text was updated successfully, but these errors were encountered: