-
Notifications
You must be signed in to change notification settings - Fork 34
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Surface navigation now split in finding the frame and relocation (#308)
The AdePT interfaces for navigation normally compute first the distance to the next hit volume, then relocates to find out the next path. The first interface for surface navigation did systematically step+relocation in one go, which is very inefficient in case of non-zero magnetic field, where the field propagator has to call the distance computation in several points along the trajectory. The PR introduces the split: distance computation does not change the output state, but sets its boundary flag according to a surface being hit within the physics step, returning also the index of this surface. The relocation method used this index as input. Due to the addition of this index in the interfaces, currently, the calling interface of the surface navigator is for the moment different than the solid navigators. --------- Co-authored-by: Severin Diederichs <65728274+SeverinDiederichs@users.noreply.github.com> Co-authored-by: Severin Diederichs <severin.diederichs@cern.ch> Co-authored-by: Juan González <juangonzalezcaminero@protonmail.com>
- Loading branch information
1 parent
4a017f5
commit 70e47b4
Showing
14 changed files
with
248 additions
and
194 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.