Allow usage of additional track information for TPC SCD map creation #10537
Conversation
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
martenole
requested review from
davidrohr,
wiechula and
shahor02
as code owners
wiechula
approved these changes
Jan 11, 2023
|
The errors seem unrelated, can this be merged? |
|
Yes, they were unrelated, so I merged now |
mwinn2
pushed a commit
to mwinn2/AliceO2
that referenced
this pull request
Jan 17, 2023
This was referenced Feb 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Since we have stored also additional track data with the residuals during the YETS production we can use that to tighten some cuts for the map creation. E.g. in order to use only the residuals which belong to tracks that have 7 ITS clusters one can do
Pinging @aschmah