Skip to content

Avoid Py:conf2toConfigurable WARNING PrivateToolHandleArray DetectorTools

Christos Anastopoulos requested to merge ATLAS-EGamma/athena:Fix_std_reco_configrable_warnings into master

This my attempt to fix :

08:13:32 Py:conf2toConfigurable WARNING    PrivateToolHandleArray DetectorTools of GeoModelSvc/GeoModelSvc does not have the same named components
08:13:32 Py:conf2toConfigurable WARNING    Old (conf1) ['BeamPipeDetectorTool', 'InDetServMatTool', 'LArDetectorToolNV', 'LUCID_DetectorTool', 'MuonDetectorTool', 'PixelDetectorTool', 'SCT_DetectorTool', 'TRT_DetectorTool', 'TileDetectorTool', 'ZDC_DetTool'] for GeoModelSvc/GeoModelSvc
08:13:32 Py:conf2toConfigurable WARNING    New (conf2) ['BeamPipeDetectorTool', 'InDetServMatTool', 'LArDetectorToolNV', 'MuonDetectorTool', 'PixelDetectorTool', 'SCT_DetectorTool', 'TRT_DetectorTool', 'TileDetectorTool'] for GeoModelSvc/GeoModelSvc

This is seen in RecExCommon where we use a mixture of old/new CA config. We need a way to add "all enabled" in TrackingGeometry when we call things via the relevant CAtoGlobalWrapper wrappers. This needs to match the "all" we have done previously "old style" before in RecExCommon.

This is a combination of what I understood from discussions with @tsulaia , @jchapman and @tadej on how a minimal hack (will be a hack until we move away, to pure C.A) would look like.

  1. Take the placement ala @tsulaia ( TrackingGeometryCondAlg)
  2. Avoid using the "AltasGeometryCfg" as per @jchapman just add the Fwd part.
  3. Do it only when we are called via a "CAtoGlobalWrapper" and comment on it as per @tadej
Edited by Christos Anastopoulos

Merge request reports