Steven Decker

I'm coming around to thinking an object-based approach may allow for handling #461 and #1735 in a different way than #2437. My proposed interface is exemplified below in some theoretical...

I wouldn't get rid of the functions; I see an OO interface being a higher-level wrapper over the existing functions, as the declarative interface is a wrapper over Matplotlib. I...

I forgot to address the question of what makes sounding calculations fundamentally different from everything else. I think the answer to that is that sounding calculations are reductions. Just about...

This variation will run without coming anywhere close to consuming all memory, and yet I can't think of any way the resulting map would be useful or intentional in a...

I'm seeing the same thing in a new environment with all the latest and greatest from conda-forge. Code: ```python import xarray as xr import intake import metpy.calc as mpcalc catalog_url...

I found the workaround for my code: Do `.compute()` before `.metpy.quantify()` rather than later.

@dopplershift Glad to hear you have a fix, and thanks for the `.metpy.quantify()` tips. I knew the one `.metpy.quantify()` was needed for the sigma-to-pressure computation. The others I think we...

Yes, I was thinking that being forgiving with respect to time is essential, but I couldn't think of a case where I don't want to specify an exact vertical level....

I can confirm that if I use `cp.level = 292 * units('degK')` that does trigger a `DimensionalityError` when the "incorrect line" is used, so that is good.

How important is the "changelog" (line 84)?