Administrator authored 1 year ago and Sergey Gorbunov committed 1 year ago

The latency defines the time how much can happen between digi creation and
readout. Only after this time the daq buffer can be written to the output
timeslice without timly disordered digis.
Increase the default time and allow to set the time from the macro.
Add info output to the CbmDaq when the latency is changed.

Administrator authored 1 year ago and Sergey Gorbunov committed 1 year ago

This latency is used by the CbmDaq to decide when the data can be moved from
the daq buffer to the final timeslice. If the latency is currently less than
110 microseconds some of the MVD digis are not properly time sorted. The
latency needs to be adjusted after the digitization parameters are finally
fixed.

Administrator authored 1 year ago and Sergey Gorbunov committed 1 year ago

Receice at the end of the run all data which is still in the buffers of the
mvd sensors, create digis and send them to the DAQ.

Administrator authored 1 year ago and Sergey Gorbunov committed 1 year ago

Fix the digi time. There were two problems pilled up. The first problem was to
get the event time to late during execution. By accident the event time was
then also used twice, once when creating the temporary CbmPixelCharge buffer
and a second time when creating the final digi.

Flush all data which is still stored in the temporary buffer at the end of
the run.

Administrator authored 1 year ago and Sergey Gorbunov committed 1 year ago

Flush the internal buffer after each event when running in event based mode.
This creates digis for all channels even if the dead time of the channel is
not yet reached. All digis are written into the current timeslice.
Flushing the internal buffer after the last event when running in time based
mode to avoid losing data.
Create and send digi matches only if required. Should fix a memory leak.
Add LOG information in the init about run mode.
Remove obsolete code.

Administrator authored 1 year ago and Volker Friese committed 1 year ago

The latency value is used to decide when data can be moved from the daq buffer
to the timeslice. It is a value for the time disordering between digis in the
data send to the daq buffer during digitization. In case of the MVD detector
this delay can be tens of microseconds such that in case the MVD is in the
setup the used latency must be increased from the default value.

This commit implements the possibility that each detector system can define
its own latency. The latency used in CbmDaq is then the maximum of all defined
detector latencies. Currently only the MVD detector defines a non standard
latency.

Eoin Clerkin authored 1 year ago and Pierre-Alain Loizeau committed 1 year ago

Updates T0 digi classes with Bmon exquivalents. Standardises
the use of Bmon across code base and, in-use and legacy macros.

Eoin Clerkin authored 1 year ago and Pierre-Alain Loizeau committed 1 year ago

Incorporates the BMON into CBMROOT, allowing simulations with T0 and
Halo detectors.

Michael Deveaux authored 1 year ago and Florian Uhlig committed 1 year ago

data reorganization

Administrator authored 2 years ago and Florian Uhlig committed 1 year ago

Remove path from include statements
Add missing include statements and remove unneeded ones.
Use forward declaration whenever possible.

Administrator authored 2 years ago and Florian Uhlig committed 1 year ago

After many dependencies in the mvd code could be remove it becomes possible to
separate the mvd code in the same as it was done for all other detector systems
some time ago.
This commits separate the code for the CbmMvdSim library.
Also the pileup manager was moved from the sim to the base library.
This commit will not compile.

Martin Beyer authored 1 year ago and Volker Friese committed 1 year ago

Rich: Major digitizer rework using signal buffers, also implementing crosstalk and charged particle clusters

Eoin Clerkin authored 1 year ago and Pierre-Alain Loizeau committed 1 year ago

Strange zero size volume were found to cause segfault for MacOS systems. Documented in https://redmine.cbm.gsi.de/issues/2759
and MR !1126. Updates hash with geometry binary.

The mvd digitizer distributes the MC points into several new arrays which are
used for the different sensors. This distribution does not allow to use any
longer the index in the array to link the proper MC information.
To vercome the problem the index in the original array is added as a data
member to the MC point.

Correctly store information about contributing MC points in MvdPixelCharge.

Lena Rossel authored 1 year ago and Florian Uhlig committed 1 year ago

Add missing break statements (Dennis Spicker)

Without these break statements,
the resulting gamma would always be
the one for the highest Bethe-Bloch value.

Fix calculation of gamma (Lena Rossel)

Change speed of light to 1.
Momentum and mass are given in GeV, therefore speed of light does not need to be c=3e8.

Eoin Clerkin authored 1 year ago and Florian Uhlig committed 1 year ago

As reported in #2913, G4 Commands for Cerenkov photons were defunct
with current FS G4 version.

(CbmTrdParModAsic) and the proper set related. Add also CROB id to the
param file