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.
Hi Ed, On Jan 11, 2008, at 1:00 PM, netcdfgroup-request@xxxxxxxxxxxxxxxx wrote:
Message: 3 Date: Fri, 11 Jan 2008 08:55:37 -0700 From: Ed Hartnett <ed@xxxxxxxxxxxxxxxx> Subject: Re: [netcdfgroup] netCDF4 file bit-for-bit reproducibility? To: Charlie Zender <zender@xxxxxxx> Cc: netcdfgroup@xxxxxxxxxxxxxxxx Message-ID: <wrx1w8ogxvq.fsf@xxxxxxxxxxxxxxxxxxxxxxx> Content-Type: text/plain; charset=us-ascii Charlie Zender <zender@xxxxxxx> writes:Hi Ed,I'm afraid there is nothing I can do at the netCDF-4 level to change that.What about trying the procedure that Quincey suggests? Charlie--This would break the order of variables and dimensions, which is a key piece of the netCDF API.
HDF5 doesn't use any time information for tracking the creation order of objects in group or attributes on objects. I tried to go that way initially, but gave up on it last summer. So, it is safe to disable the time tracking in netCDF-4 and keep the creation order feature.
Quincey
netcdfgroup
archives: