Bug #18972
Track length based only on ValidPoints (i.e. !NoPoint flag), ignores flags ExcludedByFit and RejectedByFit
Occurs In:
Experiment:
-
Co-Assignees:
Description
Track length based only on ValidPoints (i.e. !NoPoint flag), ignores flags ExcludedByFit and RejectedByFit
Subtasks
History
#1 Updated by Lynn Garren almost 3 years ago
- Status changed from New to Assigned
- Assignee set to Giuseppe Cerati
Giuseppe and Gianluca will start with a design discussion.
#2 Updated by Giuseppe Cerati almost 3 years ago
Gianluca and Giuseppe discussed, here is a summary:
- need to modify the TrajReserved1 so that it mean a suggestion (from the track producer) whether the point is meant to be used for downstream analysis (a name has to be found)
- need a more generic version of the methods NextValidPoint and PreviousValidPoint, taking as an argument a list of allowed (or forbidden) flags
- need to adapt all other TrackTrajectory methods that internally call NextValidPoint and/or PreviousValidPoint to take the same list as argument and then pass though
- need to define the default behavior; Giuseppe's proposal is !NoPoint && !TrajReserved1