For the current implementation, classes are 'unknown' if they are outside of
the closure of any annotated classes at the time of owlsim initiation. This
conflates two things:
1. classes in HPO that have not yet been annotated (at the time of server
initiation)
2. classes not in the version of HPO (at the time of server initiation)
For scenario 2 we have no way of knowing if it's something that should or
shouldn't have an IC score at all (without doing something really awkward like
an on-the-fly query of the dev version of HPO).
For scenario 1, I suggest an option that propagates down from a selected node
and associates the max value for all descendant nodes that have no IC
associated. For any nodes with no IC that are not descendants, assign zero.
Original issue reported on code.google.com by cmung...@gmail.com on 28 Jul 2014 at 6:02
Original issue reported on code.google.com by
cmung...@gmail.com
on 28 Jul 2014 at 6:02