Together with it, all supporting classes from ca::tools and cbm::ca were removed as well.

Sergei Zharko authored 4 months ago and Sergey Gorbunov committed 4 months ago

1) in-geometry: if the detector subsystem exists in geometry
2) is-active: if the detector subsystem provides hits and was not disabled manually (case of MVD in tb)

CA: replacing the hard-coded disabling of detector subsystems with respect to the tracking mode (STS, mCBM, global) to the corresponding CA-configs; adding geometry layer index to ca::Station

  - improvement of kf::SetupBuilder
  - introduction of the builder intialization from existing setup;
CA: fixes of setup initialization in parameters

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