Skip to content
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 for JPTFastjet correction chains #17900

Closed
wants to merge 5 commits into from

Conversation

kodolova
Copy link
Contributor

Correction of the L1Fstajet correction for JPT

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @kodolova (kodolova) for master.

It involves the following packages:

JetMETCorrections/Configuration

@perrotta, @cmsbuild, @slava77, @monttj, @davidlange6 can you please review it and eventually sign? Thanks.
@TaiSakuma, @gouskos, @ahinzmann, @mmarionncern, @rappoccio, @jdolen, @nhanvtran, @gkasieczka, @schoef, @mariadalfonso this is something you requested to watch as well.
@Muzaffar, @davidlange6, @smuzaffar you are the release manager for this.

cms-bot commands are listed here #13028

@perrotta
Copy link
Contributor

@kodolova please edit the PR title to include explicitly the description of the fix

@slava77
Copy link
Contributor

slava77 commented Mar 13, 2017

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 13, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/18363/console Started: 2017/03/13 19:17

@cmsbuild
Copy link
Contributor

-1

Tested at: 9354882

You can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-17900/18363/summary.html

I found follow errors while testing this PR

Failed tests: RelVals

  • RelVals:

When I ran the RelVals I found an error in the following worklfows:
140.53 step2

runTheMatrix-results/140.53_RunHI2011+RunHI2011+RECOHID11+HARVESTDHI/step2_RunHI2011+RunHI2011+RECOHID11+HARVESTDHI.log

4.53 step3
runTheMatrix-results/4.53_RunPhoton2012B+RunPhoton2012B+HLTD+RECODR1reHLT+HARVESTDR1reHLT/step3_RunPhoton2012B+RunPhoton2012B+HLTD+RECODR1reHLT+HARVESTDR1reHLT.log

1000.0 step2
runTheMatrix-results/1000.0_RunMinBias2011A+RunMinBias2011A+TIER0+SKIMD+HARVESTDfst2+ALCASPLIT/step2_RunMinBias2011A+RunMinBias2011A+TIER0+SKIMD+HARVESTDfst2+ALCASPLIT.log

1003.0 step2
runTheMatrix-results/1003.0_RunMinBias2012A+RunMinBias2012A+RECODDQM+HARVESTDDQM/step2_RunMinBias2012A+RunMinBias2012A+RECODDQM+HARVESTDDQM.log

1001.0 step2
runTheMatrix-results/1001.0_RunMinBias2011A+RunMinBias2011A+TIER0EXP+ALCAEXP+ALCAHARVD1+ALCAHARVD2+ALCAHARVD3+ALCAHARVD4+ALCAHARVD5/step2_RunMinBias2011A+RunMinBias2011A+TIER0EXP+ALCAEXP+ALCAHARVD1+ALCAHARVD2+ALCAHARVD3+ALCAHARVD4+ALCAHARVD5.log

1306.0 step3
runTheMatrix-results/1306.0_SingleMuPt1_UP15+SingleMuPt1_UP15+DIGIUP15+RECOUP15+HARVESTUP15/step3_SingleMuPt1_UP15+SingleMuPt1_UP15+DIGIUP15+RECOUP15+HARVESTUP15.log

1330.0 step3
runTheMatrix-results/1330.0_ZMM_13+ZMM_13+DIGIUP15+RECOUP15+HARVESTUP15/step3_ZMM_13+ZMM_13+DIGIUP15+RECOUP15+HARVESTUP15.log

10042.0 step3
runTheMatrix-results/10042.0_ZMM_13+ZMM_13TeV_TuneCUETP8M1_2017_GenSimFull+DigiFull_2017+RecoFull_2017+ALCAFull_2017+HARVESTFull_2017/step3_ZMM_13+ZMM_13TeV_TuneCUETP8M1_2017_GenSimFull+DigiFull_2017+RecoFull_2017+ALCAFull_2017+HARVESTFull_2017.log

136.731 step3
runTheMatrix-results/136.731_RunSinglePh2016B+RunSinglePh2016B+HLTDR2_2016+RECODR2_2016reHLT_skimSinglePh_HIPM+HARVESTDR2/step3_RunSinglePh2016B+RunSinglePh2016B+HLTDR2_2016+RECODR2_2016reHLT_skimSinglePh_HIPM+HARVESTDR2.log

20034.0 step3
runTheMatrix-results/20034.0_TTbar_14TeV+TTbar_14TeV_TuneCUETP8M1_2023D7_GenSimHLBeamSpotFull14+DigiFullTrigger_2023D7+RecoFullGlobal_2023D7+HARVESTFullGlobal_2023D7/step3_TTbar_14TeV+TTbar_14TeV_TuneCUETP8M1_2023D7_GenSimHLBeamSpotFull14+DigiFullTrigger_2023D7+RecoFullGlobal_2023D7+HARVESTFullGlobal_2023D7.log

9.0 step3
runTheMatrix-results/9.0_Higgs200ChargedTaus+Higgs200ChargedTaus+DIGI+RECO+HARVEST/step3_Higgs200ChargedTaus+Higgs200ChargedTaus+DIGI+RECO+HARVEST.log

25.0 step3
runTheMatrix-results/25.0_TTbar+TTbar+DIGI+RECOAlCaCalo+HARVEST+ALCATT/step3_TTbar+TTbar+DIGI+RECOAlCaCalo+HARVEST+ALCATT.log

10024.0 step3
runTheMatrix-results/10024.0_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2017_GenSimFull+DigiFull_2017+RecoFull_2017+ALCAFull_2017+HARVESTFull_2017/step3_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2017_GenSimFull+DigiFull_2017+RecoFull_2017+ALCAFull_2017+HARVESTFull_2017.log

10824.0 step3
runTheMatrix-results/10824.0_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2018_GenSimFull+DigiFull_2018+RecoFull_2018+ALCAFull_2018+HARVESTFull_2018/step3_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2018_GenSimFull+DigiFull_2018+RecoFull_2018+ALCAFull_2018+HARVESTFull_2018.log

50202.0 step3
runTheMatrix-results/50202.0_TTbar_13+TTbar_13+DIGIUP15_PU50+RECOUP15_PU50+HARVESTUP15_PU50/step3_TTbar_13+TTbar_13+DIGIUP15_PU50+RECOUP15_PU50+HARVESTUP15_PU50.log

25202.0 step3
runTheMatrix-results/25202.0_TTbar_13+TTbar_13+DIGIUP15_PU25+RECOUP15_PU25+HARVESTUP15_PU25/step3_TTbar_13+TTbar_13+DIGIUP15_PU25+RECOUP15_PU25+HARVESTUP15_PU25.log

21234.0 step3
runTheMatrix-results/21234.0_TTbar_14TeV+TTbar_14TeV_TuneCUETP8M1_2023D4_GenSimHLBeamSpotFull14+DigiFullTrigger_2023D4+RecoFullGlobal_2023D4+HARVESTFullGlobal_2023D4/step3_TTbar_14TeV+TTbar_14TeV_TuneCUETP8M1_2023D4_GenSimHLBeamSpotFull14+DigiFullTrigger_2023D4+RecoFullGlobal_2023D4+HARVESTFullGlobal_2023D4.log

23234.0 step3
runTheMatrix-results/23234.0_TTbar_14TeV+TTbar_14TeV_TuneCUETP8M1_2023D8_GenSimHLBeamSpotFull14+DigiFullTrigger_2023D8+RecoFullGlobal_2023D8+HARVESTFullGlobal_2023D8/step3_TTbar_14TeV+TTbar_14TeV_TuneCUETP8M1_2023D8_GenSimHLBeamSpotFull14+DigiFullTrigger_2023D8+RecoFullGlobal_2023D8+HARVESTFullGlobal_2023D8.log

@cmsbuild
Copy link
Contributor

Comparison not run due to runTheMatrix errors (RelVals and Igprof tests were also skipped)

…L1L2L3.

JPT needs CaloL1Offset and CaloL1Fastjet at the Level 1 corrections.
@cmsbuild
Copy link
Contributor

Pull request #17900 was updated. @perrotta, @cmsbuild, @slava77, @monttj, @davidlange6 can you please check and sign again.

@kodolova
Copy link
Contributor Author

Made change in JetMETCorrections/Configuration/python/JetCorrectorsAllAlgos_cff.py
There was an artefact with ak7JPTL1OffsetCorrector. Changed to ak7CaloL1OffsetCorrector.

@slava77
Copy link
Contributor

slava77 commented Mar 13, 2017

@cmsbuild please test

@kodolova
Copy link
Contributor Author

Correct me if I am wrong. This error has nothing to do with JetMETCorrections/Configuration.
An exception of category 'FatalRootError' occurred while
[0] Processing run: 1 lumi: 1 event: 1
[1] Running path 'pathALCARECOMuAlZMuMuGeneralTracks'
[2] Calling method for module TrackingMonitor/'ALCARECOMuAlZMuMuGeneralTracksTrackingDQM'
Additional Info:
[a] Fatal Root Error: @sub=TClingCallFunc::make_wrapper
Failed to compile

@slava77
Copy link
Contributor

slava77 commented Mar 14, 2017

@cmsbuild please test

error in 25.0 is apparently transient.

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 14, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/18429/console Started: 2017/03/14 22:53

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

@perrotta
Copy link
Contributor

@kodolova could you please attach here the address of a presentation (group meeting or anywhere else) in which the effect of this "bug fix" was shown and/or discussed?
Could you please also edit the title of this PR and modify it into something more descriptive, so that it will be more easily identified in the list of the PRs integrated in CMSSW?

@kodolova
Copy link
Contributor Author

There is a PAS that shows how to use L1Offset/Fastjet for JPT:https://cms.cern.ch/iCMS/analysisadmin/get?analysis=JME-14-005-pas-v30.pdf (page 3). L1JPTFastjet corrections should be done in the same way as L1JPTOffset. Otherwise it does not pickup ZSP corrections for JPT.

@kodolova kodolova changed the title JPTJECbugfixV2 L1JPTFastjetFix Mar 18, 2017
@kodolova
Copy link
Contributor Author

I renamed to L1JPTFastjetFix.

@slava77
Copy link
Contributor

slava77 commented Mar 18, 2017 via email

@kodolova kodolova changed the title L1JPTFastjetFix Fix for JPTFastjet correction chains Mar 18, 2017
)
ak4L1JPTFastjetCorrectorChain = cms.Sequence(
ak4CaloL1FastjetCorrector * ak4L1JPTFastjetCorrector
)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kodolova

I am wondering if this sequence is really used somewhere?
"ak4L1JPTFastjetCorrectorChain"

Regards,
Taejeong

@kodolova
Copy link
Contributor Author

This is the sequence for L1JPTFastjet corrections. Please, look to CorrectedJetProducers_cff.py
ak4JPTJetsL1 = cms.EDProducer(
'CorrectedJPTJetProducer',
src = cms.InputTag('JetPlusTrackZSPCorJetAntiKt4'),
correctors = cms.VInputTag('ak4L1JPTFastjetCorrector')
)
This is the correct producer for L1JPTFastjet offset.

@perrotta
Copy link
Contributor

@kodolova : this PR does not merge any more: could you please rebase and/or update it?
Furthermore: do you have any plot that shows the expected changes because of the fix implemented here? Or can you tell us what would you actually expect?

@kodolova
Copy link
Contributor Author

The reason of change is that JPTjets have the L1 corrections in two steps: firstly Calojets (part of JPTjet) are corrected for L1Offset or L1Fastjet and then corrections for zero suppression is done. Currently it is correctily implemented only for L1Offset. For chains that includes CaloL1Fastjet, zsp corrections are missed and this is 20% of jet energy scale.
Concerning rebase/update, I see that Configuration is completely changed. Thus, this is not a matter of rebase. I sent message to JetMET conveners and ask how to proceed.

@kodolova
Copy link
Contributor Author

I am closing this PR and open the new one.

@kodolova
Copy link
Contributor Author

The new PR is 18121

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants