JT Thielen

This relates to a perennial discussion point in Pint about handling of scalars and arrays (e.g., https://github.com/hgrecco/pint/issues/1128, https://github.com/hgrecco/pint/issues/950, https://github.com/hgrecco/pint/issues/753) that hasn't seen a good resolution yet. In short, this seems...

> Kind of? Depends on whether I create the quantity with `pint` or `ureg`: > ``` > ... > ``` > That's not really ideal - `force_ndarray_like` is really a...

This is unfortunately not well-defined for Pint Quantities, as a single `like` argument isn't enough info to unambiguously specify the output (is it "like" in just the array type sense,...

This would be a critical component to include with the doc updates of https://github.com/hgrecco/pint/issues/972, though, would there be an easy way to have a stop-gap fix in the current theme...

> I assuming the thinking there is "if it's not needed, the user shouldn't have it installed," [...] That's not intention with these imports, instead, we need to have a...

Here are some of the thoughts I had (from a high-level perspective, not getting into finer details of the individual pages): - **Content coverage** - I think the breadth and...

Here's a brief snippet of code that could act as a starting point, given the one level depth of organization of datasets output by `cfgrib` (though could likely be cleaned...

My hunch is that we could easily add a `cfgrib.open_datatree()` method to supplement/replace the existing `cfgrib.open_datasets()` from what I had (to https://github.com/ecmwf/cfgrib/blob/master/cfgrib/xarray_plugin.py), but supporting the backend engine would take more...

I've played around with this recently in my coursework, and I wrote up a new Python implementation for it using pint quantities. While I would still need to do some...

Also, in relation to #1199, it does work for grids.