I have a .root file created with a ROOT 5.22/00a version (linux on clued0). It contains several TNtupleD (and a small histogram). It is read with no problem with that setup and with 5.24 (on a colleague’s laptop). When I try to read it with my ROOT 5.26/00c (Ubuntu Linux), it opens succesfully, but then:
and 100s more messages of this type.
Actually, we have several such files. A possible hint is that happens for our large files (39M and
up) but not for the smaller files (13M and down). So I don’t have (yet?) a small example to send with this.
Any ideas what’s going on?
Better yet, any ideas how to work around this issue?
Preferably without regenerating all the files with the latest ROOT version, which isn’t trivial due to computing environments.
BTW1: the length and md5sum of the files are the same, so it’s not a problem in copying the file.
BTW2: as may be expected from the error messages, after the Errors, the TNtupleD has the right number of branches, but they are blank. E.g.
It’s a big to upload to my usual public website. And copying just one tree produces a tree that causes no problems
So I copied it to
in the hope you can access that.
The md5sum OK for this copy too.
BTW: Same problem from an SLC5 machine with ROOT version 5.26/00b
This file was not properly closed and is missing all the meta information needed to read it with a newer version of ROOT. You can work around the problem by either copying the file (for example using hadd) with the same version of ROOT that was used to write it (this will work because there is somehow enough information to know where the data is on the file). Alternatively to read this file in a newer version of ROOT you would need to first open another file correctly written with the orginal/old version of ROOT so that the meta data is preloaded (i.e the ‘StreamerInfo for version 11’)
Saved me a lot of headaches (I didn’t make these files).
So many thanks.
BTW: it would’ve been nice if ROOT gave a warning when using such a file, even if it manages to recover from such missing information (happens in hadd, but not when Projecting from the tree). I realize this situation may be too rare to be worth the effort, or even impossible in the latest versions.