Eoin Clerkin authored 3 years ago and Florian Uhlig committed 3 years ago

Ensures that modified .cpp, .C and .h files follow basic licence header guidelines.

Check line 1 for a copyright declaration with correct numerial and character placements for a date followed by institute and city.
Check line 2 for SPDX licence identifier.
Check line 3 for author and committer information.

Jan de Cuveland authored 3 years ago and Florian Uhlig committed 3 years ago

This change corresponds to Pascal's request at
!455 (comment 13399)

Jan de Cuveland authored 3 years ago and Florian Uhlig committed 3 years ago

Flesnet generally uses C++17, but the fles_ipc classes can currently still be compiled as C++14.
This is an attempt to keep the cbmroot CI working with GCC 4.9.2.

Florian Uhlig authored 3 years ago and Pierre-Alain Loizeau committed 3 years ago

Somehow (at least on some systems) the link order was such that the
first directory was $SIMPATH/lib. This was even the case when the order was
defined differently in the CMakeLists.txt. The problem isn't yet understood
completely.

This results in the problem that libVc.a was taken from $SIMPATH/lib
were it is installed by ROOT/FairSoft. As long as the version provided with
CbmRoot and the version provided by ROOT were the same the problem wasn't
seen. When updating our internal Vc version this results in a creash when
loading libryries due to a version mismatch between the library version and
the header file version.

Add tof digitization parameters for the mcbm 2021 beamtime.
CbmSoft/cbmroot_parameter!45

Administrator authored 3 years ago and Sergey Gorbunov committed 3 years ago

It was found that switching form FairSoft jun19p2 to nov20 or apr21 has a
dramatic influence on the performance of the KFParticleFinder. The runtime
for on of the tests increased by roughly a factor 16.
https://redmine.cbm.gsi.de/issues/2220
After long investigations it turned out that the compilation flags for the
package were inherited from the ROOT and the CbmRoot project which switched
of the performance flag "-O" when using FairSoft nov20 or apr21.
The merge request fixes the issue by defining the CMAKE_BUILD_TYPE explicitely
to be RelWithDebugInfo.
The merge request also updates the VC version from 1.4.1 to 1.4.2. refs #2220

Dominik Smith authored 3 years ago and Dominik Smith committed 3 years ago

Implemented monitoring for CbmStsUnpackAlgoLegacy. Minor fix to CbmStsUnpackConfig and some cleanup of CbmStsUnpackAlgo and CbmStsUnpackAlgoBase.

Dominik Smith authored 3 years ago and Dominik Smith committed 3 years ago

Bugfix: Replaced ECbmModuleId::kHodo by ECbmModuleId::kT0 in CbmTaskBuildRawEvents and CbmEvbuildRawTask.

This update adds parameter files corresponding to the trd_v21a geometry
for the mCBM beamtine in June 2021.

Adrian A. Weber authored 3 years ago and Volker Friese committed 3 years ago

remove sorting from Algo and add check if time is greater 0. Mkissing backplanes in data could produce negative values and bee an issue. These digis are not stored

Administrator authored 3 years ago and Florian Uhlig committed 3 years ago

With macosx 10.13 (Apple clang 10.0) there is a runtime problem when
loading libL1. The problem is due to the usage of a static constexpr
in the source file which can be overcome when doing a static cast
of the variable.

Update TRD v21a by Alexandru and complete mCBM 2021_07 setup, update external/geometry tag, refs #2215

Before this fix only the number of digis of the last component of a subsystem endet up in the counter of the event header. Now an Add function is used and the counters a resetted at the beginning of each timeslice.

This adds a safeties that protect from unwanted behavior, in case of corrupted EOM messages.

The new version implements a workaround for CbmRoot. With the latest FairSoft
versions on macosx it comes otherwise to runtime errors when JIT compiling a
macro. The problem is a define statement in termios.h which defines B0 to be 0.
This coonflicts with the parameter B0 used in the header file.

Administrator authored 3 years ago and Florian Uhlig committed 3 years ago

There are some warnings which only show up on some systems and can't be
avoided. Filter them such that they don't show up on CDash.