FACT++  1.0
uint64_t reportIncomplete ( const shared_ptr< EVT_CTRL2 > &  evt,
const char *  txt 
)

Definition at line 762 of file EventBuilder.cc.

References factOut(), factPrintf(), gi_NumConnect, MessageImp::kWarn, NBOARDS, proc1(), processingQueue1, and str.

Referenced by mainloop().

763 {
764  factPrintf(MessageImp::kWarn, "skip incomplete evt (run=%d, evt=%d, n=%d, %s)",
765  evt->runNum, evt->evNum, evtCtrl.size(), txt);
766 
767  uint64_t report = 0;
768 
769  char str[1000];
770 
771  int ik=0;
772  for (int ib=0; ib<NBOARDS; ib++)
773  {
774  if (ib%10==0)
775  str[ik++] = '|';
776 
777  const int jb = evt->board[ib];
778  if (jb>=0) // data received from that board
779  {
780  str[ik++] = '0'+(jb%10);
781  continue;
782  }
783 
784  // FIXME: This is not synchronous... it reports
785  // accoridng to the current connection status, not w.r.t. to the
786  // one when the event was taken.
787  if (gi_NumConnect[ib]==0) // board not connected
788  {
789  str[ik++] = 'x';
790  continue;
791  }
792 
793  // data from this board lost
794  str[ik++] = '.';
795  report |= ((uint64_t)1)<<ib;
796  }
797 
798  str[ik++] = '|';
799  str[ik] = 0;
800 
802 
803  return report;
804 }
void factOut(int severity, const char *message)
void factPrintf(int severity, const char *fmt,...)
A warning, things that somehow might result in unexpected or unwanted bahaviour.
Definition: MessageImp.h:18
list< shared_ptr< EVT_CTRL2 > > evtCtrl
char str[80]
Definition: test_client.c:7
uint gi_NumConnect[NBOARDS]
Definition: EventBuilder.cc:82
#define NBOARDS
Definition: BasicGlCamera.h:4

+ Here is the call graph for this function:

+ Here is the caller graph for this function: