acts: Failures during propagation
I’ve observed two more cases of propagation failures when running over Pythia8 HardQCD + SoftQCD events at mu200.
- FATRAS:
16:54:01 FatrasSimula ERROR event 571 particle id=(82|134|591|0|0)|pdg=0|q=-1|m=0|p=11.5181 failed to simulate with error PropagatorError:3: Propagation reached the configured maximum number of steps. This could be a navigation problem where the particle leaves the detector, or potentially a looper that isn’t cought by the looper protection. - Track finding
16:51:54 TrackFinding ERROR Propapation failed: EigenStepperError:3 Step size adjustment exceeds maximum trials with the initial parameters 33554 : 1.37607 2.05756 0.0118902 0.912868 2.01847 70.6078
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 25 (24 by maintainers)
Commits related to this issue
- fix: navigator priority with negative boundary distance (#1433) trying to fix a bug discovered with fatras here https://github.com/acts-project/acts/issues/1385 in some special cases the propagati... — committed to acts-project/acts by andiwand 2 years ago
- fix: navigator priority with negative boundary distance (#1433) trying to fix a bug discovered with fatras here https://github.com/acts-project/acts/issues/1385 in some special cases the propagation... — committed to acts-project/acts by andiwand 2 years ago
- refactor: debug print particle id value (#1435) while working on https://github.com/acts-project/acts/issues/1385 these changes were quite helpful for finding the "broken" particles in the CSV — committed to acts-project/acts by andiwand 2 years ago
- refactor: debug print particle id value (#1435) while working on https://github.com/acts-project/acts/issues/1385 these changes were quite helpful for finding the "broken" particles in the CSV (cher... — committed to acts-project/acts by andiwand 2 years ago
- fix: navigator priority with negative boundary distance [backport #1433 to develop/v19.x] (#1441) Backport 7ca1bb859256a2610ea52eebaac2ce99c4611506 from #1433. --- trying to fix a bug discovered with... — committed to acts-project/acts by acts-project-service 2 years ago
- fix: navigator priority with negative boundary distance (#1433) trying to fix a bug discovered with fatras here https://github.com/acts-project/acts/issues/1385 in some special cases the propagati... — committed to asalzburger/acts by andiwand 2 years ago
- refactor: debug print particle id value (#1435) while working on https://github.com/acts-project/acts/issues/1385 these changes were quite helpful for finding the "broken" particles in the CSV — committed to asalzburger/acts by andiwand 2 years ago
- refactor: debug print particle id value [backport #1435 to develop/v19.x] (#1442) Backport 5dccd51e3f07dcfb08cc5b25f05bb47fe40e9650 from #1435. --- while working on https://github.com/acts-project/ac... — committed to acts-project/acts by acts-project-service 2 years ago
- fix: stop CKF branch if particle is stopped (#1454) in some special cases particles will be stopped while propagation in the CKF due to high energy losses. in this PR this is caught and the CKF branc... — committed to acts-project/acts by andiwand 2 years ago
- fix: stop CKF branch if particle is stopped (#1454) in some special cases particles will be stopped while propagation in the CKF due to high energy losses. in this PR this is caught and the CKF branc... — committed to acts-project/acts by andiwand 2 years ago
- fix: stop CKF branch if particle is stopped [backport #1454 to develop/v19.x] (#1590) in some special cases particles will be stopped while propagation in the CKF due to high energy losses. in thi... — committed to acts-project/acts by acts-project-service 2 years ago
Yes, I implemented the ordering to cover an edge case when there was just a single boundary surface stored that was unreachable due to the particles curvature. I also utilised the boundary surface of volumes within a volume and treated them the same way. Though, I think that I observed that it could be possible to run in some strange scenarios if such a subvolume is not entirely within the other. After having a brief look at the numbers (sorry, I’m not that familiar with the output anymore), it looks to me as if the cylinder is way longer in z-direction than the position of the disc surface. Is the disc the boundary surface of the cylinder volume?