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

Eoin Clerkin authored 3 months ago and Pierre-Alain Loizeau committed 3 months ago

Allow two station MVD as requested. Update geometry hash.

- Print helper block with description of the miscoslice descriptor dump lines
- Add option to select a given system ID
- Add option to print only a given number of microslices for each component in each TS

- Fix missing own header include for CbmFormatTsPrintout in the source file
- Replace std::endl with plain newline
- Add method to print a microslice descriptor help (dump description)
- Catch more low probablility error/crash cases (TS with no comp, Comps with no MS, ...)
- Add possibility to dump the MS for only a selected System ID type (default = all as before)
- Add possibility to dump only the first M microslices in each component for each TS (default = all as before)

fix sts/#8

Update geometry hash

Eoin Clerkin authored 4 months ago and Pierre-Alain Loizeau committed 4 months ago

Introduce cfv as test

- fix deprecated Sink usage by using new Dummy Sink class
- use new mTOF 2024 calib file from Norbert
- use geometry file in macro/run/data as generated by the CI (instead of the one by the mCBM simulation)
- add missing system time offset for TRD1D and TRD2D, copied from the run_unpack_tsa.C macro