Sweeper Magnet

User Tools

Site Tools

Trace: • sweeper_usb_daq_data_format
sweeper_usb_daq_data_format

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
sweeper_usb_daq_data_format [2017/05/07 16:58]
pereira [VME Crate data format] 		sweeper_usb_daq_data_format [2017/06/11 17:26] (current)
pereira [The Sweeper USB DAQ data format]
Line 1: Line 1:
 ====== The Sweeper USB DAQ data format ====== ====== The Sweeper USB DAQ data format ======
-Two crates are read by the Sweeper DAQ software (one CAMAC and one VME), but more could be easily added to the software. This section describes the data format coming from each controller. (Please, note that this data format  is irrelevant for the user; this is so because the USB data are "pre-unpacked" by the [[Pre-unpacker|Sweeper Pre-unpacker]] software before being distributed to the user.)+Two crates are read by the Sweeper DAQ software, one CAMAC and one VME. Data from each of these controllers are pushed into [[http://docs.nscl.msu.edu/daq/newsite/nscldaq-11.2/c43.html|ring buffers ]] (**rawccusb** for CCUSB and **rawvmusb** for VMUSB). The Sweeper Event Builder (EVB) reads  data from these ring-buffers, correlates them on the basis of their time stamps, and outputs the resulting data stream on the ring buffer **sweeper**. According to the NSCLDAQ 11.x [[http://docs.nscl.msu.edu/daq/newsite/nscldaq-11.2/x4509.html|format]], data in the ring buffer **sweeper** will be organized in ring items, each consisting of two fragments, one for each controller. 
 + 
 +The structure of the data from the Sweeper EVB is schematically illustrated in the figure below: 
 +{{:wiki:diagram_ringitem_fromevb.png?800|Schematic representation of data format from Sweeper EVB}} 
 + 
 +Events from the Sweeper EVB will be encapsulated in ring items, consisting of header, a body header, and a body. The body part contains two fragments, one from each controller. Each fragment has a header, followed, again, by a ring item (with its corresponding header, body header, and body). 
 + 
 +The structure from the body of each fragment is described below in some detail. Please, note that this data format  is irrelevant for the user; this is so because the USB data are "pre-unpacked" by the [[Pre-unpacker|Sweeper Pre-unpacker]] software before being distributed to the user.
  
  
Line 26: Line 33:
 The tags and end tags identify the modules being read and encapsulate the data from each. The tags, end tags and their corresponding modules are listed below: The tags and end tags identify the modules being read and encapsulate the data from each. The tags, end tags and their corresponding modules are listed below:
  
-0x2367, 0xf367: LeCroy ULM2367 Trigger module+  * 0x2367, 0xf367: LeCroy ULM2367 Trigger module 
 +   
 +  * 0x4300, 0xf300: LeCroy4300B FERA module for plastic scintillator energies
  
-0x4300, 0xf300: LeCroy4300B FERA module for plastic scintillator energies+  * 0x7164, 0xf164: Phillips7164 ADC module for ion chamber energies
  
-0x7164, 0xf164: Phillips7164 ADC module for ion chamber energies +  * 0x7167, 0xf167: Phillips7164 ADC module for CRDC anodes (energies and TAC)
- +
-0x7167, 0xf167: Phillips7164 ADC module for CRDC anodes (energies and TAC) +
- +
-0x7186, 0xf168: Phillips7186 TDC module for time-of-flights (DISCONTINUED)+
  
 +  * 0x7186, 0xf168: Phillips7186 TDC module for time-of-flights (DISCONTINUED)
 + 
  
  
Line 129: Line 136:
 The tags and end tags identify the modules being read, and encapsulate their data. The tags, end tags and their corresponding modules are listed below: The tags and end tags identify the modules being read, and encapsulate their data. The tags, end tags and their corresponding modules are listed below:
  
-0x5901, 0xf901: trigger pattern from Level-3 trigger module (XLM72) +  * 0x5901, 0xf901: trigger pattern from Level-3 trigger module (XLM72) 
- +  
-0x5903, 0xf903: time stamp pattern from Level-3 trigger module (XLM72) +  * 0x5903, 0xf903: time stamp pattern from Level-3 trigger module (XLM72) 
- +  
-0xcfdc, 0xffdc: XLM72 module configure to read CRDC1 pad signals +  * 0xcfdc, 0xffdc: XLM72 module configure to read CRDC1 pad signals 
- +  
-0xcfdd, 0xffdd: XLM72 module configure to read CRDC2 pad signals +  * 0xcfdd, 0xffdd: XLM72 module configure to read CRDC2 pad signals
- +
-0x59b0, 0xf9b0: MADC-32 module for Hodoscope+
  
-0x59b0, 0xf9b0: MADC-32 module for Segmented Target +  * 0x59b0, 0xf9b0: MADC-32 module for Hodoscope 
 +  
 +  * 0x59b0, 0xf9b0: MADC-32 module for Segmented Target 
  
-0x0ddc, 0xfddc: MTDC-32 module for time-of-flights+  * 0x0ddc, 0xfddc: MTDC-32 module for time-of-flights
sweeper_usb_daq_data_format.1494190728.txt.gz · Last modified: 2017/05/07 16:58 by pereira

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki