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

When you zoom in super far on the rank plot, the display breaks a bit #284

Open
fedarko opened this issue Mar 4, 2020 · 0 comments
Open
Labels
backburner Low-priority things that are still good to keep track of bug Something isn't working external issues/bugs with other libraries, frameworks, etc.; might include reproducing an issue minimally

Comments

@fedarko
Copy link
Collaborator

fedarko commented Mar 4, 2020

Observed this in the context of ALDEx2's p-values, which are included in its output statistics. Some of the lower-ranked (i.e. just straight up smaller) p-values are really tiny -- the smallest for the TCGA tutorial example is 4.35615455249617e-41.

Anyway, when you zoom in far enough (if you're a fool like me and interested in seeing what this low end of the plot looks like), the plot begins to not feel so good:

Screen Shot 2020-03-03 at 6 40 40 PM

This happens regardless of if you have the Fit bar widths to a constant plot width? thing selected or not.

In addition to these graphical glitches, the plot also becomes unresponsive (although interestingly the rest of the Qurro interface, including the sample plot, is unaffected). Resetting the plot's zoom level by double-clicking the rank plot makes the plot responsive again and removes the glitches.

I'm pretty sure this is just a Vega* problem that isn't going to be feasible (or worth spending time) to fix on our end of things. However, I'm documenting here in case this comes up in the future -- if lots of people run into this problem, it may be worth seeing if we can impose a maximum zoom level on the plot.

@fedarko fedarko added bug Something isn't working external issues/bugs with other libraries, frameworks, etc.; might include reproducing an issue minimally backburner Low-priority things that are still good to keep track of labels Mar 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backburner Low-priority things that are still good to keep track of bug Something isn't working external issues/bugs with other libraries, frameworks, etc.; might include reproducing an issue minimally
Projects
None yet
Development

No branches or pull requests

1 participant