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 CSCCluster skim config #37782
Add CSCCluster skim config #37782
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-37782/29688
|
A new Pull Request was created by @kakwok for master. It involves the following packages:
@cmsbuild, @bbilin, @kskovpen, @jordan-martins can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Hi @kakwok
However, the resulting unskimmed file is 8.7GB and the skimmed file is 39 MB. |
Hi @sam7k9621 , Yes, those are the 4 root files I used, but I didn't run over all the events in the file. |
Hi @sam7k9621 Can this be merged now? |
please test |
paths = (EXOCSCClusterPath), | ||
content = skimRawAODContent.outputCommands+['keep *_csc2DRecHits_*_*','keep *_dt1DRecHits_*_*'], | ||
selectEvents = cms.untracked.PSet(), | ||
dataTier = cms.untracked.string('AOD') |
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.
it doesn't seem that "AOD" is the correct data tier for this event content...
Also by changing skimRawAODContent here, you change it for everyone. If that is intended, the additional keep statements should go instead into Configuration.Skimming.PDWG_cff.py
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.
I think I'm just taking the value of skimRawAODContent
output command and adding the extra collections that I need here, which shouldn't change what's in skimRawAODContent
for everyone?
What should I put for the data tier here then?
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.
Ah. - yes, you are correct I agree. I'm not sure what naming convention is being followed for raw+aod skims. (Hopefully it is not AOD)?
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.
I followed the convention in this PR (similar skim for DTClusters):
https://github.com/cms-sw/cmssw/pull/37509/files
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.
@kskovpen so it this really supposed to be AOD
after all?
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.
I think it can be modified as "USER" to follow EXODisplacedJet
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.
(hmm it's not supposed to be my business, but since I'm following the PR...) isnt USER
only meant for private productions from the users? I saw the other skims mostly use RAW-RECO
, why shouldnt this use that too?
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.
In my understanding, different “types” only affect how it will be categorized in the DAS.
Since it shares the same content with EXODisplacedJet, I think we can follow the settings
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.
IMO this should be USER
, it's AOD
with customized event content.
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.
@kakwok please modify it to USER
then
) | ||
|
||
# Additional output definition | ||
process.SKIMStreamEXOCSCCluster = cms.OutputModule("PoolOutputModule", |
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.
implemented this way, the test does not test the skim as defined in the cffs above.
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.
Hi David, what's the right way to do so then?
the script is generated with the cmsDriver command as stated in the config:
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.
Right, cmsDriver doesn't quite do this for you - eg, you can instead import the output module configuration from your cff and use it.
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.
Hi @davidlange6 It's fixed now
3515db5
unhold
|
@cmsbuild , please test |
@kakwok can you please also prepare the 12_4_X backport of this PR? thanks! |
Not for this PR, but
This should be made a unit test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-37782/31172
|
Pull request #37782 was updated. @bbilin, @kskovpen, @jordan-martins can you please check and sign again. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ecd84a/26361/summary.html Comparison Summary@slava77 comparisons for the following workflows were not done due to missing matrix map:
Summary:
|
+pdmv |
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, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
CSCClusterTrigger = HLTrigger.HLTfilters.hltHighLevel_cfi.hltHighLevel.clone() | ||
CSCClusterTrigger.TriggerResultsTag = cms.InputTag( "TriggerResults", "", "HLT" ) | ||
CSCClusterTrigger.HLTPaths = cms.vstring( | ||
["*CscCluster*","*L1CSCShower*"] | ||
) | ||
CSCClusterTrigger.throw = False | ||
CSCClusterTrigger.andOr = True |
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.
Not for this PR, but for a possible cleaning in another PR:
CSCClusterTrigger = HLTrigger.HLTfilters.hltHighLevel_cfi.hltHighLevel.clone() | |
CSCClusterTrigger.TriggerResultsTag = cms.InputTag( "TriggerResults", "", "HLT" ) | |
CSCClusterTrigger.HLTPaths = cms.vstring( | |
["*CscCluster*","*L1CSCShower*"] | |
) | |
CSCClusterTrigger.throw = False | |
CSCClusterTrigger.andOr = True | |
CSCClusterTrigger = HLTrigger.HLTfilters.hltHighLevel_cfi.hltHighLevel.clone( | |
TriggerResultsTag = ( "TriggerResults", "", "HLT" ), | |
HLTPaths = ["*CscCluster*","*L1CSCShower*"], | |
throw = False, | |
andOr = True | |
) |
+1 |
PR description:
This PR adds the config for a RAW-AOD skim for the CSC clusters events, based on new LLP trigger paths.
The CSC cluster skim saves the following collections in addition to standard RAW-AOD output:
The CSC cluster skim selects events passing the following HLT paths, which is already included in the HLT v2 menu:
HLT Jira ticket
PR validation:
Tested with a high-Pt QCD sample in
CMSSW_12_4_0_pre3
The skimmed file size for was 12MB, and the size of the unskimmed AOD file was 1.9GB with 1951 events.
The test script (
test_CSCCluster_cfg.py
), generated withcmsDriver
, is attached in the PR.