BadPFMuonDzFilter removed by mistake + fix the nanoFlag "Flag_METFilters"

[mariadalfonso]

discussed here https://hypernews.cern.ch/HyperNews/CMS/get/JetMET/2113.html problem introduced here for the ULminiV2

https://github.com/cms-sw/cmssw/pull/31087

[lathomas]

Hello. Just to clarify because there are several things:

• the filter discussed in that HN thread is BadPFMuonFilter (without DZ, the one with DZ is ok). A cosmetic update of CMSSW is needed that shouldn't have any impact on data formats.
• Checking https://github.com/cms-sw/cmssw/pull/31087 BadPFMuonDzFilter was indeed not added to NANOAOD (and is therefore not present in UL NANOv2). That requires a (simple) PR prior to ULNanov3

[mariadalfonso]

@lathomas we should profit to check that all the flags are there;

https://cms-nanoaod-integration.web.cern.ch/integration/cms-swmaster/mc106Xul16_doc.html#Flag

also the Flag_METFiltersis broken, can we fix it ? https://twiki.cern.ch/twiki/bin/view/CMS/MissingETOptionalFiltersRun2#Analysis_Recommendations_for_ana

[lathomas]

Hello, I can confirm that when BadPFMuonDzFilter is present in MINIAOD (which is the case for MINIAOD v2 but not v1), the corresponding bool is saved in NANOAOD. In other words, the bool will be there for NanoV9 (but is absent from V8)

[gouskos]

Thanks @lathomas

[alkaloge]

It actually seems that there must be also nAODv9 MC datasets that the BadPFMuonDzFilter is missing like this one /WJetsToLNu_HT-70To100_TuneCP5_13TeV-madgraphMLM-pythia8/RunIISummer20UL18NanoAODv9-106X_upgrade2018_realistic_v16_L1v1-v1/NANOAODSIM

[mariadalfonso]

@alkaloge and @lathomas

this seems easy to fix for te early run3 nano. Can you have a look and make a PR ?

[vlimant]

closing the loops : @alkaloge and @lathomas can we consider this past history ?