[ntuple] Initial integration with TBrowser #18889
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
silverweed
reviewed
May 28, 2025
silverweed
reviewed
May 28, 2025
Test Results 20 files 20 suites 3d 14h 49m 5s ⏱️ For more details on these failures, see this check. Results for commit 09f8bad. ♻️ This comment has been updated with latest results. |
Similar to ROOT::MergeFunc_t, the function pointer for the Browse() function will allow custom browsing for objects that don't derive from TObject.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds minimal browsing capability for RNTuple with TBrowser (browsing already works with RBrowser). Introduces the more general capability for foreign objects (not inherited from TObject) to implement custom browsing. This is done similar to a custom merge function, by a special method signature that is picked up by the dictionary generation and registered in TClass. This capability is then used by the RNTuple anchor object.
As a result, TBrowser can show the structure of an RNTuple. Note that RNTuple only uses the abstract TBrowser interface, which is part of the core library.
In a follow-up PR,histogramming data is to be implemented. The idea is that the graphical browser will register an RNTuple visitor for the drawing, so that the GUI will depend on the RNTuple library but not vice versa.
Icons in the tree view panel of the browser need to be fixed, too.
Result after PR:
