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
enhancement of unmatched phenotypes #130
Comments
See #173 for more updates. |
I think this is necessary too. Consider the following case - There are two models, one which matches the given HP terms well and another with no match at all. The second simply vanishes, but it would, as Harry said be very useful to see that there are infact no decent matches. Hiding it is certainly unexpected behaviour. I supose you're doing something else now, but this would be a very good thing to implement if you're still working on phenogrid.
|
@julesjacobsen agreed. We've not found any particularly compelling approach to this problem. Let's try to give it some thoughts. Suggestions welcome. |
My expectation would be that there is simply a column containing the label, info and score, but with no coloured squares on the grid. |
@julesjacobsen, you mean a column for the model with no labels, right? This seems possible, but it's not a great use of screen space. Also, if there are no matches, the score should be very low (if not zero), right? |
Ok. @julesjacobsen, can we get release now and put this on the short list of priority enhancements? |
Sure, go for it. |
thanks! |
@harryhoch can we close this issue? I think Zhou fixed this in this here: #173. He lists the unmatched phenotypes below the grid. |
The unmatched phenotypes can currently be seen when clicked, however, so far users haven't actually been drawn to click there, and have been confused by it. I think the desired behavior is still to have the unmatched things show up on the left with the others. Perhaps with a horizontal line delineating the things unmatched in the query group versus the matched group. A list is better than nothing but it is not as useful, nor as obvious as simply including in the grid from the start. |
I think I understand. What is the proposed behavior? Should I add rows representing the unmatched phenotypes to the bottom of the phenogrid? |
@jmcmurry, I think your first response is reasonable, so long as it is collapsiable. @cborromeo, how hard would this be to do? |
I have a question about the first screenshot. Where does hyperglycemia and polyphagia appear if they are matched in some cases but unmatched in others? Is the rule if there is one or more matches then the phenotype appears above the "Unmatched Phenotypes"? Or will all phenotypes be repeated? Once above the Unmatched Phenotypes and once below (assuming all the phenotypes will be both matched and unmatched? |
I suggest that only those phenotypes that are truly unmatched for any model should go below the line. Others can have a blank square above. |
@jmcmurry are you ok with @harryhoch 's suggestion? If so, I'll figure out how to get it to work. |
@jmcmurry what goes above the horizontal line? I don't quite understand? Why not just have only the things that are completely unmatched go below the line? |
Just so we don't confuse unmatched query phenotypes with unmatched target phenotypes, that's all. If it confuses rather than clarifies, happy to have them all below the line. Did the part about having the query item be a column make sense to you? |
actually, no - I didn't quite get that. Let me think about unmatched target phenotypes. |
@jmcmurry @harryhoch I spoke to Zhou about this. The execution steps for unmatched phenotypes (in this case query phenotypes) are as follows:
I think there is a need for the simsearch webservice to return two lists: a) the unmatched query items (the list should include the id, label, and data type) |
@cborromeo, greed. we need a monarch-app call to batch these up, at the very least , and possibly an owlsim call. Please enter an issue on monarch-app.... |
Hi |
We should have the ability to see the unmatched phenotypes for the profile on the left list, as well as for any column. Basically, if you were interested in comparing a patient against a particular model (as in UDPICS), you want to be able to see what phenotypes do not match against the two, almost as much as those that do.
@harryhoch I wonder if we can think of an approach that is consistent for how to display these regardless if it is on the left list or in a matched column.
This will also be very helpful in particular for debugging ZP matches, don't you think? @cmungall @nlwashington
monarch-initiative/monarch-app#495 for more detail
The text was updated successfully, but these errors were encountered: