Use of material map in the track propagator - #3682
Merged
Merged
Conversation
Collaborator
|
Thanks, this looks reasonable at first glance. Will have a closer look tomorrow. Ruben is working on the material map itself. It will be optimized, then also the lookup should be faster. I think for now it is just good to have it in to test the GPUs with it. For the synchronous it will be disabled anyway.
|
Collaborator
|
Tested already, white space change that broke clang-format is fixed |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi @davidrohr
this is the material correction map in the propagator. It works now.
For the TPC fit the resolutions stays the same, the pulls look a bit different (I would say, better).