You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to this PR, it looks like the chunkspec was extended to allow a per-variable chunking, using
-c var:c1,c2,...ck
where var is the name of the variable and ci is the chunksize for the ith dimension of that variable. However, I don't see this second form documented in the man page of nccopy , and the entry in the NUG describing the chunkspec option says that you cannot use nccopy to chunk variables independently.
It is unclear if this new form was added and the supporting documentation was never updated, or if the new form was removed at some point. Either way, we just need to verify that the documentation is accurate. Tagging @DennisHeimbigner in as well.
The text was updated successfully, but these errors were encountered:
It looks like the man page is updated and correct - the issue was that I was looking at the output of nccopy -h, which does not show an example of the variable level chunking syntax (might be too much text to add there, though). The NUG page should be updated. @ethanrd
As reported by @lesserwhirls:
PR #1087 introduced an alternative form for per-variable chunking, as described below:
So using nccopy, you can set a chunkspec based on dimensions like so:
According to this PR, it looks like the chunkspec was extended to allow a per-variable chunking, using
where var is the name of the variable and ci is the chunksize for the ith dimension of that variable. However, I don't see this second form documented in the man page of nccopy , and the entry in the NUG describing the chunkspec option says that you cannot use nccopy to chunk variables independently.
It is unclear if this new form was added and the supporting documentation was never updated, or if the new form was removed at some point. Either way, we just need to verify that the documentation is accurate. Tagging @DennisHeimbigner in as well.
The text was updated successfully, but these errors were encountered: