The two files being compared are not in fact, different. But I've noticed that h5diff 1.8.8 fails when comparing H5T_STD_U32LE to H5T_STD_U64LE (see bold text below). When I see that error message, I know it's going to be wrong.
dws@qawin32 /winsame/dws/vorpalall/vptests/tests/ptcls
$ C:/winsame/contrib-vs9/hdf5-1.8.8-par/bin/h5diff -v taggedParticles2p_taggedptcls_2.h5 C:/winsame/dws/vorpalall/vptests/vpresults-win32/ptcls/taggedParticles2p/taggedParticles2p_taggedptc ls_2.h5 /taggedptcls
dataset: </taggedptcls> and </taggedptcls>
attribute: <charge of </taggedptcls>> and <charge of </taggedptcls>>
0 differences found
Warning: different storage datatype
<currentTags> has file datatype H5T_STD_U32LE
<currentTags> has file datatype H5T_STD_U64LE
attribute: <currentTags of </taggedptcls>> and <currentTags of </taggedptcls>>
size: [4] [4]
position currentTags of </taggedptcls> currentTags of </taggedptcls> difference
···
------------------------------------------------------------
[ 1 ] 289 0 289
[ 2 ] 2 289 287
[ 3 ] 3 0 3
3 differences found
…
Now if I use h5diff 1.8.7 to diff those same files, I get the correct answer (and no complaint about datatypes):
dws@qawin32 /winsame/dws/vorpalall/vptests/tests/ptcls
$ C:/winsame/contrib-vs9/hdf5-1.8.7-ser/bin/h5diff -v taggedParticles2p_taggedptcls_2.h5 C:/winsame/dws/vorpalall/vptests/vpresults-win32/ptcls/taggedParticles2p/taggedParticles2p_taggedptcls_2.h5 /taggedptcls
dataset: </taggedptcls> and </taggedptcls>
attribute: <charge of </taggedptcls>> and <charge of </taggedptcls>>
0 differences found
attribute: <mass of </taggedptcls>> and <mass of </taggedptcls>>
0 differences found
attribute: <numPtclsInMacro of </taggedptcls>> and <numPtclsInMacro of </taggedptcls>>
0 differences found
attribute: <numSpatialDims of </taggedptcls>> and <numSpatialDims of </taggedptcls>>
0 differences found
attribute: <ptclEnds of </taggedptcls>> and <ptclEnds of </taggedptcls>>
0 differences found
attribute: <time of </taggedptcls>> and <time of </taggedptcls>>
0 differences found
attribute: <vsLimits of </taggedptcls>> and <vsLimits of </taggedptcls>>
0 differences found
attribute: <vsNumSpatialDims of </taggedptcls>> and <vsNumSpatialDims of </taggedptcls>>
0 differences found
attribute: <vsTimeGroup of </taggedptcls>> and <vsTimeGroup of </taggedptcls>>
0 differences found
attribute: <vsType of </taggedptcls>> and <vsType of </taggedptcls>>
0 differences found
I see this problem on both 32-bit and 64-bit Windows. Has anyone else seen it?
Dave