-
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
Update Run3 GEM to use the eMap from the DB #29194
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29194/14168
|
please test |
The tests are being triggered in jenkins. |
A new Pull Request was created by @watson-ij (Ian J. Watson) for master. It involves the following packages: EventFilter/GEMRawToDigi @perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
it looks like run3 and phase2 MC is broken for GEMs using the database for emap. |
We have a candidate GT for GEM eMap in MC. If I run the ttbar 2021 workflow with the auto GT and then with the following: |
assign alca I'm adding alca to keep track of the GT update. @watson-ij |
New categories assigned: alca @christopheralanwest,@franzoni,@tlampen,@pohsun,@tocheng you have been requested to review this Pull request/Issue and eventually sign? Thanks |
@cmsbuild please test |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
+1
|
@silviodonato |
unassign alca |
@christopheralanwest the difference is related to #29237 |
+operations |
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, @silviodonato, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
waiting for #29210 |
+1 |
PR description:
Fix for GEM crashing in Run3 data due to the emap not being read from the database. This patch instructs run3 to also use dbEmaps, as was done in slice test (its a minimal change as currently only slice test and run 3 emaps are in the db).
PR validation:
I tested on one of the files [1] and it no longer crashes. There are still warnings of the form
%MSG-e BadDigiInput: GEMRecHitProducer:gemRecHits 11-Mar-2020 11:39:34
CET Run: 335670 Event: 4434
Failed to find GEMEtaPartition for ID Re -1 Ri 1 St 1 La 2 Ch 25 Ro 8
%MSG
which is due to currently only the slice test geometry being in the DB, which is being worked on.
I haven't checked on MC though.
[1] cmsDriver.py GEM --step=RAW2DIGI,L1Reco,RECO --filein=/store/data/Commissioning2020/MinimumBias/RAW/v1/000/335/670/00000/5F3ECF4A-0637-844F-AE67-6BB424F0BF80.root --data --conditions 110X_dataRun3_Prompt_v3 --no_exec --era Run3
@jshlee @hyunyong