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 Puppi MET and smearing MET correction, add central test for the MET tool #13954
Conversation
A new Pull Request was created by @mmarionncern for CMSSW_8_0_X. It involves the following packages: PhysicsTools/PatAlgos @cmsbuild, @cvuosalo, @slava77, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
@cmsbuild please test |
The tests are being triggered in jenkins. |
@slava77 those fixes are quite minor ones, no problem of not having them super-soon |
-1 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 ----- Begin Fatal Exception 06-Apr-2016 15:22:37 CEST----------------------- An exception of category 'InvalidInput' occurred while [0] Processing run: 1 lumi: 1 event: 1 [1] Running path 'validation_step1' [2] Calling event method for module METTester/'pfPuppiMetAnalyzerMiniAOD' [3] Calling produce method for unscheduled module PATMETSlimmer/'slimmedMETsPuppi' [4] Calling produce method for unscheduled module CorrectedPATMETProducer/'patPFMetT1JetEnUpPuppi' [5] Calling produce method for unscheduled module ShiftedParticleMETcorrInputProducer/'shiftedPatMETCorrJetEnUpPuppi' [6] Calling produce method for unscheduled module ShiftedPATJetProducer/'shiftedPatJetEnUpPuppi' Exception Message: cannot find key 9 in the JEC payload, this usually means you have to change the global tag ----- End Fatal Exception ------------------------------------------------- you can see the results of the tests here: |
could we split off the part that affects miniAOD production from the one that does not? I don't like the idea of producing miniAOD v2 mainly to put in some new JECs, but do that with a release that applies them wrongly. |
The matrix test fails due to the use of the GT pointed by " auto:run2_mc_50ns" which does not contains the Puppi JEC. I don't know what is the proper action to take : should they be added to that GT or should the _50ns be removed from the GT pointer (the matrix test works with auto:run2_mc)? |
The changes affecting the miniAOD production is half of the PR in term of changes : The other ones are just and update of the test files and a new unit test. The separation between both is feasible, but it means I will have to split the single commit we have right now. |
@mmarionncern, just to clarify, PUPPI JEC for 50ns do exist. Only uncertainties are not available. |
On 4/7/16 4:01 AM, Marco Musich wrote:
To the first order, I'd supply the same as for 25ns.
|
From a previous thread with @blinkseb: "concerning the issue with uncertainties, it seems the database we use for 50ns does not contains the uncertainties for all the jets collection, but only for AK4PFchs. I'll update this database so that if we need another GT for 2015 the 50ns uncertainties are included for all jet collections." Marco |
Indeed ;) It's fairly easy to do, but should I request the creation of a new 50ns GT? Or maybe the new feature of creating private GT can be useful in this case? |
@blinkseb go ahead and create the self-GT for this purpose! once we've seen this PR works we'll update queues and autoCond. thanks |
Self-GT created: Is there something else I need to do on my side? |
@blinkseb no, thanks! @mmarionncern needs to change his version of autoCond.py in this PR and re-run the tests |
@cmsbuild please test |
The tests are being triggered in jenkins. |
+1 Fixing PUPPI MET in Mini-AOD. The code changes are satisfactory. Jenkins tests against baseline CMSSW_8_0_X_2016-04-12-2300 show only the expected differences in PUPPI MET. An extended test of workflow 25202.0_TTbar_13 with 70 events against baseline CMSSW_8_0_X_2016-04-07-2300 also shows only the expected small differences from the MET fix. RECO event content does not change, and Mini-AOD event content changes only very slightly:
|
+1 |
It looks like this PR broke 50 ns run2 and run 1 workflows with PAT. |
@slava77 are you referring to this:
we need the 50ns uncertainty propagated everywhere we need it (i.e. both run2 50ns data and run1 data) |
@blinkseb do you think it would be feasible to get the 50ns IOVs of Run2 data and Run1 data fixed adding the uncertainties? |
@mmusich Yes sure, I'm doing it right now. For Run1 data, is there an issue using for example CMSSW 8.0.X to create the database? |
@blinkseb we are using the I see:
we need therefore a new payload for the IOV [1-25300] and also for the 50ns ones covering run2 data (I think you have the correct boundaries) |
Ok great, thanks a lot! Should I create a self-GT for this one, or request a new GT as usual via the hypernews? |
please queue them and announce when done. I'll cut the new GT and make the PR, from the ORP today I understand it's kind of urgent. Thanks, |
@mmusich Announcement done: https://hypernews.cern.ch/HyperNews/CMS/get/calibrations/2300.html I hope it'll be ok! |
This PR fixes only configuration : the computation of the puppiMET in the miniAOD production, now using the proper jet energy corrections for the puppiMET and a small inconsistency in the MET smearing correction have been also added.
A central test for the MET tool has been added, in order to avoid conflicts such as the one seen with the update of the PAT names few weeks ago.
Few internal variable names were also modified.
The miniAOD to miniAOD MET reprocessing example test file has been updated and a test file for the MET production from AOD has been added.
Packages impacted by this PR :
Changes :