-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
a first unit test for backward compatibility of Scouting data formats #41093
a first unit test for backward compatibility of Scouting data formats #41093
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41093/34712
|
A new Pull Request was created by @missirol (Marino Missiroli) for master. It involves the following packages:
@cmsbuild, @smuzaffar, @Dr15Jones, @makortel can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
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.
A couple of typos I'll have to fix.
('vector<Run3ScoutingVertex>', 'hltScoutingPrimaryVertexPacker:primaryVtx') | ||
] | ||
else: | ||
raise RuntimeError(f'getScoutingProductsList -- invalid key (must be "Scouting", "Run3Scouting"): "{key}"') |
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.
raise RuntimeError(f'getScoutingProductsList -- invalid key (must be "Scouting", "Run3Scouting"): "{key}"') | |
raise RuntimeError(f'getScoutingProductsList -- invalid key (must be "Scouting", or "Run3Scouting"): "{key}"') |
parser.add_argument('-n', '--maxEvents', type = int, help = 'Max number of input events to be processed', | ||
default = 10) | ||
|
||
parser.add_argument('--skipEvents', type = int, help = 'Number of input events to skipped', |
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.
parser.add_argument('--skipEvents', type = int, help = 'Number of input events to skipped', | |
parser.add_argument('--skipEvents', type = int, help = 'Number of input events to be skipped', |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-4d50da/31391/summary.html Comparison SummarySummary:
|
a790a14
to
eb36eaf
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41093/34722
|
Pull request #41093 was updated. @cmsbuild, @smuzaffar, @Dr15Jones, @makortel can you please check and sign again. |
please test (Only fixed a few typos.) |
Okay, I un-drafted the PR, and the last push integrates #41093 (comment). "Better than nothing" is indeed in the PR description. I would also backport this to
This is also not addressed in this PR, and should be improved in the future. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41093/34793
|
Pull request #41093 was updated. @cmsbuild, @smuzaffar, @Dr15Jones, @makortel can you please check and sign again. |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-4d50da/31524/summary.html Comparison SummarySummary:
|
Another incarnation of #39803 |
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR adds a refined version of the unit test described in #41040 (comment) [*]. The aim of the test is to fail whenever non-backward-compatible changes are introduced in the Scouting data formats.
The implementation of the test could certainly be improved (one suggestion is in #41040 (comment)), but I decided to open a draft PR because I think the test in this PR is better than nothing. (I plan to address #41040 (comment), but I don't have an ETA for that.)
[*]
More precisely, there are two unit tests, one for the Run-2 Scouting data formats ("Scouting*"), and one for the Run-3 ones ("Run3Scouting*"). The two tests have the same structure:
a 1st step reads O(100) events from an existing EDM file, and writes the Scouting collections to disk (this first step should fail if non-backward-compatible changes are made to the data formats);
a 2nd step uses FWLite to print to stdout one entry/object for each of the Scouting data formats being tested. To check that the correct values are read, the test compares the output of step-2 to a reference in the form of a text file. This is currently done for 1 object per data format. It might be necessary to check more than 1 object (and/or more than 1 event), because Add additional track variables to the Run 3 scouting electron collection for low pT electrons. #41025 (comment) showed that some issues can only be spotted when checking multiple objects/events.
PR validation:
The new unit tests pass locally.
If this PR is a backport, please specify the original PR and why you need to backport that PR. If this PR will be backported, please specify to which release cycle the backport is meant for:
If accepted, it would be good to backport it to at least
CMSSW_13_0_X
.