Patch KKLine for KinKalGeom migration#1811
Conversation
|
Hi @brownd1978,
which require these tests: build. @Mu2e/write, @Mu2e/fnalbuild-users have access to CI actions on main. ⌛ The following tests have been triggered for 300ac74: build (Build queue - API unavailable) |
|
☀️ The build tests passed at 300ac74.
N.B. These results were obtained from a build of this Pull Request at 300ac74 after being merged into the base branch at 5912724. For more information, please check the job page here. |
|
@FNALbuild run build test |
|
⌛ The following tests have been triggered for fead67b: build (Build queue - API unavailable) |
|
☀️ The build tests passed at fead67b.
N.B. These results were obtained from a build of this Pull Request at fead67b after being merged into the base branch at 5912724. For more information, please check the job page here. |
PR #1811 Review — "Patch KKLine for KinKalGeom migration"Author: @brownd1978 · Base: 1. PR SummaryFollowing the migration of
Risk: medium. The build CI passes (3070), but there are at least two substantive (non-refactor) changes hiding inside what reads as a mechanical patch — see issues #1 and #2 below. 2. Core Changes (issues found)🚨 Issue 1 —
|
| File | sample list | TCRV |
|---|---|---|
KKFit.hh |
rebuilt per call | n/a |
CentralHelixFit_module.cc |
rebuilt per call | n/a |
KinematicLineFit_module.cc |
rebuilt per call | rebuilt per call |
Worth aligning on one pattern (preferably "cache in beginRun"), even if as a follow‑up.
ℹ️ Issue 5 — New include may be unused
#include "Offline/Mu2eKinKal/inc/KKShellXing.hh"This include is added but I don’t see a new symbol from KKShellXing referenced in the diff (KKCRVXING/KKCRVXINGPTR were already in use before). Please confirm it isn’t already pulled in transitively — if so, drop it.
ℹ️ Issue 6 — Pre‑existing typo retained, plus stray blank line
KKFit.hhkeeps the typo// surfaces to sample; this interface is deprecatecd(was already there — easy to fix while editing the line).KinematicLineFit_module.ccleaves a stray double blank line where theExtrapolateTCRVblock was removed.
ℹ️ Issue 7 — clang‑tidy delta
The CI table on the latest build (fead67b) reports 4 errors / 71 warnings and TODO (19) FIXME (6) in 3 files, up from 2 errors / 20 warnings and TODO (2) FIXME (1) in 1 files on the first push. Most of this is likely because the second push touches more files, but worth a glance at the clang‑tidy log to confirm none of the new diagnostics are introduced by this PR.
3. Merge Readiness
| Item | Status |
|---|---|
| Mergeable | ✅ clean |
| Build CI | ✅ passed (job 3070) |
| Reviews | ⏳ none yet (review requested from @rlcee) |
| Validation | The PR description says it fixes an exception in extracted validation — please post the validation/extracted‑run output as evidence before merge |
| Blocking issues | None compile‑level; Issue 1 (physics constant change) and Issue 2 (typo) should be addressed first |
4. Suggested Improvements
- Update the PR description to explicitly call out the
tcrvthick_value/semantics change. - Fix
int extrapdebug_ = false;→int extrapdebug_ = 0;. - Move the
GeomHandle<KinKalGeom>lookup,sample_resolution, andExtrapolateTCRVconstruction intobeginRun()to avoid per‑track work. - Drop the (apparently) unused
KKShellXing.hhinclude. - Fix the pre‑existing
deprecatecdtypo inKKFit.hhwhile you’re there. - Align the three modules on one caching pattern in a follow‑up.
5. Want me to…
- Post these review comments inline on the PR (you’d need to confirm the file/line targets).
- Open a small follow‑up issue tracking "cache
KinKalGeom‑derived objects inbeginRun" acrossMu2eKinKal? - Pull and read the clang‑tidy log to confirm whether any new diagnostics are introduced by this PR?
- Look up the actual CRV sector thickness from
GeometryServiceto verify150.0mm is correct?
|
📝 The HEAD of |
|
Addressed AI issues: |
|
@FNALbuild run build test |
|
⌛ The following tests have been triggered for 3d9133d: build (Build queue - API unavailable) |
|
☀️ The build tests passed at 3d9133d.
N.B. These results were obtained from a build of this Pull Request at 3d9133d after being merged into the base branch at b38c2bf. For more information, please check the job page here. |
This addresses the exception in extracted validation following the migration of KinKalGeom to GeometryService.