-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[ntuple] fixes to subfield name handling #20629
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
Open
jblomer
wants to merge
3
commits into
root-project:master
Choose a base branch
from
jblomer:ntuple-fix-variant-item-names
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,53 @@ | ||
| #include "ntuple_test.hxx" | ||
|
|
||
| TEST(RNTuple, SubFieldName) | ||
| { | ||
| EXPECT_EQ("_0", ROOT::RAtomicField("f", std::make_unique<RField<char>>("x")).begin()->GetFieldName()); | ||
| EXPECT_EQ("_0", ROOT::RVectorField("f", std::make_unique<RField<char>>("x")).begin()->GetFieldName()); | ||
| EXPECT_EQ("_0", ROOT::RRVecField("f", std::make_unique<RField<char>>("x")).begin()->GetFieldName()); | ||
| EXPECT_EQ("_0", ROOT::RArrayField("f", std::make_unique<RField<char>>("x"), 2).begin()->GetFieldName()); | ||
| EXPECT_EQ("_0", ROOT::ROptionalField("f", std::make_unique<RField<char>>("x")).begin()->GetFieldName()); | ||
| EXPECT_EQ("_0", ROOT::RAtomicField("f", std::make_unique<RField<char>>("x")).begin()->GetFieldName()); | ||
| EXPECT_EQ("_0", ROOT::RSetField("f", ROOT::RSetField::ESetType::kSet, std::make_unique<RField<char>>("x")) | ||
| .begin() | ||
| ->GetFieldName()); | ||
|
|
||
| { | ||
| std::unique_ptr<ROOT::RPairField> p{ | ||
| new ROOT::RPairField("x", {std::make_unique<RField<char>>("x"), std::make_unique<RField<char>>("x")})}; | ||
| EXPECT_EQ("_0", ROOT::RMapField("f", ROOT::RMapField::EMapType::kMap, std::move(p)).begin()->GetFieldName()); | ||
| } | ||
|
|
||
| { | ||
| std::vector<std::unique_ptr<ROOT::RFieldBase>> items; | ||
| items.emplace_back(std::make_unique<RField<char>>("x")); | ||
| items.emplace_back(std::make_unique<RField<int>>("x")); | ||
| ROOT::RVariantField f("f", std::move(items)); | ||
| auto itr = f.begin(); | ||
| EXPECT_EQ("_0", itr->GetFieldName()); | ||
| itr++; | ||
| EXPECT_EQ("_1", itr->GetFieldName()); | ||
| } | ||
|
|
||
| { | ||
| std::array<std::unique_ptr<ROOT::RFieldBase>, 2> items; | ||
| items[0] = std::make_unique<RField<char>>("x"); | ||
| items[1] = std::make_unique<RField<char>>("x"); | ||
| ROOT::RPairField f("f", std::move(items)); | ||
| auto itr = f.begin(); | ||
| EXPECT_EQ("_0", itr->GetFieldName()); | ||
| itr++; | ||
| EXPECT_EQ("_1", itr->GetFieldName()); | ||
| } | ||
|
|
||
| { | ||
| std::vector<std::unique_ptr<ROOT::RFieldBase>> items; | ||
| items.emplace_back(std::make_unique<RField<char>>("x")); | ||
| items.emplace_back(std::make_unique<RField<char>>("x")); | ||
| ROOT::RTupleField f("f", std::move(items)); | ||
| auto itr = f.begin(); | ||
| EXPECT_EQ("_0", itr->GetFieldName()); | ||
| itr++; | ||
| EXPECT_EQ("_1", itr->GetFieldName()); | ||
| } | ||
| } |
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to be a degradation. The user used on line 121 the name
myfloatwhich is now no longer represented in the schema ... is that the intent?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, because the binary format specification says that the item field has name
_0Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Humm .... when reading back how will the user properly retrieve
myfloatvsmyotherfloatif they are both turned into_0and the name are completely forgotten?i.e. Is the name really gone (likely a blocker of sort) or is it just an artefact of the printing?