cmssw: Possible misconfiguration of TrackingPOGFilters

The PR tests of (now merged) https://github.com/cms-sw/cmssw/pull/37134 for wfs 10804.31 and 10805.31 are showing at every event the following error messagges:

%MSG-w NoModule:   ByClusterSummaryMultiplicityPairEventFilter:toomanystripclus53X  28-Apr-2022 20:02:03 CEST Run: 1 Event: 1
No information for requested module 5. Please check in the Provinence Infomation for proper modules.
%MSG
%MSG-w NoModule:  ByClusterSummaryMultiplicityPairEventFilter:manystripclus53X  28-Apr-2022 20:02:03 CEST Run: 1 Event: 1
No information for requested module 5. Please check in the Provinence Infomation for proper modules.
%MSG

I did not verify whether this also happens in other workflows.

As pointed out by @mmusich in https://github.com/cms-sw/cmssw/pull/37134#issuecomment-1113011199, it looks like there’s something wrong with how the “tracking POG” filters in:

https://github.com/cms-sw/cmssw/blob/6d2f66057131baacc2fcbdd203588c41c885b42c/RecoMET/METFilters/python/trackingPOGFilters_cfi.py#L44-L58

are configured.

About this issue

Original URL
State: open
Created 2 years ago
Comments: 22 (22 by maintainers)

Most upvoted comments

It should be straightforward to suppress messages from particular category (NoModule in this case) already with something along

cmsDriver.py ... --customise_commands="process.MessageLogger.NoModule = dict(limit=0)"

(see https://github.com/cms-sw/cmssw/blob/master/FWCore/MessageService/Readme.md#suppressing-a-particular-category), but if the demand for such suppression starts to spread, perhaps some more specific structure in runTheMatrix.py infrastructure could be useful (@cms-sw/pdmv-l2).

makortel on May 16, 2022

Also to add here: since CMSSW_12_4 2022-04-29-2300 , there is an IB issue with 10805.31 @ssrothman Please have a check.

Let’s move this to a separate issue as the Triton issue has nothing to do with TrackingPOGFilters. I opened https://github.com/cms-sw/cmssw/issues/37767.

makortel on May 2, 2022

this is probably a tracker issue (clusterSummaryProducer is under the tracker )

there was a PR that drops empty detsets in the cluster collections #37035 @ferencek I guess this then leads to the clustersummary not seeing BPIX or other dets in the photon gun events, which then in turn leads to the warning.

@cms-sw/trk-dpg-l2

Hi @slava77, https://github.com/cms-sw/cmssw/pull/37035 drops empty DetSets from the pixel digi collection so the multiplicity of pixel clusters remains unchanged (after all, there is nothing to cluster from empty DetSets, more details in https://github.com/cms-sw/cmssw/pull/37035#issuecomment-1049601999). Hence, I don’t see how the issue reported here could be related to https://github.com/cms-sw/cmssw/pull/37035.

ferencek on Apr 29, 2022

this is probably a tracker issue (clusterSummaryProducer is under the tracker )

there was a PR that drops empty detsets in the cluster collections #37035 @ferencek I guess this then leads to the clustersummary not seeing BPIX or other dets in the photon gun events, which then in turn leads to the warning.

@cms-sw/trk-dpg-l2

slava77 on Apr 29, 2022

type trk

jpata on Apr 29, 2022