Skip to content

Add possibility to use tracking geometry conditions data in the Navigator.

Goetz Gaycken requested to merge goetz/athena:TrkGeomNavigator_master_optionally_use_tracking_geom_cond_data into master

The configuration is prepared to use the TrackingGeometry conditions data instead of the TrackingGeometrySvc in the Navigator. The TrackingGeometrySvc does not support concurrent events with different alignments. Thus, migration to the conditions data is mandatory for atheneMT. Since parallel usage of the TrackingGeometrySvc and the TrackingGeometry conditions data introduces differences it is not used by default. Support for the conditions data will be added in all clients package by package and once support is available in all clients, all clients will be switched to the TrackingGeometry conditions data and the service will be retired.

The observed differences when using the TrackingGeometry conditions data instead of the service are most likely only caused by failing pointer comparisons between TrackingGeometry objects: surfaces, layers and volumes. The comparisons are used to identify whether e.g. destination surfaces etc. are reached and such comparisons will fail if the objects originate from different providers e.g. the conditions data and the service.

The migration to the conditions data is documented in ATLASRECTS-5600.

Edited by Goetz Gaycken

Merge request reports