Hits across sensors for 2 station MVD.

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

Addinga hash getter for a CbmSetup; storing and testing a reference hash in the KF-setup builder initialization

[BugFix] Add [KfCore/CaCore/Algo]Offline libraries to remove feed down of NO_ROOT flag to libraries in reco folder

- Build AlgoOffline library only if not in CBM_ONLINE_STANDALONE (aka not online container mode)
- Build [Ca/Kf]CoreOffline libs only if not in CBM_ONLINE_STANDALONE (aka not online container mode)
- Use AlgoOffline as dep for libs CbmSimDigitizationSteer CbmAtConverterSteer CbmRecoOfflineSteer

Administrator authored 1 year ago and Pierre-Alain Loizeau committed 1 year ago

The scripts are the old way to define settings fro geant3 and geant4 and are
still used in some of the test macros. With this commit the changes already
implemented in the new class CbmGeant4Settings some time ago with commits
cb453d4b and 982c4b76 are added to fix errors during Geant4 initilisation.

Alexandru Bercuci authored 1 year ago and Florian Uhlig committed 1 year ago

Move macro code from Create_geometry_* macro to namespace cbm::trd:geo.
Implement the latest modifications to the design of the chamber and FEB as they are proposed for day 1.

Radim Dvorak authored 1 year ago and Florian Uhlig committed 1 year ago

The current implementation works only for event-by-event based digitisation and reconstruction. When running time based the results will be definitely wrong.

Closes #3195

Apar Agarwal authored 1 year ago and Administrator committed 1 year ago

Earlier the pads on one edge of the frame used to be under estimated on one
side while they were overestimated on the opposite side.
This problem should now be rectified by taking into account the special case
of module boundaries.
Add special case of pad size being smaller than the spot radius

Simon Neuhaus authored 1 year ago and Pierre-Alain Loizeau committed 1 year ago

- change outer dimension of RICH detector
  - change width and length of RICH
  - change mainframe
    - make shape in top view rectangular
    - make slope on front
    - reuse mainFrame3
      - change mainframe5 to trapezoid form
      - add new mainframe7 which replace some of the mainFrame2
    - cutoff shieldingbox
      - add new mainframe8 in x-direction
    - reduce some mainframes by a length of (2x) thickness from the mainframe to reduce overlapping
    - cutoff a cubic where mainframes cross each other
  - change the length of the pillars
- Rich entrance window
  - change width of the entrance window
  - add 10cm wide and 2cm thick Aluminum flange
  - reduce size of entrance window without flange a bit
- Rich exit window
  - add 10cm wide and 2cm thick Aluminum flange
  - change width to 569cm
  - change hight to 384cm
  - change material of exit window from kapton to Polycarbonat
  - increase thickness to 1cm
- Add Studs to each pillar
  - 10cm x 10cm 0.2cm thick Aluminum
- Add Connections between pillars
  - 6cm x 2.5cm 0.2cm thick Aluminum
- Make beampipe to beampipe tunnel
  - change material to carbon
  - change radius at entrance and exit
  - change pipe thickness to 0.3cm
  - increase the length by 0.5cm
  - change and increase cutoff at middle mirror parts
  - increase hole in sensitivity plane (move subtracted Cone)
  - remove belt types 4 and 5 because of overlap with the beampipe tunnel
- change CreateStuds
  - CreateStuds now need length and angle
  - selecting of length and angle with fix value if conditions is removed
  - remove some typo failurs where was schieldingbox written instead of shieldingbox.
- renamed Polycarbonat to RICH_Polycarbonat in media.geo
- change cutoff cone in exit, entrance window and senseplane to tubes to fix issue with a small structure hanging in the circle.
- add some comments about creating older version of geometry.
- make output reproduceble and change commet about producing older versions.

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

When comapring real numbers for equality one shouldn't compare the difference
of both values with zero. Due to rounding effects the result can be slightly
differnt from zero. If the difference of the values is smaller than a a small
value ( e.g. 0.00001 ) both values are equal.

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

Up to now the input and event numbers where added to the match when the match
was created. In time based mode the digi and match objects are not necessarily
created at the same event to witch the MvdPoint belongs. This results in
wrongly matching the digis to the MvdPoints.
Add information about input and event number to the pixel charge to store the
the correct information about input and event numbers. Use this information
when creating the match object.

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.