Closed kgoebber closed 5 years ago
For some reason, DNR has not had radiosonde data posted since 12 UTC 29 Mary 2019...can't find any messages for why this is the case. I'll rerun once DNR is available again as one of the examples relies on "current" DNR data.
@kgoebber I don't see where you're pulling in current data - can you point me to what you mean by your previous comment? Other than my suggested change, this looks like a great example!
Ah, the DNR comment wasn't for this particular PR, it was a comment on why the build was failing...still don't know why Denver was not reporting any upper-air observations for a while, but alas, they are again.
Yes, I have been seeing those errors. That is new with the latest versions of Pint. I'm open to making the change (although it will be present in a lot of the examples beyond this one). It seems a bit extra to put in all of the ".m" just to get rid of a warning, when it will work with the units since they are stripped in the background. I like that there is a warning to let you know that they have been stripped, but since it is largely happening at the point of figure creation is doesn't really matter to the end user. @dopplershift thoughts on the stripping of units piece?
50/50. Maybe a slight lean to leaving it as is (no .m
) since it's being stripped by matplotlib so we could technically "fix" it there.
That all makes sense. I assumed that was the Pint update since I hadn't seen those errors before and have always used the same syntax that you have here. Looks good to go then!
Another example for a simple upper-level map analysis. This one is for 850-hPa geopotential heights and temperature.