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
Move muon SelectionType and Selector string to enum maps to muon namespace #29786
Conversation
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29786/15244
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29786/15245
|
A new Pull Request was created by @dntaylor (Devin Taylor) for master. It involves the following packages: DataFormats/MuonReco @perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@dntaylor |
No, I wanted to have the muon reco L3 look at it first. I didn't think it would trigger the review process if it was in draft. Next time I'll just pass around the comparison URL. |
OK. |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29786/15278
|
@cmsbuild please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 for #29786 1c92d45
|
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. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
The goal here is to make available the list of Selectors or SelectionType enums in a given release available as strings. Specifically for analysis based recipes (like TagAndProbe) that want to store all supported Selectors but not have to manually update the code when new IDs are released.
For example:
PR validation:
runTheMatrix (so I didn't break anything) and the above example in a ntuplizer works as expected.