Conversation
…ign params to tuple indices
…accelerator names
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.
BEGINRELEASENOTES
exactly as it appears between the two bold lines
ENDRELEASENOTES
Lifted from @Victor-Schwan work in another repository.
The goal in the end is to have a simple algorithm that merges tracks based on track parameters at the IP such that they can then be passed to an algorithm or processor that does a fit of the combined track. The context is tracking in ILD @ FCCee, where we use Clupatra for the TPC and ConformalTracking for the inner tracker. (The standard ILD tracking sequence is too specific and geared towards the standard ILD geometry to make it usable in this context).