Janneke van der Zwaan

Thanks for the suggestions, Jurriaan! I had a look at the github search results, and most of them are demo projects or not very active projects. This raises the question...

Yes, that's why I was suggesting gmail, we wouldn't have to set up that ourselves. There is the matter of the password, of course... I was also thinking of raising...

@rabernat do you maybe have example files that can be opened using `open_mfdataset`, `open_rasterio`, `open_zarr`, and `open_dataarray`? Preferably small files, that I'm allowed to add to recipy as test data.

@rabernat Thanks! In the mean time, I found sufficiently small netcdf data for testing the patch of `open_mfdataset`. For `open_rasterio`, I just used a standard tiff file, since we are...

It would be great if you can prepare a zarr file! Small is kilobytes (the netcdf-files I found are 67kb). The data does not have to make sense, but must...

No, don't worry about it! The work of patching xarray is more or less done (if you could prepare a small zarr file for testing that would still be helpful)....

It sounds like a bit of a hassle, also to maintain, but I don't have suggestions for a better (simpler) way. It is probably a good idea to install everything...

Ah, interesting! In the netcdf branch, I added an alternative way of getting version numbers, also using `pkg_resources` (see https://github.com/recipy/recipy/blob/netcdf/recipyCommon/libraryversions.py). Maybe this works even better!

I think we should go for the more flexible approach and make patched functions deal with checking whether a run id was created or not. Otherwise it will be very...

I think output file hashes are always None for the integration tests, because the files are removed before the script ends (and the hashes are calculated).