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

Add HCAL LLP Jet Skim config #41111

Closed
wants to merge 95 commits into from

Conversation

kennedykiley
Copy link

PR description:

This PR adds the config for a RAW-AOD skim for HCAL-based LLP candidate events, based on new LLP trigger paths.
The HCAL RecHit skim saves the following collections in addition to standard RAW-AOD output:

HBHERecHit (via 'keep *_hbhereco__*')

The HCAL RecHit skim selects events passing the following HLT paths, which are included in the prompt HLT menu:

HLT*_L1SingleLLPJet_*

LLP HLT Jira Ticket

PR validation:

Tested with the following 2022 data samples in CMSSW_12_4_0_pre1:

/DisplacedJet/CMSSW_12_4_11-124X_dataRun3_Prompt_v4_gtval_RelVal_2022D-v1/RECO

The skimmed file event size was 0.7 MB (87 total events) and the unskimmed file was 3.2 GB (1000 total events).

The test script, generated with cmsDriver, is on lxplus: /afs/cern.ch/user/k/kikenned/public/Skims/2023-03-20/test_EXOLLPJetHCAL_SKIM.py

@tvami
Copy link
Contributor

tvami commented Mar 23, 2023

Hello! Thanks for your comments and suggestions. I've rebased my branch with the official master & added a PR for 13_0_X.

You should have rebased to 13_1_X not 13_0_X

@tvami
Copy link
Contributor

tvami commented Mar 23, 2023

-1

  • rebase to 13_0_X brought in alca signature

@menglu21
Copy link
Contributor

sorry but 276 files are updated?

@aloeliger
Copy link
Contributor

-1

  • Duplicate L1 commits

@kennedykiley did you use cms-merge-topic instead of cms-rebase-topic? These are all duplicate commits.

@bsunanda
Copy link
Contributor

-1

@emanueleusai
Copy link
Member

-1

  • remove from dqm queues

@missirol
Copy link
Contributor

@kennedykiley , please do a proper rebase, or close this PR and open a new one.

@kennedykiley
Copy link
Author

I'm very sorry about all the issues I inadvertently caused in the PR with my improper rebase. Closing now -- I'll open a fresh PR started from the latest release. Thanks for everyone's help and feedback!

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