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
By default, the subsumer matrix contains all subsumers, and thus the semantic similarity metrics computed with it uses the entire superclass hierarchy.
For phenotype dependency and mutual exclusivity evaluation, it is sometimes useful to consider similarity only for a certain part of the superclass hierarchy. Specifically, it should be possible to consider only the parthood hierarchy.
The text was updated successfully, but these errors were encountered:
One possibility to accomplish this on the client (RPhenoscape) side would be to remove (filter) from the subsumer matrix those subsumers that aren't in the desired hierarchy. If we can identify terms in the desired hierarchy (or their complement(s)) by, for example, a subclass query, then this would be an effective filter.
Note that filtering the subsumer matrix in this way assumes that rows in the matrix are independent, This should be true for Jaccard, but should be checked when weights are not in {0, 1}.
I think if we wanted to accomplish this it would have to be through a feature of the KB API (parameter allowing specification of allowable relationships for subsumption paths; or a named corpus defined as using only certain relationships for the transitive closure).
@balhoff can you remind us whether there's any work underway for supporting this, and whether this should be available before the TraitFest event?
By default, the subsumer matrix contains all subsumers, and thus the semantic similarity metrics computed with it uses the entire superclass hierarchy.
For phenotype dependency and mutual exclusivity evaluation, it is sometimes useful to consider similarity only for a certain part of the superclass hierarchy. Specifically, it should be possible to consider only the parthood hierarchy.
The text was updated successfully, but these errors were encountered: