-
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
Update of the LumiPCC module veto list and afterglow factors for 2024 data-taking #44567
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SoA range checking: adds inter operability between range checked and non range checked [14.0.x]
…fBramVal_from1400pre3 Implement the GSF Track fBrem Variable Filling for Scouting Electrons: 14_0
…attacharya with cms-merge-topic
…ase2 [14.0.X] miscellaneous updates to improve validation of phase-2 Tracker Alignment samples
…co_muon_selection [14.0.X] add phase2 customizations to `TkAlMuonSelectors` to increase selection efficiency
Migration to ConfDb 14_0_0_pre3 template and addOnTests bug fix [14_0_X]
…ving some of the gaps (backport of cms-sw#43903)
…terizerInZ [14.0.X] fix `DAClusterizerInZ_vect` for `ASAN_X` build
…dExceptionFix Implementation of TauWPThreshold without need to catch exceptions [14_0_X]
[14.0.X] Fix Phase2 ditau HLT path (with DeepTau Isolation)
Backport [14_0]: Add low pt muon fix objects into phase 2 L1 event content.
…QuickFix Backport track jet eta quick fix
…-L1-GT-emulator_14_0_0_X_backport [14_0_X] [backport] [Phase-2] Change Phase-2 HLT Egamma paths to use the GT emulator
…rDisplacedEg [14_0_X backport] Produce sMajor, sMinor in EgammaHLTClusterShapeProducer
Phase2-hgx353X Add a new scenario 2026D109 utilizing the V18 version of HGCAL after removing some of the gaps (backport of cms-sw#43903)
Follow up to the Alpaka integration in CMSSW [14.0.x]
Update Alpaka to version 1.1.0 [14.0.x]
Add support to multi layout portable collections (up to 5) [14.0.x]
… version of GE21 geometry
Configuration arguments for version and packing schema of covariance in DeepJetTag producer [14_0_X]
…risonFilter_14_0_X [14.0.X] update `HLTPPSJetComparisonFilter` to use `LHCInfoCombined`
[14.0.X] Introduce HCAL only workflows using Alpaka-based PF clustering
…ate_forV03-01-01_backport140X [14.0.X] Backport - Refactor scatterer addition in aGblPoint to explicitly specify type for scatPrecision.inverse()
[CMSSW_14_0_X ] Fix tag for the SiPixelLorentzAngleSimRcd in the Phase2 MC GT
…ewTriggerBits_backup Backport of New Trigger Filter Bits for Muon POG NanoAOD
[14_0_X] Hack `EgammaHLTR9IDProducer` to be able to run it in Phase2 HLT
[14.0.X] EL9-migration related patches to All-in-one
…mix stage2 The PixelFEDChannelCollection produced by the MixingModule in premix stage2 is not used at all so there is no point is creating it. Another PixelFEDChannelCollection is produced later by the DataMixer and propagated to tracking (after undergoing DigiToRaw and RawToDigi steps).
Up to now permanently bad components were killed prior to the DataMixer and separately for signal and pileup. For pileup this was happening in the MixingModule in stage 1 premixing and for signal in the MixingModule in stage 2 premixing. Instead, killing of transiently bad components was deferred to the last step in the DataMixer where signal and pileup digis are mixed. With this commit both permanently and transiently bad pixel components are killed in one place, in the DataMixer. This way premixed pileup library can be produced even before the list of bad components has been finalized and can later be reused with different bad component scenarios.
MSSM Hbb trigger dqm updates for 2024 triggers [14.0.X]
…ps_14_0_X [14.0.X] add input / output LA `TkDetMaps` in `SiStripLorentzAnglePCLHarvester`
…t_simulation_update Update for simulation of pixel bad components
…ne_14_0_X [14.0.X] Miscellaneous fixes for dqm online clients
This PR contains too many commits (263 >= 240) and will not be processed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR description:
Update of the LumiPCC module veto list and afterglow parameters implemented in the corresponding configuration files. The parameters and the veto are defined by studying the reprocessed 2023 data. The workflow remains unchanged. Similar changes have been submitted for 2023 #41242 #41256
PR validation:
Validated by running runTheMatrix.py -l 1020.0 configuration.
Backport will be requested later