add sequence for HLTDQM only step on AOD

[mtosi]

add a new sequence offlineHLTSourceOnAOD
which is meant to be used via cmsDriver command, like -s DQM:offlineHLTSourceOnAOD,
for running the HLT DQM on AOD files
(w/o the need of running the RECO step on the fly)

the standard sequence offlineHLTSource used by almost all the workflows w/ the DQM step
is now defined as the sum of
the offlineHLTSourceOnAOD one
plus the modules/sequences which need to access to transient collections
(for instance the HCAL monitoring hcalMonitoringSequence and jetMETHLTOfflineAnalyzer)

no differences w.r.t. current DQM are expected

[cmsbuild]

The code-checks are being triggered in jenkins.

[cmsbuild]

A new Pull Request was created by @mtosi (mia tosi) for master.

It involves the following packages:

DQMOffline/Trigger

@kmaeshima, @cmsbuild, @vanbesien, @vazzolini, @dmitrijus can you please review it and eventually sign? Thanks.
@battibass, @jhgoh, @calderona, @HuguesBrun, @trocino, @rociovilar this is something you requested to watch as well.
@davidlange6, @slava77 you are the release manager for this.

cms-bot commands are listed here

[mtosi]

@cmsbuild, please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/22602/console Started: 2017/08/30 21:29

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/PR-20322/401

[cmsbuild]

+1
Tested at: 7b1558c
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20322/22602/summary.html

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
60ea8c8
You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20322/22602/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20322/22602/git-merge-result

[cmsbuild]

Comparison job queued.

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20322/22602/summary.html

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 0 differences found in the comparisons
• DQMHistoTests: Total files compared: 26
• DQMHistoTests: Total histograms compared: 2653934
• DQMHistoTests: Total failures: 202
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 2653543
• DQMHistoTests: Total skipped: 189
• DQMHistoTests: Total Missing objects: 0
• Checked 107 log files, 14 edm output root files, 26 DQM output files

[dmitrijus]

+1

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar (and backports should be raised in the release meeting by the corresponding L2)

[davidlange6]

for this to work for more than a few releases, it needs a test in runTheMatrix - @fabozzi could you look into doing that with @mtosi ?

[fabozzi]

ok, we will follow-up with Mia for that

[mtosi]

uhmm I'm not sure we need a relval, now this sequence is meant to make the step DQM:HLTonly be able to run on AOD, without the need of running the RECO step the main goal is the validation of the HLT menu (see my email on the HLT v3 validation) but I might not totally get your question

…

On 6 Sep 2017, at 18:03, fabozzi ***@***.***> wrote: ok, we will follow-up with Mia for that — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[mtosi]

I'm using it by doing the following

cmsDriver.py hltdqm -s DQM:offlineHLTSourceOnAOD --conditions=92X_dataRun2_Prompt_v8 --geometry DB:Extended --eventcontent DQM --datatier DQMIO --data --era Run2_2017 --filetype=EDM --filein root://eoscms.cern.ch//eos/cms/tier0/store/da
ta/Run2017D/HLTPhysics/AOD/PromptReco-v1/000/302/043/00000/CA7873CD-678F-E711-9376-02163E01429E.root -n 100 --fileout DQM_onlyHLT.root

[davidlange6]

hi @mtosi - right - but if this functionality is not tested regularly it will break. So having a simple cmsDriver that reads aod and runs this sequence each IB means that any problems will be caught and reported. you cmsDriver is whats needed by @fabozzi. thx.

[davidlange6]

+1