Sergei Zharko authored 10 months ago and Sergei Zharko committed 10 months ago

The functions InitDataBranches and InitHistograms are merged into the InitQa function,
the functions FillHistograms and InitTimeslice are merged into the ExecQa function.

Sergei Zharko authored 10 months ago and Sergei Zharko committed 10 months ago

The commit introduces the possibility of the specific QA task configuration withing the QA-config yaml file.
In the yaml-file, the configuration should be defined under qa/<task name>/specific node. On the task side
the configuration is represented with a plain structure (Config), which can be defined using the function
std::optional<Config> CbmQaTask::ReadSpecificConfig<Config>() in the task initialization function (for
expample see the CbmCaInputQaBase class implementation).

The specific configuration feature is optional and can rely on the default-initialized Config structure, so the "specific" branch
of the QA-configuration file is not mandatory.

1. CbmQaTask[BUGFIX]: default run over entire time-slice, if the opposite is not required explicitly (fixes a repeated loop over hits in the CA input QA)
2. mcbm_qa.C: modifications to run on the real data
3. New histograms for the CbmCaSetupQa task
4. Installation rules are added for the create_mcbm_geo_setup.C and run_recoQa.C macros

Sergei Zharko authored 11 months ago and Sergei Zharko committed 11 months ago

The tracking parameter file extention is changed from "L1Parameters.dat" to "ca.par" in the
offline data reconstruction in order to keep a consistency with the naming rule, used
in the online tracking chain.

Sergei Zharko authored 1 year ago and Sergei Zharko committed 1 year ago

The framework encapsulates creation tools for a generic QA-report source, which can be compiled
into different sources (LaTeX, Beamer, Markdown, HTML, etc.).

A report consists from an ordered tree of elements (cbm::qa::report::Element). At the moment
three types of elements are available: cbm::qa::report::Section, cbm::qa::report:Figure and
cbm::qa::report::Table. Each element is registered in the LinkDef.h file for accessibility
from a ROOT-macro, but never the less does not rely on the ROOT libraries.

A variety of the report source formats is achieved using the Visitor desing pattern. Each set
of element compilation rules is defined in a specific implementation of the cbm::qa::report::Engine
class (the visitor), which alows the simultanious creation of report different sources. From the
box the source for LaTeX plain document (cbm::qa::report::LatexEngine) and HTML-page
(cbm::qa::report::HtmlEngine) are available.

The use-case of the framework is given in the cbmroot/macro/qa/report_example.C macro. The macro
generate CA tracking status report for a given setup and requires an output from the run_qa.C/mcbm_qa.C
macro.

- point station index definition in the performance
- rejection of hits with NaN or Inf parameters
- transport macro with box generator for mCBM

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

CA: Rebase on master; updates in QA-task framework; replacement of CbmQaEff with TProfile in CbmCaInputQaSts

- CTest for running qa_compare.C macro
- Improvements in QA-Checker