Skip to content

fix: hide anonymous RNTuple fields by default #1469

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

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

ariostas
Copy link
Collaborator

This PR hides the anonymous fields present in RNTuples. I made this a draft because I want to spend some more time thinking about this to make sure everything that people might want to access is actually easily accessible.

This is a rough first draft that has some downsides. For example, if you have a tuple field, the underlying data in each position of the tuple is stored in fields _0, _1, ..., so those would be hidden, but those should actually be accessible. Similarly, if you have an array of structs, let's say an array of electrons, then the members get stored in _0.pt, _0.eta, ..., so again those would be hidden, but should actually be accessible.

The tricky part that I'll have to figure out is how to separate "key paths" from the "real paths" inside the RNTuple (e.g. electron.pt vs electron._0.pt).

Thanks to @kratsg for bringing up this issue.

@ianna ianna added the next-release Required for the next release label Jul 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
next-release Required for the next release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants