-
Notifications
You must be signed in to change notification settings - Fork 262
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
The max dimension sizes do not take CDF-5 format into account. #187
Conversation
NetCDF-c Github issue #185 The code in libsrc/dim.c has not been upgraded to support CDF-5 format. Rule we are implementing sets the max dimension sizes as follows: Classic: CDF-1 NC_MAX_INT - 3 = 2147483647 - 3 64 bit Offset: CDF-2 NC_MAX_UINT - 3 = 4294967295 - 3 64 bit Data: CDF-5 NC_MAX_UINT64 - 3 = 18446744073709551615 - 3 The -3 is to handle rounding.
I got it, but cannot figure out yet why it works Ward Fisher wrote:
|
Poking around on this a bit, the failure on travis is in the |
The first issue appears to be that tst_dimsizes.sh does not have the executable bit set; other errors are reported once it runs, but that at least is the initial problem :). |
I'm also seeing, in the docker container, the following when I run the script: ./tst_dimsizes.sh: 24: test: ../ncdump/ncdump: unexpected operator So perhaps |
(#187) Primary problem was cmake build errors.
The max dimension sizes do not take CDF-5 format into account.
NetCDF-c Github issue #185
The code in libsrc/dim.c has not been upgraded to support
CDF-5 format.
Rule we are implementing sets the max dimension sizes as follows:
Classic: CDF-1 NC_MAX_INT - 3 = 2147483647 - 3
64 bit Offset: CDF-2 NC_MAX_UINT - 3 = 4294967295 - 3
64 bit Data: CDF-5 NC_MAX_UINT64 - 3 = 18446744073709551615 - 3
The -3 is to handle rounding.