`regHandle` is being called by the algorithm base class already. Also
cleanup link dependencies.

1. Pixel and SCT algorithms turned into AthAlgorithms to address ATLASRECTS-6553

2. TRT, LAr and Calo algorithms fixed by adding event context to the constructors
of condition handles

Thomas Strebler authored 3 years ago and Frank Winklmeier committed 3 years ago

This reverts commit 29104c2b73d098c4e3f9abf563d8ecc5219084e3.

The deadmap format will be changed in rel.22.
The previous DB folder was /PIXEL/PixMapOverlay, and new folder /PIXEL/PixelModuleFeMask .
This new folder is not included in old global tag.
Thus, in the job option, the DB-tag is specified, but this should be removed when the q-test update new global tag.
Unfortunately, q221 uses old global tag, OFLCOND-MC16-SDR-25, which associates PixMapOverlay-SIM-MC16-000-02.
But the RUN-2 best-knowledge tag is based on PixMapOverlay-SIM-MC16-000-03, and new deadmap conditions also based on this tag (-03).
Therefore, the q221 test will not pass T0 policy. The reference file is updated.
On the other hand, the data q431 is no problem.

Soshi Tsuno authored 4 years ago and Adam Edward Barton committed 4 years ago

revert removal of some condalgs which are needed in the legacy trigger (prevents problems with ordering of the condSeq)

These changes (hopefully) finish the change needed to remove the use of the RegSelSvc
for the ID sub-systems.

In addition, there are changes to the RegSelSvc code and the IDRegionSelector
code to remove the generation of the lookup tables using the old code, and remove
the RS functionality for the Pixel, SCT and TRT from the old RegSe;Svc.

In addition, to get round an issue with the PixelCablingCondAlg which seems to
report an unusable EventIDRange, there is a hack to get it to return a range
which should (mostly) work.

This hack should be replaced by a proper impementation of the PixelCablingCondAlg
which no longer needs to set up during the initialise (at least for the RegionSelector)

If the pixel cabling still needs to be configured during initialize() for some
other reason, then this range should be fixed such that it provides a valid range
for the subseuqnet use, or overwridden properly in the execute method.