Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Synonymization/generality problems #62

Open
dkoslicki opened this issue Jun 27, 2024 · 10 comments
Open

Synonymization/generality problems #62

dkoslicki opened this issue Jun 27, 2024 · 10 comments
Labels
Too General The asset is too general to be a good test

Comments

@dkoslicki
Copy link
Member

For test 7 asset 79, the ARAX result has progesterone as result 2 of 103. But the asset asks for progestin (the synthetic version of progesterone, iirc).

For test 12, asset 309, pegfilgrastim is asked for, but any filgrastim or G-CSF should be accepted.

For test 13, asset 362, the goal is to get ACE inhibitors and ARAX returns Angiotensin-converting enzyme inhibitors (i.e. the full name)

For test case 15, asset 318, Ivacaftor is asked for and ARAX returns Ivacaftor / texacaftor and ivacaftor /lumacaftor as results 2 and 3. Do we want to do the testing post-conflation?

Test 24, asset 396 Butyrate derivatives is asked for, but butyrate and butyric acid aren't accepted as answers.

Test 29, asset 504, thrombin is asked for, but alpha-thrombin is not accepted as an answer (similarly for test 30, asset 595)

Test 35 asset 665, KRASG12D inhibitor MRTX1133 is asked for, but MRTX1133 (CHEMBL.COMPOUND:CHEMBL5081048) is not accepted

@dkoslicki
Copy link
Member Author

Similarly Test 9 asset 623, Rabeprazole is asked for, but Rabeprazole sodium is not accepted as correct. Again with the post/pre-conflation issue

@colleenXu
Copy link

colleenXu commented Jun 28, 2024

Note this issue for Asset 362 / ACE inhibitors: #76.

There's a little more going on with this test. I also link it to the "too general" issue you opened.

@colleenXu
Copy link

colleenXu commented Jun 28, 2024

We noted the same issues for some tests:

  • asset 396 Butyrate Derivatives UMLS:C0581820: BTE returned entities that seem related like butyric acid CHEBI:30772, D-alpha-aminobutyric acid CHEBI:28797, and phenylbutyrate CHEBI:41500
  • asset 665: there's another NodeNorm entity for MRTX-1133: UNII:DU32DM9CHD. I got that ID from Wikipedia

@colleenXu
Copy link

colleenXu commented Jul 4, 2024

Here's some more tests with the same kind of problem (I'm closing their separate issues and moving the info here):

asset 32 Lactase `CHEMBL.COMPOUND:CHEMBL2108505`

(old issue)

  • the NodeNorm entry for this ID seems odd: it has no other equivalent IDs (Dev NodeNorm).
  • There are other lactase entities with more equivalent IDs that show up in BTE's results with higher scores/ranks: MESH:D043322 (ChemicalEntity) and UMLS:C0083183 (Protein)
  • I've noted before that tools tended to fail this test. I haven't done this comparison lately though

asset 355 fosinopril `PUBCHEM.COMPOUND:55891`

PUBCHEM.COMPOUND:55891
(old issue)

asset 397 hemin `PUBCHEM.COMPOUND:26945`

hemin
(old issue)

  • the NodeNorm labels for this entity's IDs are "protoheme", not hemin
  • Instead, I see "hemin" in the NodeNorm conflated-ID labels for hematin PUBCHEM.COMPOUND:455658. BTE consistently has hematin in its result set (often too low for a TopAnswer, but still).
  • It's not clear to me if the conflation of hematin and hemin in NodeNorm is okay or not. Wikipedia notes the difference in ions and also has hemin IDs that map to other NodeNorm entities
  • think all tools have been consistently failing this test, which may be in part due to the answer ID choice: Tests that no one passed #69

asset 595 thrombin/F2 `UMLS:C0040018`

(old issue)

@maximusunc
Copy link
Collaborator

So I think this gets to a root question: The Test is asking for a superclass identifier (in most cases) and an ARA gives back a subclass (more specific). Is the ARA expected to also return the superclass? If not, why not?

@maximusunc maximusunc added the Too General The asset is too general to be a good test label Jul 12, 2024
@dkoslicki
Copy link
Member Author

From the subclass reasoning perspective (if a general concept is asked for, also return more specific instances), my impression was that precision is preferred to generality. But I guess it hasn't really been codified one way or another. My $0.02 is that a subclass being should "count" for the test asking for a superclass. Open to other opinions though

@maximusunc
Copy link
Collaborator

I agree that more specific instances are preferred, but does that mean that the general concept that was asked for should not be returned?

If we were to support subclass answers in the tests, how exactly would that work? Is there an easy way to determine if something is a subclass of the expected output?

@maximusunc
Copy link
Collaborator

This general topic will be discussed during the testing session of the upcoming Relay.

@sandrine-muller-research

wrt "wrong output IDs": I guess not all tests are from me but the purpose of the test assets is to test the UI so when the UI returns something wrong (e.g. superclasses) the ID given by the UI is reported.

wrt synonymization/generalization:

  • since the testing is testing the UI, the testing is done "post conflation" if the creative query returned by ARA does the conflation. At least that's how I made the tests.
  • When a super set family was outputed the question I was asking myself was "are all BioLink entities in that superclass" passing/failing. If not then it is "too general" and is a failure.
  • for the thrombin case: I have not idea why alpha-thrombin is not accepted because I did not write a fail test for that one.

@colleenXu
Copy link

Asset 79 also has this issue. It's been running in sprints 5-6.
The answer is "progestin" MESH:D011372, but this is a drug class with ~ 60 individual chemicals. Some of those individual chemicals (including progesterone itself) are high-ranking ARA results and should probably pass...

No one has been passing this test is sprints 5-6 (also noted previously).

This test is also flagged in #93

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Too General The asset is too general to be a good test
Projects
None yet
Development

No branches or pull requests

4 participants