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/10/31 13:30]
pereira [TPPACs packet]
event_filter [2015/11/01 08:11]
pereira [Mesytec TDC (MTDC) packet]
Line 283: Line 283:
  
  
-Where Ch is the segment number (from 0 to 15, being segment 0 the most upstream). The Filter gives an energy word for each segment as long as **energy** is greater than 0.+where Ch is the segment number (from 0 to 15, being segment 0 the most upstream). The Filter gives an energy word for each segment as long as **energy** is greater than 0.
  
  
Line 399: Line 399:
  
  
 +
 +
 +
 +
 +==== Hodoscope packet ====
 +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]].
 +
 +Each of the **two first packets** look like:
 +
 +  * **Packet Length** (self-inclusive)
 +
 +^    A number from 3 to 19    ^^^^^^^^^^^^^^^|
 +| 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 |
 +
 +
 +  * **Packet Tag**
 +
 +^    0x58B0    ^^^^^^^^^^^^^^^|
 +| 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 |
 +
 +
 +  * **Hodoscope Sub-packet "Energy" Tag** 
 +
 +
 +^    0x0000 or 0x0001    ^^^^^^^^^^^^^^^|
 +| 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 |
 +
 +where 0x0000 labels the energy sub-packet of the first group of crystals from 1 to 16, and 0x00001 labels the second group of crystals from 17 to 32.
 +
 +
 +
 +  * **Energy values**
 +The energy from each of the two Phillips 7164H ADC modules is given by a series of words that look like: 
 +
 +^  ^^^ Ch ^   energy   ^^^^^^^^^^^|
 +| 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 |
 +
 +
 +where Ch is the crystal number in the packet (from 0 to 15). The Filter gives an energy word for each crystal as long as **energy** is greater than 0.
 +
 +
 +
 +
 +
 +The **third hodoscope packet** with information from the coincidence register looks like:
 +
 +  * **Packet Length** (self-inclusive)
 +
 +^    5    ^^^^^^^^^^^^^^^|
 +| 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 |
 +
 +
 +  * **Packet Tag**
 +
 +^    0x58B0    ^^^^^^^^^^^^^^^|
 +| 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 |
 +
 +
 +  * **Hit pattern** 
 +
 +
 +^    hit pattern of first 16 crystals   ^^^^^^^^^^^^^^^|
 +| 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 |
 +
 +
 +
 +^    hit pattern of crystals 16 to 32   ^^^^^^^^^^^^^^^|
 +| 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 |
 +
 +
 +
 +  * **Time**
 +The Hodoscope OR time (from an ORTEC TAC encoded in the [[S800 USB DAQ data format#Tag 0x7167: Phillips 7164 ADC module for CRDC anodes (energies and TAC)|S800 Phillips 7164H ADC]]) is given by: 
 +
 +^  empty ^^^^   time   ^^^^^^^^^^^|
 +| 0 | 0 | 0 | 0 | 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 |
  
  
Line 462: Line 548:
 The **connector** number is defined between 0 and 3, and it is related to the pad number (**pad**). The value 0 refers to the first 64 pads, and correspond to the strips in the dispersive direction of the first TPPAC. The value 1 is for pads between 63 and 127, and includes the strips in the non-dispersive direction of the first TPPAC. The value 2 corresponds to pads between 128 and 191, which are associated to the strips in the dispersive direction of the second TPPAC. Finally, the value 3 corresponds to pads between 191 to 256, and covers the strips in the non-dispersive direction of the second TPPAC. The **connector** number is defined between 0 and 3, and it is related to the pad number (**pad**). The value 0 refers to the first 64 pads, and correspond to the strips in the dispersive direction of the first TPPAC. The value 1 is for pads between 63 and 127, and includes the strips in the non-dispersive direction of the first TPPAC. The value 2 corresponds to pads between 128 and 191, which are associated to the strips in the dispersive direction of the second TPPAC. Finally, the value 3 corresponds to pads between 191 to 256, and covers the strips in the non-dispersive direction of the second TPPAC.
  
-The value of *pad* is given by **index** + **connector** x 64, where **index** is depends on the value of **channel** and **connector** according to the table below, where the second column shows the index values for **connector**=0 or 2, and the third column corresponds to the index values for **connector**=1 or 3:+The value of **pad** is given by **index** + **connector** x 64, where **index** is depends on the value of **channel** and **connector** according to the table below, where the second column shows the index values for **connector**=0 or 2, and the third column corresponds to the index values for **connector**=1 or 3:
  
 ^channel^index^index|    ^channel^index^index|   
Line 531: Line 617:
  
  
 +
 +
 +
 +==== Mesytec TDC (MTDC) packet ====
 +The MTDC packet includes the multiple timing values [[S800 USB DAQ data format#encoded in the Mesytec MTDC for a given event. The packet looks like:
 +
 +
 +
 +
 +
 +
 +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]]. 
 +
 +
 +  * **Packet Length** (self-inclusive)
 +
 +^    A number from 2 to 10    ^^^^^^^^^^^^^^^|
 +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | X | X | X |
 +| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
 +
 +
 +  * **Packet Tag**
 +
 +^    0x5802    ^^^^^^^^^^^^^^^|
 +| 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 |
 +| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
 +
 +
 +  * **Time-of-flight values**
 +The time-of-flight information for each channel is coded in words that look like:
 +
 +^  ^^^ Ch ^  time  ^^^^^^^^^^^|
 +| 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 |
 +
 +Up to eight of these words can be present (depending on wheter **time** is greater than 0): six from the Phillips TDC, and two from the XFP-FP and OBJ-FP TACs. The channel number Ch is given by:
 +
 +^ Ch ^ Source  |
 +| 6 | Phillips TDC time from the A1900 IM2 north scintillator (optional)  |
 +| 7 | Phillips TDC time from the A1900 IM2 south scintillator (optional) 
 +| 12 | Phillips TDC time from the RF    |
 +| 13 | Phillips TDC time from the OBJ scintillator  |  
 +| 14 | Phillips TDC time from the XFP scintillator  |  
 +| 15 | Phillips TDC time from the LaBr (optional)  |  
 +| 4 | XFP-FP time-of-flight from TAC  | 
 +| 5 | OBJ-FP time-of-flight from TAC  | 
 +
 +
 +Note that the time values from the Phillips TDC are subtracted by SpecTcl to the time from the S800 trigger E1 up (encoded in the [[#trigger packet|trigger packet]]) in order to calculate the corresponding time-of-flight. On the other hand, the times from the TACs (Ch 4 and 5) correspond to actual time-of-flight values. 
  
  
event_filter.txt ยท Last modified: 2019/05/24 13:58 by pereira