Inconsistency in ALCARECOHcal paths

[Dr15Jones]

The new schedule consistency checker, #34735 , found the following problem in RelVal 1000.0

----- Begin Fatal Exception 03-Aug-2021 23:03:32 CEST-----------------------
An exception of category 'ScheduleExecutionFailure' occurred while
   [0] Calling beginJob
Exception Message:
Unrunnable schedule
Paths are non consistent
  module 'ALCARECOHcalCalPhisymDQM' depends on 'hbherecoNoise' which appears on paths
  pathALCARECOHcalCalMinBias 
but is missing from
  pathALCARECOHcalCalIterativePhiSym 
----- End Fatal Exception -------------------------------------------------

looking at the configuration, hbherecoNoise only appears on pathALCARECOHcalCalMinBias which means pathALCARECOHcalCalIterativePhiSym can not operate without that other path being present.

[Dr15Jones]

assign alca

[cmsbuild]

New categories assigned: alca

@francescobrivio,@tvami,@malbouis,@pohsun,@tlampen,@yuanchao you have been requested to review this Pull request/Issue and eventually sign? Thanks

[cmsbuild]

A new Issue was created by @Dr15Jones Chris Jones.

@Dr15Jones, @perrotta, @dpiparo, @silviodonato, @smuzaffar, @makortel, @qliphy can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[Dr15Jones]

The configuration fragments are

cmssw/Calibration/HcalAlCaRecoProducers/python/ALCARECOHcalCalMinBias_cff.py

Line 68 in 6d2f660

seqALCARECOHcalCalMinBias = cms.Sequence(hbherecoMBNZS*horecoMBNZS*hbherecoNoise*hfrecoNoise*hfrecoMBNZS*horecoNoise)

cmssw/Configuration/StandardSequences/python/AlCaRecoStream_Specials_cff.py

Line 47 in 6d2f660

pathALCARECOHcalCalMinBias = cms.Path(seqALCARECOHcalCalMinBiasDigi*seqALCARECOHcalCalMinBias*ALCARECOHcalCalPhisymDQM)

cmssw/Configuration/StandardSequences/python/AlCaRecoStreams_cff.py

Line 218 in cfbe413

pathALCARECOHcalCalIterativePhiSym = cms.Path(seqALCARECOHcalCalIterativePhiSym*ALCARECOHcalCalPhisymDQM)

[tvami]

Hi @bsunanda can you please look into this? Thanks!

[Dr15Jones]

One thing to know, the Paths pathALCARECOHcalCalMinBias and pathALCARECOHcalCalIterativePhiSym both start with different filters. If the filter on Path pathALCARECOHcalCalMinBias fails and the filter on path pathALCARECOHcalCalIterativePhiSym succeeds, then when ALCARECOHcalCalPhisymDQM is called, the EDAnalyzer will fail to get the data products it needs (since they were only defined on Path pathALCARECOHcalCalMinBias).

[bsunanda]

The two paths produce different outputs and the same DQMAnalyzer should not be used for both. I am trying to see if a second DQM analyzer can be made for pathALCARECOHcalCalIterativePhiSym

[bsunanda]

Submitted a PR #34784 to resolve this issue.

[perrotta]

As this isssue is fixed by #34784, it can probably be signed and closed

[francescobrivio]

+alca

[cmsbuild]

This issue is fully signed and ready to be closed.