-
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
remove tmp patch in the configuration of association thresholds for P… #18511
Conversation
A new Pull Request was created by @abbiendi for master. It involves the following packages: Validation/RecoMuon @cmsbuild, @dmitrijus, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
this is a very simple fix, is it possible to move on with it ? |
+1 |
The tests are being triggered in jenkins. |
This pull request is fully signed and it will be integrated in one of the next master IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
Hi, about the above comparison summary: there cannot be any sensible difference if (as I assume) the tested workflows are just the standard ones, given that this change touches only the New muon validation, which has to be enabled by a customization. |
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
please do not merge it. I fear it might spoil the other updates in PR #20701. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
Fix the configuration for phase2 New muon validation, removing the previous temporary patch.
This restores the desired defaults and is possible after the integration of the fix to the TrackerHitAssociator (PR #18354).
Git could not take that PR as wished (the file NewAssociators_cff.py was the wanted one in the submitted branch) as there was a previous PR (#18290 ) branched from the same base release which was integrated previously, containing the temporary patch, so it had to be expected. I realized it after checking the latest IB. sorry...