Add a standard reco Gaudi options file

[tmadlener]

BEGINRELEASENOTES

• Add a Gaudi options file to run the standard reconstruction with some command line arguments to configure what to run
  • Created via automatic conversion of the Marlin steering file plus the necessary adaptions to make it run
  • Run from LCIO or EDM4hep inputs (mutually exlusive), use --inputFiles
  • Produce EDM4hep output only by default, but allow to add LCIO output as well or switch to that using --lcioOutput.
  • Read the README section to see all available command line arguments
• The overall reconstruction chain is modularized effectively in the same way as it was previously done for Marlin.
  • Different parts of the chain live in different files, where each file defines part of the whole chain as a sequence.
  • These sequences are dynamically loaded and configured depending on calibration constants, which depend on the CMS energy as well as the detector model.
• Calibration for the different detector models is also split into different .cfg files which essentially all just define a single dictionary with all calibration constants. The same approach is followed by the CMS energy dependent config parameters.

ENDRELEASENOTES

The EDM4hep output currently stores everything that is available in the event (more or less corresponds to the REC LCIO output).

For bkg overlay there is a slightly more involved configuration because there are no default background files in the Marlin steering file. I effectively just disable overlay for now.

I have also replaced the InitDD4hep processor with the Key4he GeoSvc to load the detector geometry.

I would postpone code cleanup and potential re-organization to a follow up PR to not complicate this one too much.

• [x] Add an option to also configure EDM4hep output.
• [x] Other energy dependent parameters -> follow-up PR
• [x] Needs https://github.com/iLCSoft/MarlinReco/pull/126 to always work
• [x] Needs https://github.com/key4hep/k4FWCore/pull/178 (backported necessary changes)
• [x] PerfectPFA option
• [x] Consistent detector model and constant file?
• [x] Check whether the full configuration makes it into the metadata of the EDM4hep output file (i.e. make sure that the fully resolved thing is stored) -> Yes, done via a Gaudi service that sees the full configuration that is run

[Zehvogel]

It might be good to have the documentation for this not only in the release notes :)

[tmadlener]

Good point. Done