-
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
Promiscuous compounds #617
Comments
Hydrogen |
Needs investigation to determine amount and cause? Perhaps this would be something good to define some tests around. |
Additional compounds that are frequently returned as results for various queries:
|
adding "needs review" so that we can assign a volunteer or group of volunteers to design tests and/or otherwise determine next steps. |
from TAQA: what we need to do:
is it always one ARA that is returning one of these, or a set of these? is it from one source or many sources? (this could change what we want to do about it). is there evidence for each of these or are they in the middle of hops -- highly connected nodes, etc... do ARAs check the inverse? do we also check what this drug can treat vs. the other way - it might affect the results that come back. drugs coming back on this thing, but look for the things by drug to see if there are still results. |
I ran 37 diseases through what may treat. Attempted to have a diversity of disease types(blindness, constipation, AD, webbed toes, PTSD, etc.). See table below with diseases and PKs. I included a breakout by ARA and included the number of responses that they gave 1 or more answers for. Not sure how to count things if they did not provide any results. For the screenshot below: I don't know if this is bad or good or neither? However, if you are a diabetic on metformin being given cyclosporin to suppress your immune system while controlling your seizures with valproic acid, you may be immortal! Here are the diseases and the PKs
|
I did not do this for MVP2. Do we need that? I can redo this process for that as well, but will wait for feedback on what mistakes I made here. |
I think those nodes have a high degree (or perhaps a high first degree). Perhaps the node "cardinal" (not sure it was the correct naming, sorry I have a blank) that @MarkDWilliams created could help? They are ways to correct for the node degree effects but I do not think it could be done easily. At list inform the user about the "connectivity" of the node or of its close neighbors could be helpful? (have an icon of something that says that is is potentially a false positive). |
from TAQA:
|
Not at all arguing against the fact that this really should be addressed, but is this an actual deployment showstopper? I ask since such a pervasive issue (but subtle, as these "promiscuous" results are mixed in with better quality ones), and one that many ARAs are experiencing leads me to believe that this is something that will not have a quick fix. I.e instead of a showstopper, what about making it one of the sprint priorities? |
I agree with your analysis. I put this tag so it gets a chance to be discussed at TAQA to choose collectively a proper action (one of the sprints or next phase? ) I am happy to remove showstopper |
Scrutinizing a bit more the results (first 5 pages of 50 compounds or so) for several queries (~10), I have started to see some ChemicalEntities that seem to be promiscuous (coming as an answer for a lot of queries) :
sirolimus
valproic acid
gadolinium
curcumin
Ergocalciferol
Ozone
Nicotine
Tacrolimus
Mercury
propofol
Potassium chloride
aspirin
tramadol
propofol
Sodium chloride
Calcium
codeine
Methylene blue
Propranolol
Ethanol
Oxygen
Analgesics
Ibuprofen
They seem to come as results because they are linked to a lot of diseases and score up too high to my taste. I wonder if @MarkDWilliams 's cardinality could help lower them down?
The text was updated successfully, but these errors were encountered: