Make "process" a required input and configure pyconf functions globally once with user input

Closes #59 (closed) and closes #74 (closed).

• Make process a required input.
• Make "options.process" as the default input to algorithms (e.g. truth matching).
• Make process a required input to truth-matching algorithm (related to issue: #62 (closed)) and also set correct root-in-tes for Turbo process.

To be tested with: LHCb!3806 (merged), Moore!1812 (merged) and Analysis!914 (merged)

added Configuration DPA-WP3 labels

requested review from @dfazzini, @erodrigu, and @pkoppenb

assigned to @amathad and @dfazzini

marked the checklist item Make "options.process" as the default input to algorithms (e.g. truth matching). as completed

changed the description

mentioned in merge request !716 (merged)

changed the description

added 1 commit

• cb0d0a44 - revert change

Compare with previous version

Regarding the first point, I think we can implement in DV a function similar to validate_input, for checking the DV-specific properties (since process could not be shared in other application as Gauss). So I am thinking to something like:

def validate_input(values):
   if not values.get("process"):
     raise ValueError(f"'process' is a required property for running DaVinci. Available values: 'Spruce', 'Turbo', 'Hlt2'.")
   return values

This function could be call inside make_config before invoking the DV master function.

marked the checklist item Make process a required input. (Could you help me with this @dfazzini ?) as completed

changed the description

added 12 commits

• cb0d0a44...1e709d7a - 10 commits from branch master
• a7ca5dbc - Merge branch 'master' of ssh://gitlab.cern.ch:7999/lhcb/DaVinci into AM_process
• 7ae71994 - make process required

Compare with previous version

resolved all threads

marked this merge request as ready

@pkoppenb : This is ready to be tested.

/ci-test

I like it when hard-coded strings go away.

approved this merge request