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
Remove unused simTrackHits parameter from some L1 track trigger code #22929
Conversation
To avoid any further confusion
To avoid further confusion
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-22929/4315 |
A new Pull Request was created by @makortel (Matti Kortelainen) for master. It involves the following packages: L1Trigger/TrackTrigger @cmsbuild, @civanch, @kpedro88, @nsmith-, @rekovic, @mdhildreth, @thomreis can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
The tests are being triggered in jenkins. |
Thanks @makortel - I'm not sure why is was there is the first place - |
@boudoul this is historical, initially the simhits were also matched. At some point the simhits were removed from the event content, but apparently everything was not fully cleaned up. |
Thanks @sviret for the confirmation that these can indeed be safely clean up. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
+1 |
1 similar comment
+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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
This PR suggests to remove
simTrackHits
parameter from two places in L1 track trigger code where I found them confusing and not used. (confusion arose from the need to understand whether these modules actually needg4SimHits
or not in the context of pileup mixing)Tested in CMSSW_10_1_0, no changes expected.