Open patinkaew opened 2 months ago
cms-bot internal usage
A new Issue was created by @patinkaew.
@Dr15Jones, @antoniovilela, @makortel, @mandrenguyen, @rappoccio, @sextonkennedy, @smuzaffar can you please review it and eventually sign/assign? Thanks.
cms-bot commands are listed here
assign xpog
New categories assigned: xpog
@ftorrresd,@hqucms you have been requested to review this Pull request/Issue and eventually sign? Thanks
I would like to start a discussion. I noticed that Dataset branch has been created since NanoAODv13 [1] and I'm not sure whether this is what we expect. I believe Dataset branch is added because introduction of ScoutingNano since only branches in Dataset are Scouting datasets (ScoutingPFRun3, ScoutingPFMonitor). They seems to be added unintentionally at, for example, [2] since Scouting paths started with
DST
, notL1
orHLT
, e.g.DST_PFScouting_JetHT_v*
.The question: should we keep Dataset branch or drop it?
HLT
flags which are already stored in NanoAOD.Scouting
as it is currently done, we can check that the flag starts withDST
and containsScouting
. Checking Scouting paths on HLT-Scouting wiki [3], I believe this condition should pick up all Scouting paths used in 2022-2024.[1] https://cms-nanoaod-integration.web.cern.ch/autoDoc/ [2] https://github.com/cms-sw/cmssw/blob/master/PhysicsTools/NanoAOD/plugins/TriggerOutputBranches.cc#L25 [3] https://cms-hlt-scouting.docs.cern.ch/PathsRecoContent/Paths/