Nick Hodgskin

@fluidnumerics-joe I think that this is important to discuss. Just tuning back into parcels dev over the next couple days - I want to get a grasp on xgcm to...

I think we can close this now we have FieldSet and Field and VectorField in the codebase

Looks like the problem is in the C-conversion code in `kernel.py` (perhaps not being able to handle the dataset for some reason?)

After some investigation from @sruehs and @michaeldenes it looks to be a problem with the data and not Parcels

https://github.com/OceanParcels/Parcels/blob/93cc635b82397a826e4e0869f2db4ecc7b3bfb19/parcels/fieldset.py#L1352-L1372 `Fieldset.add_constant()` needs to have the value being a float, so in the case of a 2D array `...lon[0]` would return an array instead of a single float. This isn't...

> or they're used for tasks that will be implemented via other means in the v4 codebase. An example is the checking for duplicated Grids. This will be handled via...

This is now the case in `v4-dev`

I mean the type of compression that is used (there are various available compressors [zarr-developers/numcodecs](https://github.com/zarr-developers/numcodecs)). I agree about chunk size, but it would be good to also investigate the compression...

Thanks for clarifying! :) I haven't had the time yet to fully go through the paper. I've updated the description here to match.

Closing this. In v4 of Parcels users can choose their compressor for output data using https://zarr.readthedocs.io/en/stable/user-guide/config.html#runtime-configuration . If a user finds a better compressor than the default for some reason...