Sergei Zharko authored 11 months ago and Pierre-Alain Loizeau committed 11 months ago

online/ca: Adding yaml-configuration for the tracking chain; setting number of threads to Opts().NumOMPThreads()

ca Bugfix: account for inactive tracking stations in material budget map calculation read from ca config

bugfix: Fixing the CA-parameters output file name in case the output directory is not provided

Grigory Kozlov authored 1 year ago and Sergey Gorbunov committed 1 year ago

- Added template-based CaParameters
- Deleted inherited classes CaStationV/F/D, CaFieldV/F/D, have to be used with <DataT> instead

A CA iteration (L1CAIteration class) represents a set of parameters, dependent from the particular track finder
running step. Previously, default iterations were initialized in the CbmL1::Init function with hard-coded values.
Now, the default iteration list is provided in the in the configuration file. At the moment there are three
main configuration files:
   ${VMCWORKDIR}/macro/L1/configs/ca_params_sts.yaml    -- L1Algo::TrackingMode::kSts
   ${VMCWORKDIR}/macro/L1/configs/ca_params_mcbm.yaml   -- L1Algo::TrackingMode::kMcbm
   ${VMCWORKDIR}/macro/L1/configs/ca_params_global.yaml -- L1Algo::TrackingMode::kGlobal

L1: explicit implementation of copy and move constructors and assignment operators were replaced with default for L1Parameters and L1CAIteration classes

L1: replaced preprocessor macros DO_NOT_SELECT_TRIPLETS, TRACKS_FROM_TRIPLETS, TRACKS_FROM_TRIPLETS_ITERATION, EXTEND_TRACKS with flags in L1CAIteration

L1: Added boost serializers for L1Parameters objects and their components; implemented an interface for parameters and input data RW