Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PPS: AlCaReco producer, content filters and testing files #36273

Merged
merged 5 commits into from Feb 16, 2022

Conversation

grzanka
Copy link
Contributor

@grzanka grzanka commented Nov 28, 2021

PR description:

This PR adds a new AlCaReco producer to be used in PCL workflows for the PPS subsystem.

PR validation:

This PR was tested with Tests in Calibration/PPSAlCaRecoProducer/test.
Tests were performed on AOD-like Run2 (2018) data which should have the same format as the dataset required by PCL.

if this PR is a backport please specify the original PR and why you need to backport that PR:

N/A

FYI @fabferro @AndreaBellora @jan-kaspar @MatiXOfficial @ChrisMisan

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36273/26962

  • This PR adds an extra 40KB to repository

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @grzanka (Leszek Grzanka) for master.

It involves the following packages:

  • Calibration/PPSAlCaRecoProducer (****)

The following packages do not have a category, yet:

Calibration/PPSAlCaRecoProducer
Please create a PR for https://github.com/cms-sw/cms-bot/blob/master/categories_map.py to assign category

@cmsbuild can you please review it and eventually sign? Thanks.
@perrotta, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

@perrotta
Copy link
Contributor

perrotta commented Dec 1, 2021

assign alca

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 1, 2021

Pull request #36273 was updated. @cmsbuild, @malbouis, @tvami, @yuanchao, @francescobrivio can you please check and sign again.

@tvami
Copy link
Contributor

tvami commented Dec 1, 2021

assign alca

Oh so this PR was submitted 3 days ago? @perrotta @qliphy I think it's actually something that we need in 12_2_X, let me check with PPS

@tvami
Copy link
Contributor

tvami commented Dec 1, 2021

@cmsbuild , please test

@malbouis
Copy link
Contributor

malbouis commented Dec 1, 2021

A first general question about the integration plan. Is this new AlCaReco producer to be used for the already existing PCL workflows? Or would it be only for the AlCa Stream at a first moment?

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 1, 2021

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-92e153/20906/summary.html
COMMIT: e6ea381
CMSSW: CMSSW_12_2_X_2021-12-01-1100/slc7_amd64_gcc900
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/36273/20906/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 4 differences found in the comparisons
  • DQMHistoTests: Total files compared: 41
  • DQMHistoTests: Total histograms compared: 3041955
  • DQMHistoTests: Total failures: 5
  • DQMHistoTests: Total nulls: 1
  • DQMHistoTests: Total successes: 3041927
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: -0.004 KiB( 40 files compared)
  • DQMHistoSizes: changed ( 312.0 ): -0.004 KiB MessageLogger/Warnings
  • Checked 175 log files, 37 edm output root files, 41 DQM output files
  • TriggerResults: no differences found

@malbouis
Copy link
Contributor

malbouis commented Dec 1, 2021

@grzanka I think you also have to include this AlcaReco producer in https://github.com/cms-sw/cmssw/blob/master/Configuration/StandardSequences/python/AlCaRecoStreams_cff.py

@tvami
Copy link
Contributor

tvami commented Dec 1, 2021

assign alca

Oh so this PR was submitted 3 days ago? @perrotta @qliphy I think it's actually something that we need in 12_2_X, let me check with PPS

After liaising with PPS: we don't need to have this in 12_2_X

@grzanka
Copy link
Contributor Author

grzanka commented Dec 2, 2021

assign alca

Oh so this PR was submitted 3 days ago? @perrotta @qliphy I think it's actually something that we need in 12_2_X, let me check with PPS

After liaising with PPS: we don't need to have this in 12_2_X

I confirm, we don't need it at this moment for 12_2_X, as we don't have now the raw files (ALCARAW) on which this producer can be tested.
We only did some tests on raw data from Run2 (as in Calibration/PPSAlCaRecoProducer/test which is included in this PR).

@tvami
Copy link
Contributor

tvami commented Dec 6, 2021

Hi @grzanka have you had the chance to check #36273 (comment) ?

@smuzaffar smuzaffar removed this from the CMSSW_12_2_X milestone Dec 6, 2021
@tvami
Copy link
Contributor

tvami commented Feb 15, 2022

unhold

@cmsbuild cmsbuild removed the hold label Feb 15, 2022
@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-92e153/22433/summary.html
COMMIT: ead8252
CMSSW: CMSSW_12_3_X_2022-02-14-2300/slc7_amd64_gcc10
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/36273/22433/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 5 differences found in the comparisons
  • DQMHistoTests: Total files compared: 46
  • DQMHistoTests: Total histograms compared: 3764435
  • DQMHistoTests: Total failures: 13
  • DQMHistoTests: Total nulls: 1
  • DQMHistoTests: Total successes: 3764399
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.004 KiB( 45 files compared)
  • DQMHistoSizes: changed ( 312.0 ): 0.004 KiB MessageLogger/Warnings
  • Checked 193 log files, 42 edm output root files, 46 DQM output files
  • TriggerResults: no differences found

process.hltAOD.triggerResults = cms.InputTag("TriggerResults","","HLTX")
process.hltAOD.triggerEvent = cms.InputTag("hltTriggerSummaryAOD","","HLTX")
process.hltAOD.triggerName = cms.string("HLT_PPSMaxTracksPerRP4_v1")
process.hltAOD.stageL1Trigger = cms.uint32(2)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor comment: this makes the output of the unit test somewhat verbose: given the urgency perhaps can be followed up later.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point - it didn't look that bad in the terminal... :) We'll get back to it in the next PR.

@tvami
Copy link
Contributor

tvami commented Feb 15, 2022

Hi @MatiXOfficial I see

Last active module - label/type: hltBoolEnd/HLTBool [13 out of 0-13 on this path]
 'L3' filter in slot 5 - label/type hltL1sZeroBias/HLTL1TSeed
   0 accepted 'L3' objects found: 

in the output of the unit test. I see this 0 accepted 'L3' objects found: several times. Is that expected?

The producer looks fine tho
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-92e153/22433/unitTests/src/Calibration/PPSAlCaRecoProducer/test/testExpressPPSAlCaRecoProducer/testing.log

@tvami
Copy link
Contributor

tvami commented Feb 15, 2022

+alca

@MatiXOfficial
Copy link
Contributor

Hi @tvami,

From what I see these messages appear only in the log of testPromptPPSAlCaRecoOutput and the testExpressPPSAlCaRecoOutput is fine. They are produced only if this hltAOD marked by @mmusich is included in the process.

Since there is no rush this time, I'd prefer to postpone this discussion until next week, when @grzanka returns - unless @AndreaBellora knows something more.

@tvami
Copy link
Contributor

tvami commented Feb 15, 2022

Ok, @perrotta @qliphy feel free to review I dont have any further comments

@tvami tvami mentioned this pull request Feb 15, 2022
Copy link
Contributor

@perrotta perrotta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few more question and possible fixes, intended for a forthcoming PR which includes all them (possibly within pre6!)


from RecoPPS.Local.ctppsDiamondRecHits_cfi import ctppsDiamondRecHits as _ctppsDiamondRecHits
from RecoPPS.Local.ctppsDiamondLocalTracks_cfi import ctppsDiamondLocalTracks as _ctppsDiamondLocalTracks
ctppsDiamondRecHitsAlCaRecoProducer = _ctppsDiamondRecHits.clone(digiTag = cms.InputTag('ctppsDiamondRawToDigiAlCaRecoProducer','TimingDiamond'))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
ctppsDiamondRecHitsAlCaRecoProducer = _ctppsDiamondRecHits.clone(digiTag = cms.InputTag('ctppsDiamondRawToDigiAlCaRecoProducer','TimingDiamond'))
ctppsDiamondRecHitsAlCaRecoProducer = _ctppsDiamondRecHits.clone(digiTag = 'ctppsDiamondRawToDigiAlCaRecoProducer:TimingDiamond')

from RecoPPS.Local.totemTimingRecHits_cfi import totemTimingRecHits as _totemTimingRecHits
from RecoPPS.Local.diamondSampicLocalTracks_cfi import diamondSampicLocalTracks as _diamondSampicLocalTracks

totemTimingRecHitsAlCaRecoProducer = _totemTimingRecHits.clone(digiTag = cms.InputTag('totemTimingRawToDigiAlCaRecoProducer','TotemTiming'))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
totemTimingRecHitsAlCaRecoProducer = _totemTimingRecHits.clone(digiTag = cms.InputTag('totemTimingRawToDigiAlCaRecoProducer','TotemTiming'))
totemTimingRecHitsAlCaRecoProducer = _totemTimingRecHits.clone(digiTag = 'totemTimingRawToDigiAlCaRecoProducer:TotemTiming')

import FWCore.ParameterSet.Config as cms

process = cms.Process( "HLTX" )
process.load("setup_dev_CMSSW_12_1_0_GRun_V14_cff")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As I said, it is an overkill to dump a whole GRun menu only to access one (or a few) AlCa paths that you need for your test: please move to a lighter menu, and possibly a less obsolete version of it

'file:RelVal_Raw_GRun_DATA.root',
),
inputCommands = cms.untracked.vstring(
'keep *'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Normally scary for the event size... but ok, it is a test script...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that this is Source's inputCommands, i.e. for dropping some branches on input. Single keep * is redundant though, and for clarity the whole inputCommands PSet could be dropped.

function die { echo $1: status $2; exit $2; }

customise_commands="process.GlobalTag.toGet = cms.VPSet()\
\nprocess.GlobalTag.toGet.append(cms.PSet(record = cms.string(\"AlCaRecoTriggerBitsRcd\"),tag = cms.string(\"AlCaRecoHLTpaths_PPS2022_express_v1\"), connect = cms.string(\"frontier://FrontierProd/CMS_CONDITIONS\")))\
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these tags still not available in the GT?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They are, but they are added to the online GT, thus valid from 2022, i.e. it wont work on a replay with 2018 data. Everything with PPS will be just so much clearer when they collect their first data this year...

@perrotta
Copy link
Contributor

perrotta commented Feb 16, 2022

@cmsbuild
Copy link
Contributor

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. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2)

@perrotta
Copy link
Contributor

+1

  • Most of the updates are in the test area
  • Since this is apparently urgently needed, to be tested at P5 with pre5, let have it merged as such: but please follow up as soon as possible with the issues reported in the review, and summarized above

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet