As the installation of 22.2.0 to CVMFS is already underway in ATLINFR-3765.

Delete VP12DGeometrySystems and VP12DGeometryPlugin, which do not seem
to be used and are not compiled in athena currently.

Frank Berghaus authored 4 years ago and Adam Edward Barton committed 4 years ago

This has just laid dormant ever since the CMT->CMake migration. :-(

At the same time introduced some tests for the implicit copy-constructor
and copy-operator of xAOD::EventFormat.

Starting a new convention with numbering the analysis project(s) in the master branch.

Since the package was not built as part of Athena before, it is now
added to that project as well.

The test in Athena doesn't actually run anything... It sets up a job,
but doesn't run any event loop. However I didn't want to completely
re-design the test to set things up correctly for an Athena test.
(The Athena and standalone tests should just be done using separate
Python files, as they don't actually share any meaningful amount of
code with each other.)

One of the last missing packages.

The externals build caching did not work correctly when the LCG version
was being changed via a cmake command line argument. Fix this by adding
a hash of the extra cmake parameters to the stamp file.

Fixes ATLINFR-3018.

TauAnalysisAlgorithms/DiTauSmearingAlg.cxx depends
on DiTauSmearingAlg which is not migrated from R21.2 yet.
This fix removes the DiTauSmearingAlg from compilation,
which should be added back once TauAnalysisTools is
properly migrated. TauAnalysisAlgorithms added back
to package list.

This package is outdated in many ways, and mostly contains examples
for writing CP tools that we cooked up during LS1.  Besides providing
outdated examples of how to do things it also includes a conflicting
`IJetCalibrationTool` implementation (possibly others as well),
meaning it can't even be included in any release that also contains
the regular CP tool packages.

Now all of this could be fixed, but it would probably be easier to
rewrite the examples from scratch instead of trying to fix this up.
And I am not at all convinced that this is even a worthwhile
endeavour.  These examples were provided to give CP tool developer an
idea of how to develop the CP tools in the first place and that is
done now.  For the question of how to use CP tools we would probably
point users to the common CP algorithms these days.  And for either
one there is plenty of production level code available that people can
look at (though that is not a full replacement for educational
examples).

Nils Erik Krumnack authored 4 years ago and Adam Edward Barton committed 4 years ago

Just adding some more dual-use features to get AnalysisBase packages
working.

Only one package that only needed the WriteHandle added, but at least
it's something.

This is just blindly enabling packages that seem to work/compile now.

Nils Erik Krumnack authored 4 years ago and Frank Winklmeier committed 4 years ago

Just the most basic thing, so I can start the migration.