Error message for SiPixelPhase1TrackClusters DQM

[fabiocos]

I notice that the test log files in 10_2_X are filled in the (RECO,DQM) step with error messages

%MSG-e SiPixelPhase1TrackClusters: SiPixelPhase1TrackClusters:hltSiPixelPhase1TrackClustersAnalyzer 31-May-2018 11:01:00 CEST Run: 315489 Event: 47976080
incompatible configuration 27!=28
%MSG

check for instance wf 136.85 . This message comes from

https://cmssdt.cern.ch/lxr/source/DQM/SiPixelPhase1Track/plugins/SiPixelPhase1TrackClusters.cc#0105

[cmsbuild]

A new Issue was created by @fabiocos Fabio Cossutti.

@davidlange6, @Dr15Jones, @smuzaffar, @fabiocos can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[fabiocos]

assign dqm

[cmsbuild]

New categories assigned: dqm

@jfernan2,@vazzolini,@vanbesien,@kmaeshima,@dmitrijus you have been requested to review this Pull request/Issue and eventually sign? Thanks

[fabiocos]

In the move from pre3 to pre4 the message has changed from

%MSG-w SiPixelPhase1TrackClusters: SiPixelPhase1TrackClusters:hltSiPixelPhase1TrackClustersAnalyzer 05-Jun-2018 12:05:58 CEST Run: 1 Event: 4
PixelClusterShapeCache collection is not valid
%MSG

to

%MSG-e SiPixelPhase1TrackClusters: SiPixelPhase1TrackClusters:hltSiPixelPhase1TrackClustersAnalyzer 05-Jun-2018 12:05:25 CEST Run: 1 Event: 3
incompatible configuration 27!=28
%MSG

I think that the cause for these messages should be anyway removed at the root, having the log files plenty of them makes difficult to catch new problems, besides it looks clear that there are pieces of software that do not work properly

[boudoul]

sounds like a deja-vu (even multiple dejavu) sigh ... maybe this thread could help https://groups.cern.ch/group/cms-hlt/Lists/Archive/DispForm.aspx?ID=2999

[fioriNTU]

@fabiocos (@jandrea and @arossi83) this is the usual issue with the HLT monitoring of PixelPhase1. My guess is that e new plot has been added to the Phase1TrackCluster plugin but has not been added in the corresponding HLT DQM configuration (and disabled there). As far as I know TkDQM is already working to provide a completely independent HLT plugin in a way to avoid this kind of things forever

[fabiocos]

@fioriNTU @boudoul @jandrea @arossi83 thanks for the comments, do you know when is this plugin expected to arrive? It will be in time for CMSSW_10_2_0_pre6?

[arossi83]

@fabiocos most probably it will be not ready for CMSSW_10_2_0_pre6, we will provide a FIX for this in time for CMSSW_10_2_0_pre6 @jandrea @fioriNTU

[fabiocos]

The PR #23575 "fixes" the LogError problem, but it does not solve ultimately the problem as the module is still not executed (producing a new LogWarning message). Therefore I keep this issue open to track the continuation of the work needed to finally clean up the use of this DQM code.

[fioriNTU]

@fabiocos this issue should be solved by PR #23576 , can we close it?

[fabiocos]

@fioriNTU that specific problem looks gone, yes, I close the issue