-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
SaveGraph producing unclear results, when the TChain has no name #10928
Comments
:) |
Blessed |
Just "Unnamed" is not very descriptive. If the chain has no name SaveGraph can show e.g. |
FYI: Added in Milestone 6.28. since this is the default behaviour in the RDatasetSpec when having a chain with different tree names. I should solve it if noone comes before the release of 6.28. |
Removed the 6.28 milestone, this is not severe enough to block the release. |
This might be affected/solved by #13088. |
Thanks @bernhardmgruber , unfortunately this is independent of RNTuple. TChains with no name are a thing, in general. |
Ah, I didn't check the implementation and assumed #13088 was implemented in |
Nice change. I proposed a simplification. The tests seem to fail because the change does what it is supposed to do and the reference would need to be adapted. |
Thanks! We're on it |
If the underlying TChain has no name (""), then the output of SaveGraph is far from helpful.
The following script:
Produces:
Example solution: if the chain has no name => call the source node
TChain with no name
.(Remark, same comment is applicable for the
Describe()
action. The commented line would produceDataframe from TChain in file f.root [...]
. Notice the 2 spaces after "TChain".)CC: @eguiraud @vepadulano
The text was updated successfully, but these errors were encountered: