You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some of the ontologies used by present node expansion do not use purely the prefix for which they are named, which results in rare cases where BTE will fail a query with TypeError as the subclass edge-sourcing code is unable to handle this situation. Further, the subclassing code uses a base assumption that the ontology source will line up with the prefix, which clearly is not correct for these cases.
We need to figure out a better solution for subclass edge sourcing that avoids running into this problem.
The following (unfortunately long) query can replicate the error:
Looks like it's just these two that are non-monoprefix.
Note: both contain mappings where the parent is not HP or MONDO, so we can't just check the original vs expanded to reason about which file it came from.
I'm not sure how the descendant-relationships were decided / parsed, and whether it's valid for all those other ontologies to be included.
I agree with the discussion in the lab slack thread that for now, we could remove the non-mondo IDs from the mondo file and the non-hp IDs from the hp file...
tokebe
added
On CI
Related changes are deployed to CI server
On Test
Related changes are deployed to Test server
and removed
On CI
Related changes are deployed to CI server
labels
Aug 16, 2023
Some of the ontologies used by present node expansion do not use purely the prefix for which they are named, which results in rare cases where BTE will fail a query with TypeError as the subclass edge-sourcing code is unable to handle this situation. Further, the subclassing code uses a base assumption that the ontology source will line up with the prefix, which clearly is not correct for these cases.
We need to figure out a better solution for subclass edge sourcing that avoids running into this problem.
The following (unfortunately long) query can replicate the error:
Tagging @colleenXu @ericz1803
The text was updated successfully, but these errors were encountered: