Structure code with separate IO layer
The current focus (and within IS-ENES3 hopefully) is to focus on IRIS as the IO layer. But it might be strategically wise to keep a door open for XARRAY. IRIS use the cube construct for storing data (and metadata), and XARRAY use a pandas-like (pandas-compatible?) construct. Both builds on dask under the hood. So the question at hand is whether it is possible and worthwhile to structure CLIMIX so that either can be used.