-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Browsing a ROOT file... #194
Comments
I'm kinda of mentally done with legacy ROOT; my hope is to find time to do RNTuple and just ask everyone to use that... |
Amen to that! |
I agree, however we have a several hundreds of TB of ROOT data already and much more to come 😆 I think the "legacy ROOT" will still have high-demand in the next decade, unfortunately... I am still not sure how to solve the exploration issue, but I guess I will then implement an additional method like |
first we probably want to clear the mess of difference between:
|
Yes absolutely ;) I'd prefer to have it similar to My main point is that something is needed which allows to explore the structure. Even if So in principle, I would start with Lines 137 to 147 in 57e49d3
and let that return some new wrapper struct ( What do you think? |
I am totally happy with #199 so let use close this for now ;) |
Yes I know, we are buried in issues but this is something I wanted to discuss for a long time
;)
Currently it's very user-unfriendly to explore a ROOT file's structure when there are some streamers missing because
f[...]
always tries to directly parse and return a lazy array wherever possible. I think it would be better to make it more explicit so that we don't have too many surprises when invokingBase.getindex
.Here is an example for a file I am debugging:
As seen above, we are hit with an error end then nothing helps further, although we might have some branches which are well readable.
I think there are two possibilities:
getindex
typestable and predictable by always returning some kind of an accessor object with a path in a ROOT file. Helper functions are then used to make it to a, something likelazyarray(f, "...")
orarray(f, "...")
Base.keys
to bypass the interpretation mechanismWhat do you think? I have some prototype implementations but I don't really which direction to go.
The text was updated successfully, but these errors were encountered: