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
Unexpected behaviour of figsize and overlap #53
Comments
Hi there, thanks for using joypy! |
It looks like I can't reproduce it, using your example I'm able to print even with figsize (8,30) and everything works as expected. |
Thanks for taking a look. I just tried it on the command line and in IPython and indeed it works fine. It seems like this is a problem within PyCharm instead, despite using the same environment. Sorry about that.. |
No worries! |
This seems to be an issue specifically with PyCharm's SciView. For future users, you can work around this by going to "File > Settings > Python Scientific" in PyCharm and unchecking "Show plots in tool window". Incidentally, I can confirm this issue on the latest version of PyCharm without explicitly setting
No matter the value of Thanks for the heads-up! I never would have thought to try this. |
There is another possible workaround in case you do not want to deactivate SciView completely. If you are using IPython within PyCharm you can use its magic commands to switch to a different plotting backend. E.g. executing |
Hi @Sbebo,
Thanks very much for the fantastic module. I encountered a strange behaviour when trying to control
figsize
andoverlap
, which I assume is a bug. Here's a minimum code example:With these arguments the plot is created normally:
But for any height value of
figsize
that is higher than3.3
in this case, all density plots appear extremely flattened, and changing the overlap has no effect at all:I noticed this when working on some larger data, and the "threshold" of this sudden change was at a different value for the height of
figsize
Is there a way to have a larger figure but prevent this from happening?
Thanks!
The text was updated successfully, but these errors were encountered: