You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
plt.yscale("log") gives FloatingPointError: underflow encountered in multiply #4285
I'm running an optimisation algorithm and I'm using numpy. When I plot the graph using a linear graph, everything works fine, however, in a certain scenario when I use plt.yscale("log") I get the following errors:
Errr, it's a little bit difficult because the optimisation algorithm is not just one method, it's a whole class and then you need the code for making the data. Would you like me to post these?
Errr, it's a little bit difficult because the optimisation algorithm is
not just one method, it's a whole class and then you need the code for
making the data. Would you like me to post these?
—
Reply to this email directly or view it on GitHub #4285 (comment)
.
There is still a whole lot going on in your example. Can you reproduce this with just plot and set_yscale? Is it dependent on the data you are plotting? Does this happen with other backends?
Yes, I can reproduce this with just plot and set_yscale. It is dependent on the data it seems (that's why I included the data, so that you could reproduce it) but nothing seems to be wrong with the data, if you analyse it (I believe). By other backends are you talking about using something like gtk instead of tkinter? If so, yes it does happen in that case also.
Activity
tacaswell commentedon Mar 27, 2015
In the future, please paste exceptions directly here. That link will rot.
Oddly, it is coming out of the motion notify event
tacaswell commentedon Mar 27, 2015
Can you provide a minimal amount code code that will reproduce this?
theopavlakou commentedon Mar 27, 2015
Errr, it's a little bit difficult because the optimisation algorithm is not just one method, it's a whole class and then you need the code for making the data. Would you like me to post these?
tacaswell commentedon Mar 27, 2015
No, just the mpl related code. You should be able to sort out what artists
and data trigger the issue.
On Fri, Mar 27, 2015, 12:10 theopavlakou notifications@github.com wrote:
theopavlakou commentedon Mar 27, 2015
[TAC edited for markup]
tacaswell commentedon Mar 27, 2015
If you put triple backticks around your code it will preserve the formatting.
theopavlakou commentedon Mar 27, 2015
Thanks, do you think you'll need anything else?
theopavlakou commentedon Mar 31, 2015
Has there been any progress here?
Thanks
tacaswell commentedon Mar 31, 2015
There is still a whole lot going on in your example. Can you reproduce this with just
plotandset_yscale? Is it dependent on the data you are plotting? Does this happen with other backends?theopavlakou commentedon Mar 31, 2015
Yes, I can reproduce this with just plot and set_yscale. It is dependent on the data it seems (that's why I included the data, so that you could reproduce it) but nothing seems to be wrong with the data, if you analyse it (I believe). By other backends are you talking about using something like gtk instead of tkinter? If so, yes it does happen in that case also.
tacaswell commentedon May 24, 2015
I can not reproduce this
works as expected.
petehuang commentedon Jan 10, 2017
I also cannot reproduce. @theopavlakou did you end up getting this figured out or no?
theopavlakou commentedon Jan 11, 2017
I didn't figure it out, but I did some workaround from what I remember.
tacaswell commentedon Jan 11, 2017
closing because we can not reproduce 😞
Please ping to have this re-opened if you can still reproduce it.