This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
sweeper_usb_daq_data_format [2017/06/09 18:04] pereira [The Sweeper USB DAQ 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. Data from each of these controllers are pushed into ring buffers (**rawccusb** for CCUSB and **rawvmusb** for VMUSB). The Sweeper Event Builder (EVB) reads data from these ring-buffers, | + | Two crates are read by the Sweeper DAQ software, one CAMAC and one VME. Data from each of these controllers are pushed into [[http:// |
| + | The structure of the data from the Sweeper EVB is schematically illustrated in the figure below: | ||
| + | {{: | ||
| + | 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). | ||
| - | This section describes | + | The structure from the body of each fragment is described below in some detail. Please, note that this data format |