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 Charlie, > netCDF configured with --enable-logging reports many (!) of the > warnings when NCO uses it to examine HDF4 files: > "H5F_locate_signature(): unable to find a valid file signature" > Is there a way to quiet this particular warning? > It is a predictable message that could perhaps be fixed, e.g., teach > netCDF4/HDF5 to expect that valid HDF4 signatures are unavailable. > Or perhaps there is a way to set the verbosity of HDF logging? > > Configuring without --enable-logging eliminates the unwanted messages. > But that would also eliminate the unpredictable and wanted messages. If you build netCDF with --enable-logging, then put the following in your code: nc_set_log_level(3); You will then get a ton of output. Trying changing the "3" to a "1" to get less output, or to a 5 to get more. > Something for Unidata and THG to chew-on, I suppose. Yes, we're glad THG provided this, so we could make it available in the netCDF C and Fortran APIs. --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: SZV-506829 Department: Support netCDF Priority: Normal Status: Closed