-
Notifications
You must be signed in to change notification settings - Fork 13
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
True zero on axis #50
Comments
Hey @SamGG , could you please give me your |
Hi Jacob. Request updated. Best |
Hi @SamGG , I'm having trouble reproducing the plot you're seeing. It seems to be giving me a true zero on the y axis. That is, this:
gives me this: If I just set the y axis to a minimum of 0, it seems to do that appropriately:
I should mention that I am using Bioconductor's 3.8 Docker image to test this, which is at
As for the negative ticks, it's just not adding them because there is no data in that range. But you could always add explicit ticks if that were desired. As a side note, it looks like I am really having trouble reproducing your plots in the recent versions of the packages because the bins are not being re-evaluated appropriately during the re-scaling of the axis. The same plotting code above in the current which is clearly problematic and I'll be opening an issue for that soon. I'll still loop back to figure out the discrepancy over the zero on the axis as time allows. |
Hi. Thanks for looking at my question, but don't waste your time on that. I am currently updating all packages on order to get an up-to-date setup with R3.5.3. I will let you about the result. I guess I will have to switch to R3.6 and to Bioc 3.9. Best |
Sounds good, and I appreciate it. I'm actually trying to run down this scaling issue that persists in Bioc 3.9, so your post has actually been really helpful in that regard. But I think I've found the problem and I'll have it fixed soon. |
Hi,
How can I get a true zero on Y axis? Even if put I set -1000 as lower, no negative ticks are labelled.
Best.
Created on 2019-09-06 by the reprex package (v0.2.1)
The text was updated successfully, but these errors were encountered: