NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
I have submitted a PR to netcdf-fortran with the fix and tests: https://github.com/Unidata/netcdf-fortran/pull/383 On Fri, Nov 4, 2022 at 1:23 PM Edward Hartnett - NOAA Affiliate < edward.hartnett@xxxxxxxx> wrote: > I will submit a PR with a fix for the missing constants in netcdf-fortran. > > It's entirely my fault - but will be fixed for the next release. > > Until then, just use the constants 2 and 3, as defined in the C netcdf.h > file: > > #define NC_QUANTIZE_BITGROOM 1 /**< Use BitGroom quantization. */ > #define NC_QUANTIZE_GRANULARBR 2 /**< Use Granular BitRound quantization. > */ > #define NC_QUANTIZE_BITROUND 3 /**< Use BitRound quantization. */ > > > On Fri, Nov 4, 2022 at 12:22 PM Charlie Zender <zender@xxxxxxx> wrote: > >> Hi Matt, >> >> > So I was wondering: Is there a fundamental Fortran reason for not >> supporting the other two variants? Or perhaps, is it that, of the three >> variants, Bit Groom is by far the one people should use, so that's what >> was exposed by the Fortran interface? >> >> Great question. No fundamental reason. >> All three quantization methods are >> intended to be in the netCDF Fortran library via >> the same API as BitGroom. >> I'm unsure about the status of Granular BitRound >> and BitRound in the latest Fortran release. >> Others can chime in about that. >> When all three are available in your Fortran >> library, I recommend using either Granular BitRound >> (with number of significant digits) or BitRound >> (with number of stored bits). They both yield >> better compression than BitGroom, as shown here: >> >> https://nco.sourceforge.net/nco.html#fgr_003aqnt_005fcr_005fzst >> >> Charlie >> -- >> Charlie Zender, Earth System Sci. & Computer Sci. >> University of California, Irvine 949-891-2429 )'( >> >> _______________________________________________ >> NOTE: All exchanges posted to Unidata maintained email lists are >> recorded in the Unidata inquiry tracking system and made publicly >> available through the web. Users who post to any of the lists we >> maintain are reminded to remove any personal information that they >> do not want to be made public. >> >> >> netcdfgroup mailing list >> netcdfgroup@xxxxxxxxxxxxxxxx >> For list information or to unsubscribe, visit: >> https://www.unidata.ucar.edu/mailing_lists/ >> >
netcdfgroup
archives: