-
Notifications
You must be signed in to change notification settings - Fork 0
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
Inferred Edge Should Match Fully Qualified Query Graph Edge - MVP2 #855
Comments
@sierra-moxon i'm not sure if any one thing is actually wrong here, but do you have guidance? |
I believe these are all the same result and need to be merged. How do we get to a merge?
In the back of my mind, it seems a little odd that we have inferred edges that seem to be just reiterating the lookup edges. Am I misunderstanding these results? |
i believe ARS treats these edges as unique and doesnt merge them but defer to @MarkDWilliams @gprice1129 |
The predicate variation (especially |
After reviewing the pk again in the UI the edges in the first screenshot are now being properly compressed |
from TAQA: then we need the UI to pass the qualified_predicate to the ARs. Sui: too many predicates saying the same thing, eg "chemical affects expression of x" - gets mapped differently in the UI? In two-hop answers, we have down and up-regulated (can mean expression, activity, etc), a-upregulates-b- upregulates-c) |
retested on CI today, far fewer predicates, more merging. did not spend too long evaluating results but the original issue to me, is fixed. |
this is in prod |
I dont fully understand why the predicates differ so frequently, when I read them in the UI, I'm not sure I understand how substantially different to the reasoned answer
"Tamoxifen Causes Decreased Activity Or Abundance Of Arid1a" vs "Tamoxifen Affects Decreased Activity Or Abundance Of Arid1a"
then the more general "Tamoxifen Affects Arid1a"
https://ui.test.transltr.io/main/results?l=ARID1A%20(Human)&i=NCBIGene:8289&t=2&r=0&q=1d650508-5292-4faf-a52c-21954c89fb36
When I look at it in the ARAX GUI
ARAGORN
The support graph of the prediction - looks to be a TMKP lookup
ARAX
BTE
all but one of these SG edges are TMKP
Unsecret
The text was updated successfully, but these errors were encountered: