-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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 ME0 from HGCal custom (but not HGCalMuon) #3964
Remove ME0 from HGCal custom (but not HGCalMuon) #3964
Conversation
…, because the non-muon doesnot have ME0
A new Pull Request was created by @mark-grimes (Mark Grimes) for CMSSW_6_2_X_SLHC. Remove ME0 from HGCal custom (but not HGCalMuon) It involves the following packages: Configuration/PyReleaseValidation @civanch, @nclopezo, @vlimant, @mdhildreth, @cmsbuild, @franzoni, @Degano, @davidlange6 can you please review it and eventually sign? Thanks. |
Fully tested but I'll wait for the go ahead from @ianna before merging. Ping @boudoul as well. Tests 10000, 10200, 10400, 11200, 11400, 12000, 12800, 13000, 13600 and 14600 pass all steps.
Tests 12200, 12400, 13800, 14000, 14200 and 14400 fail in step 3 (as before, except 14200 gets this far as well) with:
I had a crash with 12200 in step 2 the first time I tested, then ran it again and it passed which is a little worrying. I'll look through to see if I can find any use of uninitialised memory. The crash was:
|
merge We'll try this in the next IB along with #3967 to see how the build, and revert any problems later. |
Remove ME0 from HGCal custom (but not HGCalMuon)
@mark-grimes - RPCs are part of all Phase 2 scenarios. It's only ME0 can be missing if there is no space for it. BTW, I'm not sure Extended pixel is part of HGCal scenarios yet - should it be included? |
HGCalMuon and HGCalMuon4Eta have ME0 but HGCal does not. Previously they both used the same customisation and so HGCal (142xx) failed in step 2 because it couldn't find the ME0 hits. With this pull request the customisations are diverged.
The effective only change is that HGCal calls cust_2023Pixel() before applying the HGCal specifics. It previously called cust_2023Muon() instead. HGCalMuon and HGCalMuon4Eta still call cust_2023Muon().
The consequence is that HGCal no longer has these two lines in the customisation sequence:
@ianna, is it correct to remove the customise_rpc call as well? I did it this way because it was easier to delegate to the cust_2023Pixel function.
After this change the 142xx tests run through step 2 and fail in step 3 with the same crash as all the others.