It is now twice that HBT+ has failed to load/save a specific file and continued to run. This is annoying since the user may not be aware of any problems if they see the job completed, unless they explicitly look at the error log files.
Example of incorrect loading but continued running:
####ERROR READING /PartType0/InternalEnergies from /cosma8/data/dp004/jlvc76/FLAMINGO/FOF/L1000N1800/HYDRO_LOW_SIGMA8/fof_snapshot/flamingo_0000/flamingo_0000.13.hdf5, error number -1
HDF5-DIAG: Error detected in HDF5 (1.12.2) thread 0:
#000: H5D.c line 320 in H5Dclose(): not a dataset ID
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.12.2) thread 0:
#000: H5S.c line 491 in H5Sclose(): not a dataspace
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.12.2) thread 0:
#000: H5S.c line 491 in H5Sclose(): not a dataspace
major: Invalid arguments to routine
minor: Inappropriate type
It is now twice that HBT+ has failed to load/save a specific file and continued to run. This is annoying since the user may not be aware of any problems if they see the job completed, unless they explicitly look at the error log files.
Example of incorrect loading but continued running: