User Tools

Site Tools


pre-unpacker

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
pre-unpacker [2017/06/11 17:36]
pereira [Using the Sweeper Pre-unpacker]
pre-unpacker [2017/06/26 13:24] (current)
pereira [Substructure fpic]
Line 32: Line 32:
  
 ===== Using the Sweeper Pre-unpacker ===== ===== Using the Sweeper Pre-unpacker =====
-In order to include the Sweeper Pre-unpacker, the user needs to follow a series of steps (for more details, please contact the Sweeper Device Physicist Jorge Pereira [[pereira@nscl.msu.edu]]) or Ron Fox [[fox@nscl.msu.edu]]):+In order to include the Sweeper Pre-unpacker, the user needs to follow a series of steps (for more details, please contact the Sweeper Device Physicist Jorge Pereira ([[pereira@nscl.msu.edu]]) or DAQ expert Ron Fox ([[fox@nscl.msu.edu]]):
  
   * The analysis-software compiler must include the library **libSweeperUnpacker.so** along with some header files. Their current location (June 2017) is ''/user/sweeper/develop/unpacker/library/src'', for **libSweeperUnpacker.so**, and ''/user/sweeper/develop/unpacker/library/inc'' and ''/user/sweeper/develop/unpacker/library/inc/Sweeper'', for the header files.     * The analysis-software compiler must include the library **libSweeperUnpacker.so** along with some header files. Their current location (June 2017) is ''/user/sweeper/develop/unpacker/library/src'', for **libSweeperUnpacker.so**, and ''/user/sweeper/develop/unpacker/library/inc'' and ''/user/sweeper/develop/unpacker/library/inc/Sweeper'', for the header files.  
Line 44: Line 44:
 <code cpp> <code cpp>
 #include <Sweeper.h> #include <Sweeper.h>
 +#include <SweeperEvent.h>
  
 #include <Event.h> #include <Event.h>
Line 77: Line 78:
  
  
-In the above example, all the unpacked data are encoded in the structure ''event'' (type **SweeperEvent**). Thus, all that the user needs to do is to handle the variables (organized in sub-structures) provided in the ''event'' structure. The list of **SweeperEvent** sub-structures and corresponding variables are described below:+In the above example, all the unpacked data are encoded in the structure **event** (type **SweeperEvent**). Thus, all that the user needs to do is to handle the variables (organized in sub-structures) provided in the **event** structure. The list of **SweeperEvent** sub-structures and corresponding variables are described below:
  
 ==== Substructure fpic ==== ==== Substructure fpic ====
 This substructure contains information about the focal-plane ion chamber This substructure contains information about the focal-plane ion chamber
   * **fpic.hasdata** (bool): logic variable which is TRUE when the structure contains valid data    * **fpic.hasdata** (bool): logic variable which is TRUE when the structure contains valid data 
-  * **fpsci.raw[0-15]** (uint16_t): energy array (Phillips 7164 ADC module) from each of the 16 detector pads+  * **fpic.raw[0-15]** (uint16_t): energy array (Phillips 7164 ADC module) from each of the 16 detector pads
  
  
Line 112: Line 113:
  
   * **mtdc.hasdata** (bool): logic variable which is TRUE when the structure contains valid data    * **mtdc.hasdata** (bool): logic variable which is TRUE when the structure contains valid data 
-  * **hits.data[0-31]** (uint16_t): array with number of "hits" for each channel +  * **hits[0-31]** (uint16_t): array with number of "hits" for each channel 
-  * **hits.raw[0-31]** (uint16_t): array with time of first hit of each channel +  * **raw[0-31]** (uint16_t): array with time of first hit of each channel 
-  * **hits.data[0-31][maximum number-of-hits=31]** (uint16_t): array with times for each hit and channel+  * **data[0-31][maximum number-of-hits=31]** (uint16_t): array with times for each hit and channel
  
  
pre-unpacker.1497217007.txt.gz · Last modified: 2017/06/11 17:36 by pereira