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
This may be related to #198 (which states the behavior for upper ontology terms, which ought to subsume all homologs, hence the surprise there). This case differs in two ways:
The entity query term is a pre-generated post-composition.
The expression uses a UBERON term that conceivably does have homologs.
However, even though the term conceivably has homologs, it's much less clear why only its homologs have matching annotations.
This may be related to #198 (which states the behavior for upper ontology terms, which ought to subsume all homologs, hence the surprise there). This case differs in two ways:
However, even though the term conceivably has homologs, it's much less clear why only its homologs have matching annotations.
The example is "has_part some paired fin skeleton" (http://purl.org/phenoscape/expression?value=%3Chttp%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FBFO_0000051%3E+some+%3Chttp%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FUBERON_0010713%3E):
without homologs (gives zero count), with historical homologs:
gives a count of 3546.
The text was updated successfully, but these errors were encountered: