Skip to content

[17.0.X] improve SiStripHitEffFromCalibTree and SiStripHitResolFromCalibTree - #45083

Draft
mmusich wants to merge 2 commits into
cms-sw:CMSSW_17_0_Xfrom
mmusich:mm_dev_improveCalibraTrackerSiStrip
Draft

[17.0.X] improve SiStripHitEffFromCalibTree and SiStripHitResolFromCalibTree#45083
mmusich wants to merge 2 commits into
cms-sw:CMSSW_17_0_Xfrom
mmusich:mm_dev_improveCalibraTrackerSiStrip

Conversation

@mmusich

@mmusich mmusich commented May 28, 2024

Copy link
Copy Markdown
Contributor

PR description:

Somewhat inspired by cms-sw/cms-bot#2228, trying to debug crashes reported at cms-sw/cms-bot#2228 (comment), improve the modules SiStripHitEffFromCalibTree and SiStripHitResolFromCalibTree:

  • close input calibTree files after reading them;
  • delete all new-ly allocated memory;
  • use named constants for k_END_OF_LAYERS and k_END_OF_LAYS_AND_RINGS in lieu of magic numbers

PR validation:

scram b runtests_testSiStripHitEfficiency and scram b runtests_testSiStripHitResolution run fine after the update.

If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:

Not a backport, might be backported to 14.0.X

@cmsbuild

cmsbuild commented May 28, 2024

Copy link
Copy Markdown
Contributor

cms-bot internal usage

@cmsbuild

Copy link
Copy Markdown
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45083/40403

@cmsbuild

Copy link
Copy Markdown
Contributor

A new Pull Request was created by @mmusich for master.

It involves the following packages:

  • CalibTracker/SiStripHitEfficiency (alca)
  • CalibTracker/SiStripHitResolution (alca)

@cmsbuild, @saumyaphor4252, @perrotta, @consuegs can you please review it and eventually sign? Thanks.
@rsreds, @echabert, @gbenelli, @tocheng, @yuanchao, @mmusich, @robervalwalsh this is something you requested to watch as well.
@antoniovilela, @sextonkennedy, @rappoccio you are the release manager for this.

cms-bot commands are listed here

@mmusich

mmusich commented May 28, 2024

Copy link
Copy Markdown
Contributor Author

@cmsbuild, please test

@cmsbuild

Copy link
Copy Markdown
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-8e7715/39593/summary.html
COMMIT: 75a6c3d
CMSSW: CMSSW_14_1_X_2024-05-28-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/45083/39593/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • You potentially added 1 lines to the logs
  • Reco comparison results: 4 differences found in the comparisons
  • DQMHistoTests: Total files compared: 48
  • DQMHistoTests: Total histograms compared: 3338862
  • DQMHistoTests: Total failures: 9
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3338833
  • DQMHistoTests: Total skipped: 20
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 47 files compared)
  • Checked 202 log files, 165 edm output root files, 48 DQM output files
  • TriggerResults: no differences found

bool debug{false};

if (!tFile.IsZombie() && tFile.IsWritable() && debug) {
// Delete all objects in the file recursively

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Why the objects in file are deleted and the files are written and closed only when the debug option is true?

@mmusich mmusich May 29, 2024

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

it was an (unsuccessful) attempt to debug #45084. AFAIU normally the destructor of TFileService should do that automatically, but somewhere there is a double deletion.
This piece could be removed.

@cmsbuild

Copy link
Copy Markdown
Contributor

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45083/40419

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

@cmsbuild cmsbuild added this to the CMSSW_14_2_X milestone Sep 3, 2024
@cmsbuild

Copy link
Copy Markdown
Contributor

Milestone for this pull request has been moved to CMSSW_15_0_X. Please open a backport if it should also go in to CMSSW_14_2_X.

@cmsbuild cmsbuild modified the milestones: CMSSW_14_2_X, CMSSW_15_0_X Nov 22, 2024
@cmsbuild

cmsbuild commented Feb 7, 2025

Copy link
Copy Markdown
Contributor

Milestone for this pull request has been moved to CMSSW_15_1_X. Please open a backport if it should also go in to CMSSW_15_0_X.

@cmsbuild cmsbuild modified the milestones: CMSSW_15_0_X, CMSSW_15_1_X Feb 7, 2025
@mmusich
mmusich marked this pull request as draft August 1, 2025 08:24
@cmsbuild

Copy link
Copy Markdown
Contributor

Milestone for this pull request has been moved to CMSSW_16_0_X. Please open a backport if it should also go in to CMSSW_15_1_X.

@cmsbuild cmsbuild modified the milestones: CMSSW_15_1_X, CMSSW_16_0_X Sep 10, 2025
@cmsbuild

Copy link
Copy Markdown
Contributor

Milestone for this pull request has been moved to CMSSW_16_1_X. Please open a backport if it should also go in to CMSSW_16_0_X.

@perrotta

Copy link
Copy Markdown
Contributor

-1

  • This PR is stuck since quite some while: let reject it, to keep it out of our radars
  • As soon as @mmusich or anyone else will pick it up again, the alca signature will be reset, and we will get back to it

@cmsbuild

cmsbuild commented Apr 4, 2026

Copy link
Copy Markdown
Contributor

Milestone for this pull request has been moved to CMSSW_17_0_X. Please open a backport if it should also go in to CMSSW_16_1_X.

@cmsbuild

cmsbuild commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Milestone for this pull request has been moved to CMSSW_20_0_X. Please open a backport if it should also go in to CMSSW_17_0_X.

@makortel

makortel commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Just checking, is this PR intended for Phase 2 (20_1_X) or Run 3 legacy (17_0_X) or both?

@smuzaffar

Copy link
Copy Markdown
Contributor

this needs rebase/resolve merge conflicts

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.

6 participants