Refactor Seeding to avoid repeated Finders instantiations #1690
Labels
Impact - Minor
Nuissance bug and/or affects only a single module
Improvement
Changes to an existing feature
Long Term
Tracking issues for longer-term projects and developments
Needs Decision
Needs decision or further information
Stale
Milestone
At ACTS dev. weekly 22.11.22 we discussed and agreed that SeedFinder(s) should be refactored so that clients (example algorithm in ACTS or ATLAS Athena or ... ) do not need to reinstantiate it for every event.
In practice this means that seed finding method should get part Options object that changes from event to event in the methods that process the data rather than at construction.
Suitable Option objects were introduced in PR #1630.
The changes can happen in steps, one for each specific Seeding algorithm.
FI @LuisFelipeCoelho @stephenswat
The text was updated successfully, but these errors were encountered: