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

Improved L1T Integration Testing #163

Open
mulhearn opened this issue Feb 18, 2016 · 1 comment
Open

Improved L1T Integration Testing #163

mulhearn opened this issue Feb 18, 2016 · 1 comment
Labels

Comments

@mulhearn
Copy link
Member

Now that we have a nominally working product, we need to scale up our L1T integration testing to be more stringent to reduce regressions. We want fast tests which test all core functionality. For now keeping track of good tests as they come to mind:

  • Unity of the DIGITORAW + RAWTODIGI sequence
  • Unity of L1 + DIGITORAW + RAWTODIGI + RE-EMULATION
  • Something with L1REPACK... Unity after SIM?
  • HLT tests, to make sure we don't break HLT work flows.
  • Coarse check of efficiency and rate.
  • CMSSW config file checks via runTheMatrix -l limited --command=--no_exec and maybe calling
    python on results.

Feel free to suggest new tests.

At the moment, the regimen is simply the following tests

cmsRun L1Trigger/L1TCommon/test/runL1T.py
cmsRun L1Trigger/L1TCommon/test/reEmul.py
cmsRun L1Trigger/L1TCommon/test/runStandardSequences.py

Plus calo dev teams work flows:

  1. unpack S2Calo and create ntuples
    cmsDriver.py l1Ntuple -s RAW2DIGI,L1Reco --era=Run2_2016 --customise=L1Trigger/L1TNtuples/customiseL1Ntuple.L1NtupleRAW --conditions=auto:run2_data -n 10 --data --filein=/store/data/Run2015D/ZeroBias/RAW/v1/000/260/627/00000/00A76FFA-0C82-E511-B441-02163E01450F.root

  2. as 1) but include re-emulation
    cmsDriver.py l1Ntuple -s RAW2DIGI,L1Reco --era=Run2_2016 --customise=L1Trigger/Configuration/customise_Stage2Calo.Stage2CaloFromRaw --customise=L1Trigger/L1TNtuples/customiseL1Ntuple.L1NtupleRAWEMU --conditions=auto:run2_data --geometry=Extended2016,Extended2016Reco -n 10 --data --filein=/store/data/Run2015D/ZeroBias/RAW/v1/000/260/627/00000/00A76FFA-0C82-E511-B441-02163E01450F.root

  3. as 2) but add AOD info to the ntuple
    cmsDriver.py l1Ntuple -s RAW2DIGI,L1Reco --era=Run2_2016 --customise=L1Trigger/Configuration/customise_Stage2Calo.Stage2CaloFromRaw --customise=L1Trigger/L1TNtuples/customiseL1Ntuple.L1NtupleAODRAWEMU --conditions=auto:run2_data --geometry=Extended2016,Extended2016Reco -n 10 --data --filein=/store/data/Run2015D/SingleMuon/RAW-RECO/MuTau-PromptReco-v4/000/260/627/00000/00C3E929-6D84-E511-AFDF-02163E0146A5.root

Plus TSG work flows as read from:
https://twiki.cern.ch/twiki/bin/view/CMSPublic/SWGuideL1TStage2Instructions

@mulhearn mulhearn added the Todo label Feb 18, 2016
@mulhearn
Copy link
Member Author

mulhearn commented Mar 8, 2016

Quite some progress on this one, particularly as of v9.4 in integration branch. I still have some things to fix for the usability of the new integration testing tool, before I release this to developers to start trying it out.

cecilecaillol pushed a commit to cecilecaillol/cmssw that referenced this issue Jun 3, 2022
…atedDeepTauID

Remove depreciated Deep-tau-Ids
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant