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.
On Mon, Oct 25, 2010 at 09:16:31AM -0600, Ed Hartnett wrote: > This problem was caused by an inadvisable call to H5close() inside the > netCDF library. Of course it was very silly of me to do this - how can > the netCDF library know if you are still using the HDF5 library? > > The call to H5close() was removed, and thus the problem will not occur > for you. I wonder if you added this close some time after this discussion? http://mailman.unidata.ucar.edu/mailing_lists/archives/netcdf-hdf/2007/msg00107.html and if so, does removing this call have implications for parallel I/O ? ==rob -- Rob Latham Mathematics and Computer Science Division Argonne National Lab, IL USA
netcdfgroup
archives: