I have just been bitten by an unexpected behavior of h5diff, which I think should be fixed, although it corresponds to what the documentation says.
I used a plain "h5diff file1 file2" to check if my test runs were producing the expected results. Getting no output made me believe everything was fine. In reality, file2 contained nothing at all! The documented behavior of h5diff is in fact to compare only datasets that exist in both input files. However, h5diff does consider missing datasets to be a difference, since it returns the exit code 1 meaning "data differs". It seems that even with additional options, there is no way to simply check if two files have identical contents and get a succinct information about the differences. The exit code (a bit messy to check) just says "equal or not". The only way to get information about missing datasets is the -v option which also produces tons of output. So here comes my feature request: a) Ideal version: make h5diff report datasets that exist only in one dataset by default. b) If such a change of the documented behavior is not acceptable, provide a simple command line option to get the same result. Konrad. -- --------------------------------------------------------------------- Konrad Hinsen Centre de Biophysique Moléculaire, CNRS Orléans Synchrotron Soleil - Division Expériences Saint Aubin - BP 48 91192 Gif sur Yvette Cedex, France Tel. +33-1 69 35 97 15 E-Mail: research AT khinsen DOT fastmail DOT net --------------------------------------------------------------------- _______________________________________________ Hdf-forum is for HDF software users discussion. [email protected] http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
