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

Translator Demo Workflow B - Exploring Agent queries #244

Closed
karafecho opened this issue Aug 6, 2021 · 4 comments
Closed

Translator Demo Workflow B - Exploring Agent queries #244

karafecho opened this issue Aug 6, 2021 · 4 comments

Comments

@karafecho
Copy link

karafecho commented Aug 6, 2021

This issue is to kindly request that Exploring Agent tests Workflow B. Here is an example TRAPI query that runs when sent through the ARS, but the only ARA that returns responses is ARAX. The ARS issue is apparently related to time-out errors that will be resolved with the release of TRAPI 1.2 and support for asynchronous queries, but that will not happen until early September. Thus, Hao and I would like to test direct ARA queries, and we are requesting your help. Note that we are also testing direct ARA queries using multihop.py, but BTE tests would be helpful, as multihop.py doesn't support sophisticated features like ranking, etc.

The README file provides an overview of the workflow, including suggested input CURIES. Note that the first predicate will be changed from biolink:correlated_with to biolink:has_real_world_evidence_of_association_with, but I will be sure to alert you to this change after clinical KPs implement the new predicate.

We are also testing query constraints, such as replacing biolink:related_to with biolink:interacts_with and biolink:Gene with biolink:BiologicalProcessOrPathway. Other options are welcome. Andrew and I discussed alternative workflow paths, too, so that's another option.

We realize that you all are extremely busy, but we would greatly appreciate a few quick tests. Please feel free to reach out to me or Hao Xu with questions.

@andrewsu
Copy link
Member

andrewsu commented Aug 6, 2021

@karafecho I was assuming that all of Workflow B was dependent on either ICEES or COHD being hooked up, but I realize now that I never confirmed that assumption. Am I right?

If yes, then completion of workflow B queries is dependent on us solving #213 and/or #223. #213 is being actively worked on now...

@karafecho
Copy link
Author

You are partially correct, Andrew. The first hop is intended to target clinical KPs, but because we are currently using the predicate biolink:correlated_with, it only hits COHD and ICEES. However, that will change with adoption of the new Biolink 2.2.1 predicate biolink:has_real_world_evidence_of_association_with, in which case the first hop should return results from COHD, ICEES, Multi-omics EHR Risk Provider, and CHP. The clinical KPs have not yet implemented this predicate, but I will be sure to alert you after they have.

And yes, I realize that you all are actively working on the issues you note. Just thought I'd post this ticket as a possible task to accomplish after those issues have been resolved.

Many thanks!

@karafecho
Copy link
Author

BTW, I've been working with the ICEES+ CAM KP team to explore the alternative workflow that you, Andrew, suggested. Specifically, we've been exploring biolink:Gene -> biolink:GeneOrGeneProduct (up/downstream genes) and biolink:Gene -> biolink:BiologicalProcessOrActivity connections, beginning with the five genes that are known/suspected to be causally related to DILI (listed in the README file). While these queries address a different question, I think we may be able to use them to provide additional support for the overall workflow and associated narrative. Just an FYI...

@andrewsu
Copy link
Member

completed use case -- closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants