Open felixcremer opened 3 months ago
This problem also appears, when I try to save the resulting YAXArray to netcdf via savecube.
The problem seems to come from trying to use Float16 and I think this is actually a NetCDF issue, because it could give a clearer error message rather than this cryptic array needs to be non-empty.
Indeed, as far as I know, Float16 is not supported:
When I am trying to set the output of mapCube via the OutDims path and backend combination to a netcdf file I get the following error: