User Tools

Site Tools


event_filter

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
event_filter [2015/11/01 08:25]
pereira [Mesytec TDC (MTDC) packet]
event_filter [2018/02/01 13:46]
pereira [Hodoscope packet]
Line 1: Line 1:
-====== Event Filter (S800 Filter) ======+====== S800 data format from Event Filter (S800 Filter) ====== 
 +This page describes the data format assembled by the S800 filter. The data is written in a series of 16-bit unsigned integers, subsequently referred to as ''words''. This format is suitable for the output of most of the modules presently used in the S800, and in the case where 32 bit integers are needed, the proper unpacking procedures will be given. 
 + 
 +===== General packet structure ===== 
 +All data is written using the concept of "packets". The format of a packet is: 
 + 
 +^ Length ^ Packet Tag ^ Packet Data | 
 + 
 +Length: a count of the number of words in the packet, inclusive of the length word itself 
 + 
 +Packet Tag: a predefined integer indicating the type of data found in the Packet Data 
 + 
 +Packet Data: the data themselves. These can be data read from the modules or a sub packet. Sub packets have identical structure to main packets. Using this format all data can be placed in nested packets, and coding decisions on how to unpack the Packet Data can be made by examination of the preceding Packet Tag. Packets (including sub packets) can also be skipped by jumping ahead Length words in the buffer. 
  
-The trigger bits words indicates which bits were set during the event. The encoding of the bits is the following: 
  
 In this section, each 16-bit word sent by the Filter is described by a 16x3-table diagram. The first row includes the value, either in decimal or hexadecimal format, or a descriptive note. The second row shows the value in binary ("X"s are used to describe arbitrary values that vary from event to event). The last row shows the bit number.  In this section, each 16-bit word sent by the Filter is described by a 16x3-table diagram. The first row includes the value, either in decimal or hexadecimal format, or a descriptive note. The second row shows the value in binary ("X"s are used to describe arbitrary values that vary from event to event). The last row shows the bit number. 
Line 7: Line 19:
  
  
-==== Time-stamp packet ====+ 
 +===== Time-stamp packet =====
 The timestamp is encoded in the [[S800 USB DAQ data format#Tag 0x5803: XLM72 time stamp module|XLMV72 time-stamp module]] for each event as a 64-bit word. The Event Filter parses it as a set of four consecutive 16-bit words. The timestamp is encoded in the [[S800 USB DAQ data format#Tag 0x5803: XLM72 time stamp module|XLMV72 time-stamp module]] for each event as a 64-bit word. The Event Filter parses it as a set of four consecutive 16-bit words.
  
Line 13: Line 26:
   * **Packet Length** (self-inclusive)   * **Packet Length** (self-inclusive)
  
-^       ^^^^^^^^^^^^^^^|+^       ^^^^^^^^^^^^^^^|
 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 |
 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
Line 55: Line 68:
  
  
-==== Event-number packet ====+===== Event-number packet =====
 The event-number is given by the VMUSB scaler channels as a 48-bit word coded in two 32-bit words. The Event Filter parses it and re-formats it as a three 16-bit words. The event-number is given by the VMUSB scaler channels as a 48-bit word coded in two 32-bit words. The Event Filter parses it and re-formats it as a three 16-bit words.
  
Line 61: Line 74:
   * **Packet Length** (self-inclusive)   * **Packet Length** (self-inclusive)
  
-^       ^^^^^^^^^^^^^^^|+^       ^^^^^^^^^^^^^^^|
 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 |
 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
Line 97: Line 110:
  
  
-==== Trigger packet ====+===== Trigger packet =====
 The trigger packet includes a bit-pattern word (encoded  by the [[S800 USB DAQ data format#Tag 0x2367: Trigger module|ULM trigger module]]), with information about what sources triggered the event, and their corresponding time from the [[S800 USB DAQ data format#Tag 0x7186: Phillips 7186 TDC module for time-of-flights|Phillips 7186 TDC]]. The trigger packet includes a bit-pattern word (encoded  by the [[S800 USB DAQ data format#Tag 0x2367: Trigger module|ULM trigger module]]), with information about what sources triggered the event, and their corresponding time from the [[S800 USB DAQ data format#Tag 0x7186: Phillips 7186 TDC module for time-of-flights|Phillips 7186 TDC]].
  
Line 151: Line 164:
  
  
-==== Time-of-flight packet ====+===== Time-of-flight packet =====
 The time-of-flight packet includes all the timing values encoded in the [[S800 USB DAQ data format#Tag 0x7186: Phillips 7186 TDC module for time-of-flights|Phillips TDC]] and the XFP-FP and OBJ-FP ToF from the ORTEC TACs encoded in the [[S800 USB DAQ data format#Tag 0x7167: Phillips 7164 ADC module for CRDC anodes (energies and TAC)|S800 Phillips 7164H ADC]].  The time-of-flight packet includes all the timing values encoded in the [[S800 USB DAQ data format#Tag 0x7186: Phillips 7186 TDC module for time-of-flights|Phillips TDC]] and the XFP-FP and OBJ-FP ToF from the ORTEC TACs encoded in the [[S800 USB DAQ data format#Tag 0x7167: Phillips 7164 ADC module for CRDC anodes (energies and TAC)|S800 Phillips 7164H ADC]]. 
  
Line 194: Line 207:
  
  
-==== Scintillator packet ====+===== Scintillator packet =====
 The scintillator packet includes the energy (encoded in the [[S800 USB DAQ data format#Tag 0x4300: FERA module for plastic scintillator energies|FERA LeCroy module]]) and time (encoded in the [[S800 USB DAQ data format#Tag 0x7186: Phillips 7186 TDC module for time-of-flights|Phillips TDC]]) of the [[Detectors#Plastic scintillators|S800 FP scintillator]] signals. In the original configuration, there were 3 scintillators (E1, E2, and E3) which were later reduced to just one (E1) after the installation of the Hodoscope.  The scintillator packet includes the energy (encoded in the [[S800 USB DAQ data format#Tag 0x4300: FERA module for plastic scintillator energies|FERA LeCroy module]]) and time (encoded in the [[S800 USB DAQ data format#Tag 0x7186: Phillips 7186 TDC module for time-of-flights|Phillips TDC]]) of the [[Detectors#Plastic scintillators|S800 FP scintillator]] signals. In the original configuration, there were 3 scintillators (E1, E2, and E3) which were later reduced to just one (E1) after the installation of the Hodoscope. 
  
Line 239: Line 252:
  
  
-==== Ion-Chamber packet ====+===== Ion-Chamber packet =====
 The Ion-chamber packet includes the energies of the [[Detectors#Ionization chamber|16 ion-chamber segments]] encoded in one of the [[S800 USB DAQ data format#Tag 0x7164: Phillips 7164 ADC module for ion chamber energies|Phillips 7164H ADC]]. The Ion-chamber packet includes the energies of the [[Detectors#Ionization chamber|16 ion-chamber segments]] encoded in one of the [[S800 USB DAQ data format#Tag 0x7164: Phillips 7164 ADC module for ion chamber energies|Phillips 7164H ADC]].
  
Line 245: Line 258:
   * **Packet Length** (self-inclusive)   * **Packet Length** (self-inclusive)
  
-^    A number from 4 to 18    ^^^^^^^^^^^^^^^|+^    A number from 4 to 20    ^^^^^^^^^^^^^^^|
 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | X | X | X | X | X | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | X | X | X | X | X |
 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
Line 258: Line 271:
  
  
-  * **Sub-packet "Energy" Tag**+  * **Sub-packet "Energy" Length** (self-inclusive)
  
-   0x5821    ^^^^^^^^^^^^^^^| +  A number from 2 to 18    ^^^^^^^^^^^^^^^| 
-| 0 | | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | |+| 0 | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | X | X | X | X |
 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
  
  
  
-  * **Sub-packet "Energy" Length** (self-inclusive)+  * **Sub-packet "Energy" Tag**
  
-  A number from 2 to 16    ^^^^^^^^^^^^^^^| +   0x5821    ^^^^^^^^^^^^^^^| 
-| 0 | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | X | X | X | X |+| 0 | | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | |
 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
 +
 +
  
  
Line 288: Line 303:
  
  
-==== CRDC packets ====+===== CRDC packets =====
 The Filter provides two CRDC packets: one for [[Detectors|Cathode Readout Drift Chambers (CRDC)|CRDC1]] and one for [[Detectors|Cathode Readout Drift Chambers (CRDC)|CRDC2]]. Each CRDC packet is divided in two sub-packets: the "Raw" sub-packet with information about the pads energies (encoded in the [[S800 USB DAQ data format#Tag 0xCFDC: XLM72V crdc1 pad readout module|CRDCs XLM72 modules]]), and the "Anode" sub-packet with anode energy and time information encoded in the CRDCs [[S800 USB DAQ data format#Tag 0x7167: Phillips 7164 ADC module for CRDC anodes (energies and TAC)|Phillips ADC]]. In the following, we describe the structure of the packet provided by the Filter for each CRDC. The Filter provides two CRDC packets: one for [[Detectors|Cathode Readout Drift Chambers (CRDC)|CRDC1]] and one for [[Detectors|Cathode Readout Drift Chambers (CRDC)|CRDC2]]. Each CRDC packet is divided in two sub-packets: the "Raw" sub-packet with information about the pads energies (encoded in the [[S800 USB DAQ data format#Tag 0xCFDC: XLM72V crdc1 pad readout module|CRDCs XLM72 modules]]), and the "Anode" sub-packet with anode energy and time information encoded in the CRDCs [[S800 USB DAQ data format#Tag 0x7167: Phillips 7164 ADC module for CRDC anodes (energies and TAC)|Phillips ADC]]. In the following, we describe the structure of the packet provided by the Filter for each CRDC.
  
Line 403: Line 418:
  
  
-==== Hodoscope packet ====+===== Hodoscope packet =====
 The Filter parses the [[Detectors#Hodoscope|Hodoscope]] information encoded in the two  The Filter parses the [[Detectors#Hodoscope|Hodoscope]] information encoded in the two 
 [[S800 USB DAQ data format#Tag 0x7165: Phillips 7164 ADC module for hodoscope energies 0 through 15|Phillips 7164 ADCs]] and re-formats the data in three packets, two with the energies of the two groups crystals (from 1 to 16 and from 17 to 32), and the third one with the hit pattern recorded in the [[S800 USB DAQ data format#Tag 0x4448: LeCroy4448 coincidence register module for hodoscope hit pattern|LeCroy 4448 coincidence-register module]]. [[S800 USB DAQ data format#Tag 0x7165: Phillips 7164 ADC module for hodoscope energies 0 through 15|Phillips 7164 ADCs]] and re-formats the data in three packets, two with the energies of the two groups crystals (from 1 to 16 and from 17 to 32), and the third one with the hit pattern recorded in the [[S800 USB DAQ data format#Tag 0x4448: LeCroy4448 coincidence register module for hodoscope hit pattern|LeCroy 4448 coincidence-register module]].
Line 462: Line 477:
 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 |
 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
 +
 +
 +
 +  * **Hodoscope Sub-packet "Hit-pattern" Tag** 
 +
 +
 +^    0x0002   ^^^^^^^^^^^^^^^|
 +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | X |
 +| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
 +
  
  
Line 489: Line 514:
  
  
-==== TPPACs packet ====+===== TPPACs packet =====
 The Filter parses and re-formats information from the [[Detectors#Tracking Parallel Plate Avalanche Counters (TPPAC)|Tracking PPACs]] encoded in the [[S800 USB DAQ data format#Tag 0x5870: XLM72V tracking ppac readout module|XLM72 TPPACs module]]. The new packet includes both TPPACs; its structure is very similar to that from the CRDCs. The Filter parses and re-formats information from the [[Detectors#Tracking Parallel Plate Avalanche Counters (TPPAC)|Tracking PPACs]] encoded in the [[S800 USB DAQ data format#Tag 0x5870: XLM72V tracking ppac readout module|XLM72 TPPACs module]]. The new packet includes both TPPACs; its structure is very similar to that from the CRDCs.
  
Line 620: Line 645:
  
  
-==== Mesytec TDC (MTDC) packet ====+===== Mesytec TDC (MTDC) packet =====
 The MTDC packet includes the multiple timing values [[S800 USB DAQ data format#Tag 0x0DDC: Mesytec MTDC-32 module |encoded in the Mesytec MTDC]]. The packet looks like: The MTDC packet includes the multiple timing values [[S800 USB DAQ data format#Tag 0x0DDC: Mesytec MTDC-32 module |encoded in the Mesytec MTDC]]. The packet looks like:
  
Line 633: Line 658:
   * **Packet Tag**   * **Packet Tag**
  
-^    0x58E0    ^^^^^^^^^^^^^^^|+^    0x58F0    ^^^^^^^^^^^^^^^|
 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 |
 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
Line 642: Line 667:
  
  
-^^^^^  hit  ^^^^ channel ^^^^^^^|+  ^^^  hit  ^^^^^ channel ^^^^^^^|
 | 0 | 0 | 0 | X | X | X | X | X | X | X | X | X | X | X | X | X | | 0 | 0 | 0 | X | X | X | X | X | X | X | X | X | X | X | X | X |
 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
Line 651: Line 676:
 | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X |
 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
 +
 +
 +
 +
 +
 +
 +
 +
 +
  
  
event_filter.txt · Last modified: 2019/05/24 13:58 by pereira