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.

Sign up for GitHub

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

Jump to bottom

Add a workaround for AlCa paths to the Patatrack customisation #35566

Merged
merged 1 commit into from
Oct 8, 2021
Merged

Add a workaround for AlCa paths to the Patatrack customisation #35566

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
26 changes: 26 additions & 0 deletions HLTrigger/Configuration/python/customizeHLTforPatatrack.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -217,6 +217,32 @@ def customisePixelLocalReconstruction(process):
process.HLTDoLocalPixelSequence = cms.Sequence(process.HLTDoLocalPixelTask)


# workaround for AlCa paths

if 'AlCa_LumiPixelsCounts_Random_v1' in process.__dict__:
Copy link
Contributor

Choose a reason for hiding this comment

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

"v1" because newer versions are / will be already fixed: correct?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

hopefully :-)

Copy link
Contributor

Choose a reason for hiding this comment

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

Well, we have NOt increased version numbers for a long time now...

Copy link
Contributor

Choose a reason for hiding this comment

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

So I understand this should go into ConfDB as an update to the paths in 12_1?

Copy link
Contributor

Choose a reason for hiding this comment

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

ie, for both cpu and gpu

Copy link
Contributor

Choose a reason for hiding this comment

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

and then it should be an overall customisation until then (ie, in customiseHLTforCMSSW)?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I assume we are getting close to migrating the whole menu to the Task-enabled ConfDB; when that happens, this change can be applied there directly.
Until then, we can stay at "v1"...

# redefine the path to use the HLTDoLocalPixelSequence
process.AlCa_LumiPixelsCounts_Random_v1 = cms.Path(
process.HLTBeginSequenceRandom +
process.hltScalersRawToDigi +
process.hltPreAlCaLumiPixelsCountsRandom +
process.hltPixelTrackerHVOn +
process.HLTDoLocalPixelSequence +
process.hltAlcaPixelClusterCounts +
process.HLTEndSequence )

if 'AlCa_LumiPixelsCounts_ZeroBias_v1' in process.__dict__:
# redefine the path to use the HLTDoLocalPixelSequence
process.AlCa_LumiPixelsCounts_ZeroBias_v1 = cms.Path(
process.HLTBeginSequence +
process.hltScalersRawToDigi +
process.hltL1sZeroBias +
process.hltPreAlCaLumiPixelsCountsZeroBias +
process.hltPixelTrackerHVOn +
process.HLTDoLocalPixelSequence +
process.hltAlcaPixelClusterCounts +
process.HLTEndSequence )


# done
return process

Expand Down