Skip to content

TrackingMultiplet changes to use it for a DUT (v2)

Annika Vauth requested to merge avauth/corryvreckan:Multiplet4DUTv2 into master

Re-implementation of !502 (closed) , to have a "clean start" after the changes in the tracking classes in the past year.

Description partially copied from there 😇

Follow-up of the discussion on mattermost: Some changes to use TrackingMultiplet with a DUT (rather than a scatterer) - e.g. for a use case with a scatterer behind the DUT, before the downstream telescope planes.

Contains the following changes: TrackingMultiplet

  • gbl refit (Thanks @lhuth !)
  • options "require_detectors" and "timestamp_from" (analogous to what exists in Tracking4D)
  • update README accordingly

Some more changes necessary to use the Multiplet Tracks for DUT analysis (before, unless the DUT was used for building the Multiplet, DUTAssociation etc would crash with

"Fatal internal error
Track Object Multiplet does not have any entry for detector <dut>
Cannot continue..."

--> force registration of the all planes to the multiplet (all upstream/downstream planes to the upstream/downstream tracklets). Not sure if this is the best way to fix this issue, but I also didn't see any obvious less-messy ways to do it differently

Few related classes:

  • added some debug-level log messages while debugging the changes above (not directly related to the new functionality, so I could remove them again, if you think there's no future use)
Edited by Annika Vauth

Merge request reports