If the flag is set the TRT error scaling will use mu from either
the offline or online luminosity conditions data.

Further fixes for python 3.

Edson Carquin Lopez authored 5 years ago and Adam Edward Barton committed 5 years ago

TRT alignment code: move to conditions handle, migrate client TRT_DetElementsRoadMaker, remove callback and create new conditions alg.

Removing Cache

Adding TRT_DetElementsRoadCondAlg_xk to the sequence within the new tracking configuration

Remove alignment callback from TRT_DetElementsRoadMaker_xk

Including TRT_DetElementsRoadCondAlg into InDetTrigConfigRecNewTracking.py and cleaning unused variables, commented out lines and lines included for debugging

Updating/adding copyright statements.

Use the average interactions per crossing from the luminosity conditions
data for the TRT drift circle mu corrections. This works around the problem
that the average interactions per crossing is currently not set in the xAOD
event info.

The mu correction is current disabled in the configuration to avoid output
changes.

Anthony Morley authored 5 years ago and Walter Lampl committed 5 years ago

Clean up logic in GSF extrapolator  --  still needs some work but this is a little less verbose and confusing

Goetz Gaycken authored 5 years ago and Walter Lampl committed 5 years ago

- Use a PRD-to-track map rather than the PRD_AssociationTool which conains a PRD-to-track map
  internally. This is needed to resolve ATLASRECTS-5005.
- Made all methods const.
- The score processor does not create track copies anymore, thus PRD-to-track maps stay valid for
  scored tracks.
- The ambiguity processors now use a helper class which manages the new and original tracks i.e.
  tracks with mixed ownership, and creates track copies only for the final track collection if
  necessary.
- Moved debug ntuple code of simple ambiguity processor to a new derived class, to improve the
  readability.

This fixes the configuration when running InDetPhysValMonitoring.

The association map is stored in storegate for cases in which the PRD association
is shared across multiple algorithms. The PRD_AssociationTool is still used for the
cases in which the PRD association is shared between multiple tools but which are
all related to a single algorithm instance. Thus, the PRD_AssociationTool still has
to be public for tha latter cases. The current configuration does not ensure
that tool instances are confined to single algorithms. Thus, in case of more than
one thread, different algorithms may still operate concurrently on the same internal
association map, which can be mitigated by configuration changes (to be done).

- provide methods to create fitters with all its tools which use customized pixel cluster
on track tools with configurable split cluster maps, and
- use these methods to create fitters for extended track collections, which require
different split cluster maps.

This fixes q223, which requires a special split cluster map for pixel tracks.

Use the logging infrastructure to print DEBUG messages.

- Added conditions algorithm to created TTrainedNetworks,
- whcich are accessed by the NnClusterizationFactory via
  CondHandles (replacing the conditions callbacks).


Former-commit-id: b38a3bdc

Former-commit-id: 66cbae77

This restores the override properties of the original error scaling
tool and allows to provide custom error scalaing parameters without
a custom database.


Former-commit-id: 59055193

The Pixel, SCT and TRT RIO on track error scaling is now handled by
specialised conditions data rather than a tool where the conditions data
is created by conditions algorithm.


Former-commit-id: 54495adb