Cleanup of track container filing code in ProtoTrackCreationAndFitAlg + test improvs

This is a follow up of: !68479 (closed) While working on the issue related to the last ACTS bump I have seen opportunity to simplificationof track container use and also simplifications to the test scirpt (i.e. I need to hack it like in this changeset to enable debugger).

Basically, in the flags system was designed so that in most cases we should not need additional python parsers.

@sabidi @goblirsc

This merge request affects 2 packages:

• Tracking/Acts/ActsConfig
• Tracking/Acts/ActsTrackReconstruction

Affected files list will not be printed in this case

Adding @jojungge ,@cvarni ,@pagessin ,@tbold ,@goetz ,@toyamaza ,@adye as watchers

added ACTS Tracking main review-pending-level-1 labels

CI Result SUCCESS (hash bd5dcb9f)

	Athena
externals
cmake
make
tests

Full details available on this CI monitor view. Check the JIRA CI status board for known problems
Athena: number of compilation errors 0, warnings 0
For experts only: Jenkins output [CI-MERGE-REQUEST-EL9 3909]

The changes are straightforward and there are no issues with the CI. Approving from L1.

added review-approved label and removed review-pending-level-1 label

merged

mentioned in commit 7591ffb2

That was quick. I was hoping that @goblirsc will have a chance to comment

why's the argument parser gone?

Just to second that, we have been using this script for small tests. Argpaser has been helpful for testing different things.

This particular option should be handled already here. https://gitlab.cern.ch/atlas/athena/-/blob/main/Control/AthenaConfiguration/python/AthConfigFlags.py#L581 I.e. flags can be directly controlled from command line. Btw I hopped that you would haveea chance to comment before it was merged. But it went real fast. Send from phone, sorry for brevity.

Got to it now. This is bit philosophical ... i.e. we have flags system integrated with command line parsing already, so simple tests do not need to reimplement command line handling at all. I.e. all flags can be setup and if some property is not already a flag it can be added with one-line addFlag("", ).

This changeset contains also this file: Tracking/Acts/ActsConfig/test/ActsEFTrackFit.sh with some examples.

Is there documentation on the flags / command line interface available somewhere? This honestly sounds extremely useful also for other standalone snippets, I didn't know this exists. And are there shorthands available, since some of the syntax such as Input.Files="['location']" is far too cumbersome for command line operation and would result in another layer of wrapper scripts?

Here: https://atlassoftwaredocs.web.cern.ch/guides/ca_configuration/flags/#using-flags (a very concise) As always, the best documentation is the code: https://gitlab.cern.ch/atlas/athena/-/blob/main/Control/AthenaConfiguration/python/AthConfigFlags.py#L571

Ah, and filesInput is there fortunatelly.

Neat! Thanks so much, this looks very useful. Happy to move to this scheme - @sabidi fine for you as well?