Feature #505

Support #502: Completion of libsbsdig

Add decoded data into the output

Added by Eric Fuchey 9 months ago. Updated 8 months ago.

Status:ResolvedStart date:11/15/2019
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:-Estimated time:4.00 hours
Target version:-Spent time:7.00 hours
Responsible:

Description

In addition to the data words, we want ADC and TDC values

History

#1 Updated by Eric Fuchey 9 months ago

  • % Done changed from 0 to 80

Added decoded ADC and TDC values. ADC lack pedestal subtraction, and TDC lack a reference trigger time.

#2 Updated by Eric Fuchey 9 months ago

  • Status changed from New to Feedback
  • % Done changed from 80 to 90

Decoded ADC values have been added in the output file as <detname>_adc, and are pedestal subtracted.
Decoded TDC values have been added in the output file as <detname>_tdc_l (for leading times), and <detname>_tdc_t (for trailing times)
They both appear relative to the "trigger" time, which by our convention is 0 (the trigger jitter is already included in the evaluation of the leading and trailing times).
For the non ADC words (headers or TDCs), <detname>_adc have been filled with a "stupid" value of -1000000, which cannot correspond to any value -subtracted or not-reachable by any ADC or TDC.
Same logic has been applied for the two different types of TDC values e.g for a non-leading time TDC word, the field <detname>_tdc_l is filled with the same "stupid" value.
One may just look at the data safely basically requiring the considered variable to be above that value.

That allows to have all output vectors of the same size, and going through each hit while analyzing the data, it ensure that looking into all vectors corresponding to that hit, the right dataword corresponds to the right channel number, and to the right decoded value, etc.

#3 Updated by Eric Fuchey 8 months ago

  • % Done changed from 90 to 100

#4 Updated by Eric Fuchey 8 months ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF