GtReceiver + GEBSort: Difference between revisions
No edit summary |
|||
Line 16: | Line 16: | ||
There is server port 9001. should be working fine. | There is server port 9001. should be working fine. | ||
The gtReceover will save data at the location it being called. In the star_run.sh, the path is set to the data folder. | |||
the argument of the gtReceiver is | |||
gtReceiver [IP] [filename] [max_file_size_in_byte] [data_type] | |||
IP = IP for the IOC, it already bookmarked in /etc/hosts, nickname like ioc1, ioc2, ioc3, ioc4 can be used. | |||
data_type must be 14 for helios data. it is related to the EventBuilder | |||
= GEBMerge = | = GEBMerge = |
Revision as of 19:02, January 21, 2021
Introduction
To get the data from the digitizer, we need the program "gtReceiver".
To decode the raw data, we need GEBSort.
The version of the firmware of the digitizer, the gtReceiver, and the GEBSort have to be matched to properly extract the data.
gtReceiver
gtReceiver is a C program that connect the IOC and retrieving the data from VME.
in HELIOS DAQ, the folder ~/gtReceiver_digios stored the source code.
The source code should be working fine. (tested for music daq 2020-11-19).
There is server port 9001. should be working fine.
The gtReceover will save data at the location it being called. In the star_run.sh, the path is set to the data folder.
the argument of the gtReceiver is
gtReceiver [IP] [filename] [max_file_size_in_byte] [data_type] IP = IP for the IOC, it already bookmarked in /etc/hosts, nickname like ioc1, ioc2, ioc3, ioc4 can be used. data_type must be 14 for helios data. it is related to the EventBuilder
GEBMerge
EventBuilder (old name : GEBSort)
The GEBSort is used for gammasphere, it build events and analysis data, and it split out histogram only.
The EventBuilder is a simplified code from GEBSort. It only build events, and split out root tree.
There are two versions: EventBuilder and EventBuilder_trace
The control parameters for them is the working/GEBSort.chat
$cat GEBSort.chat # NOTE: both the input (geb or file) and # the output (rootfile or mapfile) # are now specified on the command line of GEBSort # all other parameters are specified in this chat file ;DumpEvery 5 #------------------------------------------- # basic sort parameters # number of event in a block nevents 1000000000 # number of event in a block to be printed out printevents 1 # number of event to be written in Log modwrite 100000 # timestamp to be written in Log tsnumwrites 100000 # event build windows timewin 1000 #------------------------------------------- exit
The most important parameter is the timewin. It defines the time-window for an event: whenever data is clustered in the length of the time-window, it is an event.