Skip to content

fix: verbosity - #4361

Merged
osbornjd merged 1 commit into
sPHENIX-Collaboration:masterfrom
osbornjd:verbosity
Jul 28, 2026
Merged

fix: verbosity#4361
osbornjd merged 1 commit into
sPHENIX-Collaboration:masterfrom
osbornjd:verbosity

Conversation

@osbornjd

@osbornjd osbornjd commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

This print statement is wrapped into a verbosity call after the surface check was fixed last week to handle approach surfaces. This should not actually print at all but some logs show that it is because there are cases where track seeds have multiple clusters on the same layer. My understanding was that the CAseeder did not allow for that but we need to double check.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work for users)
  • Requiring change in macros repository (Please provide links to the macros pull request in the last section)
  • I am a member of GitHub organization of sPHENIX Collaboration, EIC, or ECCE (contact Chris Pinkenburg to join)

What kind of change does this PR introduce? (Bug fix, feature, ...)

TODOs (if applicable)

Links to other PRs in macros and calibration repositories (if applicable)

Motivation / Context

Reduce unexpected diagnostic output observed when track seeds contain multiple clusters on the same layer, following the prior approach-surface check fix. Further verification of CAseeder behavior is still needed.

Key Changes

  • Gate the out-of-order surface diagnostic print behind Verbosity() > 0.
  • Preserve existing surface-removal and reconstruction logic.
  • Reformat a commented-out debug statement only.

Potential Risk Areas

  • No intended reconstruction, I/O, thread-safety, or performance changes.
  • Reduced diagnostics at default verbosity may make related CAseeder issues less visible.

Possible Future Improvements

  • Verify why multiple clusters can occur on the same layer.
  • Add targeted tests or structured diagnostics for this condition.

AI-generated summaries can contain mistakes; use best judgment when reviewing the implementation.

@coderabbitai

coderabbitai Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 502ef26f-16d2-4b0e-9351-88398230e8c5

📥 Commits

Reviewing files that changed from the base of the PR and between 3f9ccc3 and 157a036.

📒 Files selected for processing (1)
  • offline/packages/trackreco/PHActsTrkFitter.cc

📝 Walkthrough

Walkthrough

The change gates out-of-order surface diagnostics on Verbosity() > 0. Surface detection and removal remain unchanged, and a commented-out debug line is reformatted.

Changes

Surface diagnostic control

Layer / File(s) Summary
Verbosity-gated surface-order diagnostics
offline/packages/trackreco/PHActsTrkFitter.cc
Out-of-order surface messages are emitted only when verbosity is enabled; surface removal logic remains unchanged, and a commented debug statement’s formatting is adjusted.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sphenix-jenkins-ci

Copy link
Copy Markdown

Build & test report

Report for commit 157a036ecbe4097eb6b12d9c5855c781f32480b7:
Jenkins passed


Automatically generated by sPHENIX Jenkins continuous integration
sPHENIX             jenkins.io

@osbornjd
osbornjd merged commit adc5d62 into sPHENIX-Collaboration:master Jul 28, 2026
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant