Skip to content

Please consider the following formatting changes to #15887 - #70

Closed
alibuild wants to merge 3 commits into
sawenzel:swenzel/o2sim-vecgeom-safety-booleanfrom
alibuild:alibot-cleanup-15887
Closed

alibuild wants to merge 3 commits into
sawenzel:swenzel/o2sim-vecgeom-safety-booleanfrom
alibuild:alibot-cleanup-15887

Conversation

@alibuild

@alibuild alibuild commented Oct 2, 2026

Copy link
Copy Markdown

Your PR AliceO2Group#15887 cannot be merged as is. You should either run clang-format yourself and update the pull request, or merge this PR in yours.
You can find the AliceO2 coding conventions at https://github.com/AliceO2Group/CodingGuidelines.

sawenzel and others added 3 commits October 2, 2026 11:24
This makes the stand-alone ComputeSafety of both VecGeom navigators cheaper, as Geant4's own navigator does.

- The caller's proposedMaxLength now limits the BVH search: the value is exact below it and a valid lower bound above it, as in G4VoxelSafety.
- A query at distance d from the last safety origin returns s0 - d when that covers the bound, without a computation. Every locate drops this cache.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This fixes a stale exit block in the relocating VecGeom navigator.

- Entering a daughter adopted the state of the step, which could still carry the block of the volume the previous crossing left, so that volume stayed blocked one step longer than Geant4's rule allows.
- Seven of 50000 geantino rays through the ITS outer-barrel services saw up to 9 X0 too much copper because of it; they now agree with TGeo.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sawenzel
sawenzel force-pushed the swenzel/o2sim-vecgeom-safety-boolean branch from 6dc8313 to 2beea34 Compare October 2, 2026 10:21
@alibuild alibuild closed this Oct 2, 2026
@alibuild
alibuild deleted the alibot-cleanup-15887 branch October 2, 2026 10:22
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.

2 participants