-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36273/26962
|
A new Pull Request was created by @grzanka (Leszek Grzanka) for master. It involves the following packages:
The following packages do not have a category, yet: Calibration/PPSAlCaRecoProducer @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
assign alca |
@cmsbuild , please test |
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? |
Calibration/PPSAlCaRecoProducer/python/PPSAlCaRecoProducer_cff.py
Outdated
Show resolved
Hide resolved
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-92e153/20906/summary.html Comparison SummarySummary:
|
@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 |
Calibration/PPSAlCaRecoProducer/python/PPSAlCaRecoProducer_cff.py
Outdated
Show resolved
Hide resolved
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. |
Hi @grzanka have you had the chance to check #36273 (comment) ? |
unhold |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-92e153/22433/summary.html Comparison SummarySummary:
|
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) |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
Hi @MatiXOfficial I see
in the output of the unit test. I see this The producer looks fine tho |
+alca
|
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 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. |
There was a problem hiding this 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')) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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')) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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") |
There was a problem hiding this comment.
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 *' |
There was a problem hiding this comment.
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...
There was a problem hiding this comment.
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\")))\ |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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...
+operations
|
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) |
+1
|
PPSAlCaRecoProducer - minor fixes requested in #36273
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