Changes from mCBM 2022 prod to mCBM MQ devices and execution
All threads resolved!
All threads resolved!
Compare changes
Files
2- Pierre-Alain Loizeau authored
- The check for consecutive TS indices was still called when receiving Missing TS Data messages even if the bypass flag was set => Surround the call with proper if condition - The range when taking the digis data out of the unpacked timeslice to the DigiEvent was missing the last digi for all detectors => Increment the stop iterator to make sure it is included - In rare case, the device can be pulled down before the Init method is called/finished, which led to a segfault => add an InitDone flag + use it to control delete operations in the destructor
+ 17
− 4
@@ -168,6 +168,7 @@ try {
@@ -254,7 +255,10 @@ bool CbmDeviceDigiEventSink::HandleMissTsData(FairMQMessagePtr& msg, int /*index
@@ -633,11 +637,13 @@ CbmDeviceDigiEventSink::~CbmDeviceDigiEventSink()
@@ -800,6 +806,7 @@ std::vector<CbmDigiEvent> CbmEventTimeslice::GetSelectedData()
@@ -824,6 +831,7 @@ std::vector<CbmDigiEvent> CbmEventTimeslice::GetSelectedData()
@@ -848,6 +856,7 @@ std::vector<CbmDigiEvent> CbmEventTimeslice::GetSelectedData()
@@ -872,6 +881,7 @@ std::vector<CbmDigiEvent> CbmEventTimeslice::GetSelectedData()
@@ -898,6 +908,7 @@ std::vector<CbmDigiEvent> CbmEventTimeslice::GetSelectedData()
@@ -922,6 +933,7 @@ std::vector<CbmDigiEvent> CbmEventTimeslice::GetSelectedData()
@@ -946,6 +958,7 @@ std::vector<CbmDigiEvent> CbmEventTimeslice::GetSelectedData()