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
fix collection names for premixing #20221
Conversation
A new Pull Request was created by @deguio (Federico De Guio) for master. It involves the following packages: Configuration/StandardSequences @vazzolini, @kmaeshima, @dmitrijus, @cmsbuild, @franzoni, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+code-checks |
please test |
1 similar comment
please test |
The tests are being triggered in jenkins. |
-1 Tested at: a2b7b4e The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: You can see the results of the tests here: I found follow errors while testing this PR Failed tests: RelVals AddOn
When I ran the RelVals I found an error in the following worklfows: runTheMatrix-results/5.1_TTbar+TTbarFS+HARVESTFS/step1_TTbar+TTbarFS+HARVESTFS.log135.4 step1 runTheMatrix-results/135.4_ZEE_13+ZEEFS_13+HARVESTUP15FS+MINIAODMCUP15FS/step1_ZEE_13+ZEEFS_13+HARVESTUP15FS+MINIAODMCUP15FS.log
I found errors in the following addon tests: cmsDriver.py TTbar_13TeV_TuneCUETP8M1_cfi --conditions auto:run2_mc --fast -n 100 --eventcontent AODSIM,DQM --relval 100000,1000 -s GEN,SIM,RECOBEFMIX,DIGI:pdigi_valid,L1,DIGI2RAW,L1Reco,RECO,EI,VALIDATION --customise=HLTrigger/Configuration/CustomConfigs.L1THLT --datatier GEN-SIM-DIGI-RECO,DQMIO --beamspot NominalCollision2015 --era Run2_25ns : FAILED - time: date Tue Aug 22 00:05:30 2017-date Mon Aug 21 23:59:09 2017 s - exit: 17920 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison not run due to runTheMatrix errors (RelVals and Igprof tests were also skipped) |
There is no packing/unpacking in Fastsim (means no hcalDigi) workflows... <...> |
sigh, I didn't think about that.
unless somebody has a smarter idea. |
I'm wondering if we can simply customize (reverting it for fastSim only) with: |
@abdoulline that is one potential solution; I still want to hear from trigger experts (e.g. @christopheralanwest) if this change is desirable in general. To clarify, the preferred more complicated solution would be:
|
@kpedro88, @abdoulline: I think either solution would work. However, I'm concerned about the change to using the unpacked TPs in the validation by default as I believe it is the simHcalTriggerPrimitiveDigis that are used downstream. In fact, before PR #19804, the packed TPs were not correct. A 92X backport of #19804 would be needed before PR #20222 (the backport for this PR) is merged, but I think that there was no such backport; perhaps @matz-e can confirm. Before switching to using unpacked TPs in the validation, it should be verified that the packed TPs are identical to those from the original collection. |
There was no backport of #19804. I'm never sure which releases need backports by now. I can quickly submit a backport. |
Please submit, Matthias. Thanks.
…On Wed, 23 Aug 2017, Matthias Wolf wrote:
There was no backport of #19804. I'm never sure which releases need backports by now. I can
quickly submit a backport.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the
thread.[AEx02kTHkE7yUZ35AFbr3RK20GsVuGRNks5sa8EhgaJpZM4O9fmv.gif]
|
+1 |
closing while we decide what's the best solution to implement |
this PR fixes: