Skip to content

add separate nHits requirements for top & bottom and for each track finding iteration in KF #1149

@bloodyyugo

Description

@bloodyyugo

We currently perform track finding separately for top and bottom SVT halves and do two iterations of track finding, the second with looser requirements than the first. However, there is only a single "minHits" setter in KalmanPatRecDriver...it uses the minHits to set the first iteration to minHits+1 and second to minhits and the top and bottom has same requirement.

We'd like to be able to set the minHits separately for each iteration and also for top & bottom (particularly since 2021 is missing a bottom module-5 sensor).

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions