fix issue for path length in FD tracking#312
Closed
tongtongcao wants to merge 3 commits intodevelopmentfrom
Closed
fix issue for path length in FD tracking#312tongtongcao wants to merge 3 commits intodevelopmentfrom
tongtongcao wants to merge 3 commits intodevelopmentfrom
Conversation
zieglerv
previously approved these changes
Aug 20, 2024
Collaborator
Author
|
Path length, as a conventional parameter for state vector in tracking, should be kept. Since no vertex information directly from tracking, starting point for path length in tracking is the final point at the last measurement DC layer. After vertex is obtained later, transition for the starting point from the final point to vertex is taken, so that time of flight can be calculated by path length from vertex to each DC hit. Comments for the above explanation are added into codes. |
Collaborator
|
can someone find which merged PR included this? |
Collaborator
Author
|
This PR has been merged into PR #494 |
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
3 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.
The original point is not starting from vertex when set path length for hits on DCs. It causes that time of flight is wrong, and further causes that hit time is wrong, and finally causes that doca is wrong.
After the issue is fixed, relative parameters in CCDB need to be re-calibrated.