Skip to content

Small fix in TEvent to avoid reading objects that would be called "MetaData" but that would not be trees (related previous MR !65967))

I found out a small issue in the recently merged MR !65967 (merged). The previous MR (among many other things) implemented the reading of extra-metadata trees in order to retrieve event format information. This case can happen for augmented derivation file for instance were there is a metadata tree per stream decision.

The issue is in case an object is called "*MetaData*" e.g. in our analysis we have an hist (TH1D object) that is called MetaData_EventCount then the code was crashing by trying to read that object as a tree. I added a bit more protections against such cases and this solved the issue.

Tagging @akraszna, @ssnyder, @ekourlit and @gwatts.

Please let me know if you have comments about the robustness of the fix,
Thanks in advance,
Best,
Romain

Edited by Romain Bouquet

Merge request reports