This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Cihan, > We have an application that uses NetCDF and another library (LLNL's > Silo) which internally uses HDF5. Since upgrading to version 4 this > causes a problem due to NetCDF calling H5close() while Silo still relies > on HDF5 data instances being valid. > > I discovered this post: > http://www.unidata.ucar.edu/support/help/MailArchives/netcdf/msg09101.html > which reveals that the reason for calling H5close() is to free memory, > however, this doesn't take into account that HDF5 might be used outside > the NetCDF library. > > Do you have any suggestions on how to solve this problem? We currently > need both libraries but this problem is a show-stopper as we can only > use one but not both. Sorry it's taken so long to respond to your question. We've removed the call to H5close() in the current snapshot, so this problem should be fixed in the upcoming release, as well as the next beta release. --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: YTC-894489 Department: Support netCDF Priority: Emergency Status: Closed