-
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
Fixes in L1T Calo packers - useful for data taking - 80x #13786
Fixes in L1T Calo packers - useful for data taking - 80x #13786
Conversation
…re bitwise test of sums Conflicts: L1Trigger/L1TCommon/python/l1tComparisonStage2RAWvsEMU_cfi.py
A new Pull Request was created by @rekovic for CMSSW_8_0_X. It involves the following packages: EventFilter/L1TRawToDigi @cmsbuild, @mulhearn, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
please start test |
please test |
The tests are being triggered in jenkins. |
@rekovic |
@Martin-Grunewald It was meant as asking one of managers to trigger jenkins. I don't think I have the privileges to do this. I think currently Mike can do it for L1T. |
@rekovic in L1Trigger/L1TCommon/python/l1tComparisonStage2RAWvsEMU_cfi.py, this PR has # for initial module testing compared unpacked to unpacked!!!
egTagB = cms.InputTag("caloStage2Digis","EGamma"),
tauTagB = cms.InputTag("caloStage2Digis","Tau"),
jetTagB = cms.InputTag("caloStage2Digis","Jet"),
sumTagB = cms.InputTag("caloStage2Digis","EtSum"),
muonTagB = cms.InputTag("gmtStage2Digis","Muon"),
algTagB = cms.InputTag("gtStage2Digis",""), while #13767 has # for initial module testing compared unpacked to unpacked!!!
egTagB = cms.InputTag("caloStage2Digis"),
tauTagB = cms.InputTag("caloStage2Digis"),
jetTagB = cms.InputTag("caloStage2Digis"),
sumTagB = cms.InputTag("caloStage2Digis"),
muonTagB = cms.InputTag("gmtStage2Digis",""),
algTagB = cms.InputTag("gtStage2Digis",""), Which version should be picked ? |
Then why do you use a different configuration here ?
But this is exactly what I am asking: once both are merged, what version of the python file should be used, to resolve the conflict ? |
@fwyzard Because this PR has latest cherry-picks from a l1t-offline branch that super-seeds the l1t-tsg-v4 (i.e. #13767). One of the cherry picks picked up the change in this testing .py file, which is not used anywhere in CMSSW at the moment. When we merge l1t-tsg-v4 we should use the .py file version of that PR. What am I missing? Are you saying that we should remove the .py file from this PR or anticipate the version from l1t-tsg-v4? |
I'm saying that we should make sure this PR should merge cleanly on top of #13767 (or the opposite, depending which one should be merged first). |
Pull request #13786 was updated. @cmsbuild, @mulhearn, @davidlange6 can you please check and sign again. |
please test |
The tests are being triggered in jenkins. |
thanks, this now merges cleanly on top of #13767 (and vice versa) |
Fixes in L1T Calo packers - useful for data taking - 80x
Fixed EG Unpacker and EtSums Unpacker and Emulation to agree with packer.
Now Unpacked and Re-emulated L1T decisions in HLT are in agreement.
Should use this in data taking immediately.