Ryan May

icon indicating a website link http://dopplershift.github.io icon indicating an email [email protected]

icon company UCAR/@Unidata icon location Loveland, Colorado, USA icon location Software Engineer at @unidata and lead developer for MetPy ⛈. Trying to help make it easier for scientists and especially meteorologists to use Python 🐍

Results 784 comments of Ryan May

Dask delayed operations and Pint Quantity

So you're saying `.to()` forces breaks the parallelism but `units.convert()` doesn't?

Dask delayed operations and Pint Quantity

That seems about right. I think overall full support will be something we look at beyond the GEMPAK work.

Use Pint Application Registry

@jthielen What do you think of this?

Use Pint Application Registry

@jthielen Does `pint.Quantity` *always* refer to the current set registry?

Use Pint Application Registry

Up to this point, we've been able to limit "direct" use of `pint` to `metpy.units`, so I don't love that this is bleeding more uses of `import pint` across the...

Use Pint Application Registry

I don't think having it direct is horrible, but I think it's marginally better organization to keep the "implementation detail" of using Pint (types in our docs aside) confined as...

Use Pint Application Registry

And to be clear, I'll do the refactor in lieu of a88d7dd.

pyproj output not acceptd by metpy

This definitely looks like a bug in the metadata mapping.

pyproj output not acceptd by metpy

Thanks for the detailed run down and example code. That error is because the conversion from PyProj to CF is giving us a value of 0 for `inverse_flattening`. While CF...

pyproj output not acceptd by metpy

I think there's still something to be done about the stereographic projection here, since it's not at all clear that Polar Stereographic (style-B) [requires a latitude of the origin](https://cfconventions.org/wkt-proj-4.html).