Skip to content
Snippets Groups Projects
  1. Jun 12, 2024
    • Sergei Zharko's avatar
      Offline QA: specific configuration of the QA task · 024a19d9
      Sergei Zharko authored and Sergei Zharko's avatar Sergei Zharko committed
      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.
      024a19d9
  2. Mar 25, 2024
    • Sergei Zharko's avatar
      cbm::qa::report framework · fb4f5c45
      Sergei Zharko authored and Sergei Zharko's avatar Sergei Zharko committed
      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.
      fb4f5c45
  3. Jan 03, 2024
  4. Dec 14, 2023
  5. Nov 24, 2023
  6. Nov 09, 2023
  7. Sep 11, 2023
  8. Aug 14, 2023
  9. Aug 01, 2023
  10. Jul 31, 2023
  11. Jul 26, 2023
  12. May 02, 2023
  13. Apr 12, 2023
Loading