Closed jrleeman closed 4 years ago
Given the discussion that happened around the change for matplotlib (matplotlib/matplotlib#7460), I think we're on the hook for fixing this on our end.
Should we be manually setting the ylimits anyway?
Probably not. Matplotlib 2.0 improved default limits anyway (things like margins)
Might be worth adding a check to the Matplotlib code that ensures the auto-limits never blow up. What sort of data are you feeding in that has this issue?
@tacaswell In this case we have live data that (apparently) was completely missing. This lead us to send NaN
s to set xlim. Before matplotlib would give us a useless panel, now we get an error--the more I think about this, I'm not sad at the new behavior.
Let's move to canned data (case study or IEM) for now as we don't have a reliable surface feed from Unidata currently.
Looks like the METAR data is giving us all NaN for pressure data and that's causing the y-limit setting to go sideways. Hazards of using "live" data I suppose. Maybe we should point the gallery at the Irma datasets? That would be interesting and consistent while still showing how to access data from THREDDS.
This looks to be a consequence of a regression in mpl https://github.com/matplotlib/matplotlib/issues/9361