Skip to content
Snippets Groups Projects
  1. Sep 11, 2024
  2. Aug 30, 2024
  3. Aug 26, 2024
  4. Aug 01, 2024
  5. Jul 15, 2024
  6. Jul 09, 2024
  7. Jul 03, 2024
    • Sergei Zharko's avatar
      BUGFIX: · 49233621
      Sergei Zharko authored
      1. CbmPVFinderKFGlobal: fix of track access
      2. reco_mcbm.sh: default parameter path for the online binary is ${VMCWORKDIR}/parameters/online (explicit pass is not required anymore)
      3. mcbm_event_reco_L1.C optional PV-finder routine
      4. CbmGlobalTrack.h: TODO is added
      49233621
  8. Jun 19, 2024
  9. Jun 12, 2024
    • Sergei Zharko's avatar
      Offline QA: · c4af5376
      Sergei Zharko authored and Sergei Zharko's avatar Sergei Zharko committed
      1) possibility for giving a supporting message to the checked criteria, if they are not passed
      2) cleaning-up of the CA input QA
      c4af5376
    • Sergei Zharko's avatar
      Offline-QA clean-up: · 3dbbdd76
      Sergei Zharko authored and Sergei Zharko's avatar Sergei Zharko committed
      The functions InitDataBranches and InitHistograms are merged into the InitQa function,
      the functions FillHistograms and InitTimeslice are merged into the ExecQa function.
      3dbbdd76
    • 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
  10. May 29, 2024
  11. May 22, 2024
  12. May 11, 2024
  13. May 08, 2024
  14. May 07, 2024
  15. May 03, 2024
  16. Apr 26, 2024
  17. Apr 25, 2024
  18. Apr 24, 2024
  19. Apr 22, 2024
    • Dominik Smith's avatar
      - Added online capable TRD hitfinders (1D and 2D) in cbm::algo. · 56819b96
      Dominik Smith authored and Felix Weiglhofer's avatar Felix Weiglhofer committed
      - Added ROOT-free implementations of CbmTrdCluster and CbmTrdHit.
      - Added class CbmTaskTrdHitFinder as wrapper for new hitfinders.
      - Added class CbmTaskTrdHitFinderParWrite to produce YAML input files.
      - Added example macro trd_hitfinder_run.C in beamtime/mcbm2022 folder to run new hitfinder.
      - Added a required getter function to CbmTrdParModGeo.h.
      - Updated CMakeLists and LinkDef files to enable compilation.
      56819b96
  20. Apr 18, 2024
  21. Mar 26, 2024
  22. 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
  23. Mar 21, 2024
Loading