Klaus Zimmermann

Github's automatic migrator has provided PR #2569 for this, though probably a little bit of manual work remains.

We are cmorizing cmip6 data for EC-Earth and are running into the following issues: - We relatively often get at least two versions for one simulation because the cmorization runs...

We are also experiencing the unused dimension issue. Here is the relevant ncdump output (omitting only the global attributes): ``` netcdf areacello_Ofx_EC-Earth3-Veg_historical_r1i1p1f1_gn { dimensions: j = 292 ; i =...

To me, Intake seems like the best way forward here. In case you do want to go forward with this proposal, I'd like to propose another variation. Instead of having...

Thanks for picking this up, @TomAugspurger. What you describe is close, but not quite what I had in mind. Indeed, I would say if Pystac has to know all the...

Are you thinking 1D, e.g. different heights, full 3D, different 2D, e.g. transects, or something else entirely? Perhaps we can add one or two concrete examples with phenomenon, source grid,...

It seems most of the goals here would best be achieved by better supporting the `dask.distributed` scheduler. This would not only allow for parallelism on one node, as multiprocessing does,...

Perhaps I was thrown off by the use of multiprocessing. So to be clear, you don't mean [`multiprocessing`](https://docs.python.org/3/library/multiprocessing.html)?

I'll be interested to see what you come up with. From my personal experience, it seems that almost any non-trivial application will require direct dask programming for the core array...

I think codewise, this is ready. Is this something that should get a news entry? It is not very user facing, rather only relevant for developers. Wrt docs, this is...