Closed RichardBruskiewich closed 11 months ago
Sigh... Alas, I'm scratching my head tonight. I wrote a unit test assuming the correct value, and it seems to work. I'm wondering if there is a stale dependency in contexts where the error is manifested. I'll take a closer look at this over the next day or so.
Ah... this was actually a Biolink Model 3.5.2 bug, fixed in 3.5.3... I was puzzled for the longest while about this, LOL.
A curious defect was noticed in qualifier value
range
slot_usage
access in somebiolink:Association
subclasses.The specific anomaly noted from accessing the following in the Biolink class:
Note that the object aspect qualifier range recorded in the model is
GeneOrGeneProductOrChemicalEntityAspectEnum
.However, when using an toolkit class instance 'bmt' (e.g. from release 3.5.2)
one gets the following
which seems to be the value of the
range
of the precedingobject part qualifier
entry, not the expectedGeneOrGeneProductOrChemicalEntityAspectEnum
range enum forobject aspect qualifier
. This, of course, causes reasoner validation false positive errors. Here's one known example of this:which has an matches to
chemical affects gene association
but fails to be validated insidebmt.validate_qualifier()
(in code similar to the above).