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

Phase2 tracker DQM package #28432

Merged
merged 9 commits into from Nov 25, 2019
Merged

Conversation

gsaha009
Copy link
Contributor

@gsaha009 gsaha009 commented Nov 20, 2019

PR description:

In this PR, two sub packages are created for Phase2 tracker DQM and Validation.

  1. Creating DQM/SiTrackerPhase2 and Validation/SiTrackerPhase2V packages.
  2. The main source code already existed in SimTracker/SiPhase2Digitizer package and was used in a standalone mode.
  3. Changes in DQM step: moved Phase2TrackerMonitorDigi module from SimTracker/SiPhase2Digitizer/test to DQM/SiTrackerPhase2/plugins. Updated DQM offline configs and autoDQM config to include this module in standard phase2 workflow.
  4. Changes in Validation step: moved Phase2TrackerValidateDigi module from SimTracker/SiPhase2Digitizer/test to Validation/SiTrackerPhase2V/plugins. Updated Validation configs and autoValidation config to include this module in standard phase2 workflow.
  5. Config files for 3, 4 are named following central DQM recommendations (twiki)

PR validation:

Tests done with workflows for phase2 : 20034.0, 21234.0, 22834.0, 23234.0

if this PR is a backport please specify the original PR: -NA

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28432/12831

Code check has found code style and quality issues which could be resolved by applying following patch(s)

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28432/12837

Code check has found code style and quality issues which could be resolved by applying following patch(s)

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28432/12839

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 25, 2019

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/3610/console Started: 2019/11/25 13:29

@mmusich
Copy link
Contributor

mmusich commented Nov 25, 2019

@fabiocos

the new packages basically contain a single plugin each, do you expect a further expansion?

much. This is the first stub of the still undeveloped phase2 tracker DQM.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9db8bc/3610/summary.html

@slava77 comparisons for the following workflows were not done due to missing matrix map:

  • /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/results/JR-comparison/PR-9db8bc/22834.0_TTbar_14TeV+TTbar_14TeV_TuneCUETP8M1_2026D48_GenSimHLBeamSpotFull14+DigiFullTrigger_2026D48+RecoFullGlobal_2026D48+HARVESTFullGlobal_2026D48
  • /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/results/JR-comparison/PR-9db8bc/23234.0_TTbar_14TeV+TTbar_14TeV_TuneCUETP8M1_2026D49_GenSimHLBeamSpotFull14+DigiFullTrigger_2026D49+RecoFullGlobal_2026D49+HARVESTFullGlobal_2026D49

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 34
  • DQMHistoTests: Total histograms compared: 2787584
  • DQMHistoTests: Total failures: 1
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2787242
  • DQMHistoTests: Total skipped: 341
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 628826.268 KiB( 33 files compared)
  • DQMHistoSizes: changed ( 20034.0,... ): 151719.350 KiB TrackerPhase2ITDigi/DigiMonitor
  • DQMHistoSizes: changed ( 20034.0,... ): 5431.483 KiB TrackerPhase2OTDigi/DigiMonitor
  • DQMHistoSizes: changed ( 20034.0,... ): 27.867 KiB TrackerPhase2OTDigi/SimTrackInfo
  • DQMHistoSizes: changed ( 20034.0,... ): 27.867 KiB TrackerPhase2ITDigi/SimTrackInfo
  • Checked 147 log files, 16 edm output root files, 34 DQM output files

@fabiocos
Copy link
Contributor

@jfernan2 @civanch @kpedro88 the update is purely technical, I will consider your previous signatures as valid. Please keep in mind that this update will not be innocent in terms of performances

@jfernan2
Copy link
Contributor

+1

@kpedro88
Copy link
Contributor

+upgrade

@fabiocos
Copy link
Contributor

+1

@fabiocos
Copy link
Contributor

merge

@cmsbuild cmsbuild merged commit b297706 into cms-sw:master Nov 25, 2019
@fabiocos
Copy link
Contributor

fabiocos commented Nov 26, 2019

@gsaha009 @mmusich I see there is a problem in the IB in test wf 20634.99:

----- Begin Fatal Exception 26-Nov-2019 18:28:11 CET-----------------------
An exception of category 'ProductNotFound' occurred while
   [0] Processing  Event run: 1 lumi: 2 event: 105 stream: 3
   [1] Calling method for module Phase2TrackerMonitorDigi/'pixDigiMon'
Exception Message:
Principal::getByToken: Found zero products matching all criteria
Looking for type: edm::DetSetVector<PixelDigi>
Looking for module label: simSiPixelDigis
Looking for productInstanceName: Pixel

----- End Fatal Exception -------------------------------------------------

@mmusich
Copy link
Contributor

mmusich commented Nov 26, 2019

@fabiocos as far as I see it's the only affected wf (a bit peculiar). Is it the only premixed wf in the upgrade matrix?

),
RZPositionMapH = cms.PSet(
Nxbins = cms.int32(3000),
xmin = cms.double(-3000.),
xmax = cms.double(3000.),
Nybins = cms.int32(1250),
ymin = cms.double(0.),
ymax = cms.double(1250.)
ymax = cms.double(1250.),
switch = cms.bool(False)
)
)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gsaha009.
I think that in this file InnerPixelDigiSource should be customized in the case of premixing.
Something like:

from Configuration.ProcessModifiers.premix_stage2_cff import premix_stage2
(premix_stage2 & phase2_tracker).toModify(digiMon,
    InnerPixelDigiSource = "mixData:Pixel"
)

or something similar (see e.g. https://cmssdt.cern.ch/dxr/CMSSW/source/RecoLocalTracker/SiPixelClusterizer/python/SiPixelClusterizer_cfi.py#31)

@mmusich
Copy link
Contributor

mmusich commented Nov 27, 2019

@fabiocos issue is addressed here: https://github.com/cms-sw/cmssw/pull/28486/files

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

Successfully merging this pull request may close these issues.

None yet

8 participants