New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--cnk_dmn specifications ignored #198
Comments
I can reproduce this issue with the current distribution. Thanks for reporting it. Will post again when I have made progress. |
These commands both produce the chunksize=1 for time in all variables, as you desire: ncks -O -4 -L 1 --cnk_map=nc4 ~/in.nc ~/foo.nc The command you tried ncks -O -4 -L 1 --cnk_dmn time,1 ~/in.nc ~/foo.nc should also do that for all variables. Apparently it sets a chunksize |
Thak you! That would help in few of my use cases. I also have files with 4D variables, and I want to have a chunk size of 1 for one record and one non-record dimension, and some smaller chunk of two other dimensions. I have found that for single-precision floats a chunk of 1x1x200x200 already gives quite good compression with good granularity for extracting small subsets. Is there any trick to arrange such chunks with current nco? |
If you know the desired chunk sizes for each dimension, try specifying them all with four |
Thank you! With the above file Similar issue is reproducible with some files of more dimensions, but I could not easily create an MWE of reasonable size for that. I hope, the above example should be enough to reproduce and hunt down the bug... |
Thanks, I'll look into this later this summer. For now I suggest you use |
Hi,
When I do
ncks -4 -L5 --cnk_dmn time,1 in.nc out_ncks.nc
on an attached file
in.nc.gz
i get a file with strange chunking
I would expect it to set chunk size to 1,210,350 ...
ncks is the one from Ubuntu 20.04.
NCO netCDF Operators version 4.9.1 "Skyglow" built by buildd on lgw01-amd64-040 at Mar 23 2020 06:20:36
Also reproducible with
netCDF Operators version 4.9.3
_NCProperties = "version=2,netcdf=4.7.0,hdf5=1.10.4
What would be the right way to force 2D chunks?
Thnak you!
The text was updated successfully, but these errors were encountered: