Template implementation

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

- CbmEventTrigger class to store different trigger flags for the event selection (Lambda, Ks, ....)

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

- a new service "run_info": prints different run properties to stdout (at the moment only the geometry setup tag)
- fixes in reco_mcbm.sh

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

1. reco_mcbm.sh:  New options (separate directory for different steps, lambda in mCBM, retrieving a tsa file name from and index list)
2. reco_mcbm_job.sh:  Settings to run reco_mcbm.sh from the box on virgo (vs. runID and jobID)
3. cbm::kfp::V0FinderTask: minor bug fixes

The experimental build mode should not remove the build directory neither
update the local working copy. Unfortunately this features were brocken because
of typos in a comparisson where lower case and upper case modes were mixed.

- Counts per given bin size and gap size depending on bin size
- Calculation abd plotting of Q-Factors, HADES style + finer steps
- Calculation and plotting of Q-Factors variations depending on bin size (timescale)
- Add TRD and RICH to bunch check macro
- Calculation of pseudo Q-factors with STS and TOF digis (counting products and not beam particles)

Pierre-Alain Loizeau authored 10 months ago and Pierre-Alain Loizeau committed 2 months ago

- tool to check data from TSA w/ legacy unp
- tool to compare digis found in the old BMon VS those found in the new BMon
  (from TSA with either legacy or online unpacker)
- tool to study BMon bunches size, extension and counts

Add more tests which were missing before. Cleanup the test cases and reduce
complexity of some tests.

Sergei Zharko authored 2 months ago and Sergei Zharko committed 2 months ago

 - setting const qualifier to the GetIndex and the GetStsTrackIndex functions
 - re-implimenting the GetIndex function to make it const qualified and reduce the number of access calls

Define the much parameter file name properly in case of mcbm geometry.

Correct file names in kfparticle test.
Add correct much initilization in kfparticle and mcbm hadron analysis
tests.

In the macro GENERATE_CBM_TEST_SCRIPT the Geant4 data variables were not
properly added to the generated shell script. This was not yet seen since all
tests were done with the Geant3 simulation engine. The problem was found after
the KF related tests were moved to  Geant4.

The transport stage still placed the target at 0. cm. The global coordinate
system was changed long time ago to have the origin in the middle of the
magnet. Change the target as well as well as the origin of the reactions to
z=-44. cm.

The current test time was slightly on the low side for run4. When running the
test locally on an empty node the execution time was below the maximum test
time. When running the test in parallel with other tests the test hits the
time limit. Fixing this by increasing the test time.

When running the Dart.sh script normally all available cores are used which
works well in most cases. Up to now it was possible to limit the number of
used cores by defining the environment variable NCPU which was used for the
build as well as the test stage. Depending on the system this resulted in a
large number of tests which ran into timeouts which were not seen when running
the tests sequentially. With this commit it becomes possible to limit the used
cores during the test stage independently. This is done by defining the
environent variable NCPU4TEST.

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

CA: migration from ca:: to kf::MaterialMap: removing ca::MaterialMap from CbmL1 and CbmGenerateMaterialMaps classes