Stephan Hoyer

> If it is the latter, one can just modify d.values and e.values (as well as their coordinates systems) to point to the new ndarrays, right? Yes, in principle we...

> I think the most confusing part is that this the modifications will trickle down sometimes -- even though I'd prefer them to be always propagated, I would still mind...

Yes, that's a great idea! We could add a copy=False argument to both the Dataset and DataArray constructors, like the align function. On Thu, Oct 29, 2015 at 11:58 AM,...

The original example how gives an error about `dim_1` have different size, but you can still reproduce the behavior if you provide explicit labels for `dim_1`, e.g., ``` ds =...

One underlying issue here (which hopefully explains part of this) is that SciPy does not support does not support lazy writes to netCDF files -- you cannot set data on...

You could do this with `lax.cond` inside `lax.scan` -- just apply the identity function if the loop should terminate early. The downside is that you will pay the price of...

This is a great question. Right now, modifying the guts of NeuralGCM models this is tricky to do with the current NeuralGCM codebase. We are planning to make this easier...

This looks great! Would it be possible to make the sync path reuse the async methods internally? This would help reduce duplication, increase test coverage and speed up sync workflows.

I'm pretty sure Zarr v3 uses async internally to implement sync methods. It may be worth taking a look at how Zarr does things, especially given the strong overlap in...

OK, let's try to reach some initial resolution about the async strategy for Xarary over in #10622 first!