-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
HLT menu development for 13_0_X (branch: 13_2_X)
Development of HLT menus for `CMSSW_13_0_X`. This update includes the integration of the following JIRA tickets. - [CMSHLT-2820](https://its.cern.ch/jira/browse/CMSHLT-2820): [EXO] tighter isolation cut on L2Taus in displaced-tau trigger (and addition of backup trigger) - [CMSHLT-2836](https://its.cern.ch/jira/browse/CMSHLT-2836): [TSG] addition of looser L1T seeds to dilepton Scouting triggers - [CMSHLT-2862](https://its.cern.ch/jira/browse/CMSHLT-2862): [TRK,ECAL] use only CPU products in CPU branch of `DQMGPUvsCPU` triggers - [CMSHLT-2867](https://its.cern.ch/jira/browse/CMSHLT-2867): [EXO] remove Tracker-HV filters in calo-only LLP triggers - [CMSHLT-2872](https://its.cern.ch/jira/browse/CMSHLT-2872): [SMP] looser DiTau trigger for W-3pi search (plus control trigger) - [CMSHLT-2873](https://its.cern.ch/jira/browse/CMSHLT-2873): [AlCa] set smartPS=2 for `HLT_Physics_v` in `ExpressPhysics` PD - [CMSHLT-2874](https://its.cern.ch/jira/browse/CMSHLT-2874): [EXO,HIG] new VBF-parking triggers without PFJet-CHF cut - [CMSHLT-2875](https://its.cern.ch/jira/browse/CMSHLT-2875): [EXO] triggers for displaced mu-tau and e-tau final states - [CMSHLT-2877](https://its.cern.ch/jira/browse/CMSHLT-2877): [GEM] save GEM `FEDRawData` in `RPCMON` stream - [CMSHLT-2878](https://its.cern.ch/jira/browse/CMSHLT-2878): [TRK] add pixel-doublet-recovery iteration to standard tracking sequence, and disable track-looper reconstruction
- Loading branch information
Showing
15 changed files
with
9,627 additions
and
1,030 deletions.
There are no files selected for viewing
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
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
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
Oops, something went wrong.