[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[netCDF #XMJ-369691]: Re: excessive warnings when accessing HDF4 from netCDF



Hi Elena,

> There is an HDF5 call H5Fis_hdf5 to find out if a file is an HDF5 file
> http://www.hdfgroup.org/HDF5/doc/RM/RM_H5F.html#File-IsHDF5
> 
> I think it will help to "teach" netCDF not to open HDF4 files with an HDF5 API
> that apperently produces the warning (it looks to me as an error from the HDF5
> error stack).
> 
> Similar API in HDF4 is Hishdf
> http://www.hdfgroup.org/release4/doc/RefMan_html/RM_Section_II_H.html#wp458258

Thanks for the suggestion!

--Russ

> On Thu, 5 Jun 2014, Charlie Zender wrote:
> 
> > Hello,
> >
> > 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.
> >
> > Something for Unidata and THG to chew-on, I suppose.
> >
> > Thanks,
> > Charlie
> >
> 
> --
> 
> 

Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu



Ticket Details
===================
Ticket ID: XMJ-369691
Department: Support netCDF
Priority: Normal
Status: Closed