RC_gui - graphical user interface
Under development.
Content
Introduction
Graphical user interface RC_gui provides a control of run.
It requires that a primary receiver, central slow control, and run control
processes are running (see How
to start DAQ).
RC_gui updates configuration and parameter files
which are used for electronics initialization and starts a data acquisition
(run). There are modules which parameters cannot be changed by RC_gui,
see Auxiliary modules section.
There are active images in the document. Commonly OK an CANCEL
buttons leads you through the windows which are opened by RC_gui.
Of course, other objects do not reacts exactly as it is done in a real
work, but we tried to do that rather realistic. So, you can try to use
buttons to navigate through the document. Please, look at the text around
images as it may contain explanations of problems you met.
Content
Main run control panel
This panel appears first and serves to control run. The states of buttons
are set in correspondence with a run status got from the data taking process.
After you pushed a button the status of run will be changed after one or
two accelerator cycles. Inactive buttons indicated by white labels.
This image is active: click on
an active button to see how it works.
|
Button
Action
Run
opens a next level windows to start run
Pause
suspends a data taking
Continue resumes the run
Slow ctrl opens windows
to control alarms and slow control processes
Exit GUI kills
RC_gui
only, all other processes are not affected.
You can do that and restart RC_gui again
Kill DAQ kills builder,
RC and RC_gui, see Kill
DAQ |
Content
Set run parameters
This image is active. Click on active buttons to see how it works.
|
This window and ones opened from it allows you to change run settings
and save new configuration and parameters in files for future use. Any
time as you click OK button default files with predefined names
are written. These files are used by other DAQ processes running on the
VME host and the main DAQ host. If you wish change nothing in comparison
with a previous run you can click
OK button in the window just as
it was opened. Pushing
Cancel button in the window you delete all
changes made on the current and more deep GUI levels. |
Field
Meaning/Action
-
Run number indicates the number of run which will
be started. Each time when one starts a run with Write file option
set to YES, the run number is incremented. If the Write file
choice is NO the run number is not incremented for next run.
-
Exposition Input field which allows one
to set how many events will be accepted or how long (astronomical
time) the data will be collected in the run. Placed on the right a choice
button provides sec/min/hours/events selection.
-
Mode You can
select PHYSICS or TUNING mode. These modes affect on
the performance of Slow Control procedures only. At start of run you can
change anything in electronics parameters for any mode. The difference
is in an execution of Slow Control procedures for a run in RUNNING
or PAUSED states:
-
In PHYSICS mode only predefined automatic calibrations are permitted,
see Set calibration.
-
The TUNING mode is foreseen to perform an automatic tuning of set
up parameters and any changes in electronics by SC procedures are permitted.
-
Std
The choice which you have here is Std/Calibration_1/Calibration_2/Calibration_3.
It means that you can select from four sets of electronics parameters.
Up to now nobody formulated what is Calibrations, so it was not
used and Std must be selected.
-
Set calibr Pushing this
button you opens a window which allows you to select which and how often
calibrations will be performed during a run. At the moment it is foreseen
that in each run one set of parameters is a main set, and three others
will be loaded time to time, at least one burst will be accepted and than
a main parameters will be restored. How often the calibration is performing
depends on how many bursts from one measurement to other you selected in
Set
calibration window.
-
Read-out
This menu contains three items: Open, Edit and Save as
and serves to set up parameters of readout electronics and save them in
configuration and parameter files for a future use.
-
Open
item allows one to select an
existing configuration file and then change
readout electronics parameters if it is needed.
-
Edit item works only
after you opened a configuration file. It is recommended to start any changes
from the opening of std.cfg file.
-
Save as item allows one to write current parameters of readout
electronics in a file for a future use. Please, do not keep a file for
your personal and rare use in a common directory, but move it somewhere
else. GUI can load configuration files only from the directory /home/run/param/RO
of VME host (for a safety reason), so before a use you must move your file_name.cfg
and file_name.par files back in it.
-
Trigger Allows to select
a trigger file to be loaded. When the file selector is opened the default
trigger file (containing the copy of last selected trigger file) is highlighted.
-
Write file This choice button determines
will be data written in a data file or it will not be. If you select NO,
the run number will not be changed, don't worry, already written file will
not be overwritten. Data files have names formed by run number, for example
1777.run and may have digital extension like 1777.run.1, 1777.run.2,
and so on. It comes from the requirement of off-line team to have short
data files. The extension number points out on the serial number of 300
Mbytes portion of data in a long run.
Content
Read-out electronics parameters
|
This window is opened just as you select Open item in Read-out
menu of Set run parameters window.
By the left mouse button you can select a configuration file to be loaded.
By default the daq.cfg file is selected and it corresponds
to the configuration and parameters of last run.
-
Rescan button serves to re-read the directory.
-
Cancel button returns to the previous window.
-
Ready button loads selected file in the program and opens a Read-out
configuration window.
|
Content
|
This window is opened if a cfg file is loaded
and allows one to switch on/off subdetectors, change a data suppression
mode and change parameters of read-out electronics. You can open this window
once more if you left it by OK button. For that select Edit
in Read-out menu of Set
run parameters window. |
-
Readout configuration frame contains pairs of buttons for
detectors.
-
Rounded button allows one to switch on or off the readout electronics
of detector in a whole. The colour of button indicates a state of detector
electronics:
-
yellow - all read-out modules are on,
-
red - part of modules are on off state,
-
grey - all modules are off.
Some detectors could not be switched off as they contain so called event
delimiter modules, if any modules of other detectors are on in the same
FERA branch. Corresponding warning message will appear in this case.
-
Rectangular button serves to
open a detector window and change module parameters one by one.
-
Suppression frame contains three radio buttons, which determines
how pedestal, and zero and overflow suppressions are performed for readout
electronics modules:
-
default -
it corresponds to standard set of parameters determined by subdetector
groups. Are pedestal and zero suppression on or off, it depends on the
detector and the module and described in a file all.sup on VME host
in the directory containing all others readout electronics files.
-
user defined - this mode
is used only for non-standard situations when you need to change something
in a limited number of modules for checks or investigations. If the previous
mode was default one, the selection of user defined mode
will change nothing until you will change parameters of detector or module
using lower level windows. The same is if the previous mode was no suppression
one. Be careful! Just as you come back to default or no
suppression mode all changes in suppression modes of detector modules
will be set back to requested mode and you will lose what was done!
-
no suppression - there is no pedestal, zero and overflow
suppression for all modules. It is used for pedestal measurements.
-
OK and CANCEL buttons serves to save or cancel made changes
in readout electronics parameters. If you pushed
-
OK - the current configuration and parameters are saved in
daq.cfg
and daq.par files which will be used by other processes to initialize
readout electronics before start of next run. If you wish to save them
for future use you can select than Save as item in Read-out
menu of Set run parameters window.
-
CANCEL - all changes will be lost, daq.cfg and daq.par
files will not be changed. If you wish to change them select than Open
item in Read-out menu of Set
run parameters window.
Content
Detector window
An example of a detector window is shown below. It contains detector
name, list of read-out modules and few buttons.
-
List of readout modules of the detector is shown in a selector frame.
By left mouse button you can select a module to change its position or
parameters.
-
Position button allows you to change the module position. The button
opens a position window and you
can change CAMAC branch, crate and slot values for the selected module.
This window shows a symbolic name of module and a computer which controls
it.
-
Parameters button opens a window to change module parameters. The
opened module window depends on the module hardware type:
-
Suppression button changes the mode of suppression for all modules of the
detector, if user defined mode was selected in Readout
configuration window.
Content
Change of module position
|
The window contains:
-
Sybolic name of module
-
Host - name of host which serves the module, you cannot change it
yet
-
Branch - CAMAC branch number
-
Crate - CAMAC crate number
-
Slot - CAMAC slot number
-
OK - change module position and return to Detector window
-
CANCEL - restore a previous module position and return to Detector
window
|
Change of module parameters
Any window opened to change module parameters contains at least:
-
Header indicating the module hardware type,
-
Symbolic name of module, which is used in on-line and off-line code
-
ON button. If this button ON, a code expects that information of
the module may appear in the data, in other case, the on-line code will
not try to find out the module data or read-out it.
-
Standard/Calibration choice which allows one to change one of four
sets of parameters (standard and three calibration ones, see Set
run parameters and Introduction
to DAQ).
-
OK button. Pushing this button you save made changes and return
to Detector window
-
CANCEL button. Pushing this button you ignore made changes (previous
parameters are restored) and returns to Detector
window
Other fields in the window depends on a module hardware type.
K427M - drift chamber control module
GUI for this module allows one to change a time window for drift chamber
readout electronics, set a check mode for work with a generator.
|
|
-
From, ch - the counter allows you to change the delay
between stop and input signals . On the left you see the delay value in
ns.
-
Window,ch - the counter allows you to change the width of time window
in channels of TDC. On the left the same value in ns.
-
To, ch - Shows the upper boundary of time range. You cannot change
it directly, but by Window or From counters.
|
Content
K429 - drift chamber track
finder
Really it is a trigger module. The GUI for it placed here only to provide
a possibility to work with it in more convenient way than with other trigger
modules. The module performs track finding or work in a transperent mode.
|
-
File - shows you the name of loaded file for track finding.
-
Change - allows you to open next level window to change loaded file.
It works only in user defined suppression mode.
-
Front panel output - must be ON (highlighted). OFF state is
for debugging only by experts.
-
Transparency mode - ON state means that there is no track finding.
Default state is OFF.
-
Time-out - if this button is ON and internal time-out is expired
the event is treated as good one. In OFF state the event analysis will
be completed so much time as it is needed.
|
Content
LeCroy 2366 register/scaler
The most of these modules are used as an event delimiters in FERA branches
to separate subevents collected in the branch. But they contains also information
which is used in the event building like time interval between events,
event time in the burst, and counting rates of subdetectors.
Available data frame in the window allows one to select data
which will be transferred by the module,
on the right there are buttons which set a mode of module.
|
-
Trigger number - it is a scaler which value is incremented
with a gate.
-
Register - input register
-
Scaler 1 - 32 bit scaler which may be cleared or not after
readout of event
-
Scaler 2 - 32 bit scaler which may be cleared or not after
readout of event
-
Gate enable - an input of module works as FERA GATE input, see the
module manual.
-
Clear enable - if ON, scalers are cleared after readout of each
event
-
Fast mode - if ON, the module works in Fast FERA mode (without
acknowledge signals during data transfer). Now all modules of this type
works in Fast mode.
-
Data delay - counter allows one to change a delay of beginning of
the data transfer relatively FERA GATE signal.
|
Content
LeCroy 3377 TDC
These modules used for different purposes. The GUI for them is limited
by the needs of the experiment.
It was agreed that all modules will work in Single data word mode (see
module manual).
|
-
Delay counter determines a minimum time interval between Gate
and Input signals.
-
Window counter determines a width of time window to detect Input
signals.
-
Bin width counter allows one to change LSB of TDC.
-
Range field informs you in which time interval hits will be recorded.
-
Trailing rounded button allows one to record both leading and trailing
edge of signals. If it is Off the leading edge is recorded.
-
Fast mode - to switch ON/OFF FERA fast mode. All LeCroy
3377 TDC modules in the experiment works in Fast mode.
-
Empty events - if the button is ON, module data containing
only headers will not be suppressed. It is only for debugging of the data
transfer!
|
Delay, Window and Bin width counters depend on
each other and provides only allowed values, so be careful when you change
them.
Content
LeCroy 4300 ADC
The GUI
control window allows you to set values which will be subtracted from the
measured charge, and selects pedestal subtraction, zero and overflow suppression
modes.
|
-
Pedestal subtraction rounded button - only if it is ON, the
values which you can see in a below placed frame will be subtracted from
the measured ones.
-
Input counter serves to select an input for which you will change
a subtracted value.
-
Subtract counter allows one to change a value subtracted from the
measured one for the selected input.
-
Data compression - if it is ON, the zero values will not
be transferred further. We always work with data compression ON!
-
Overflow suppression - if it is ON, the maximal possible
measured values (overflow ones) will be ignored. Commonly, Overflow
suppression is ON for modules used for time measurements, and
is OFF for amplitude measurements.
|
Content
MSGC control
There are predefined file names for control sequences and pedestals which
are loaded in default and no suppression modes. So, if you
wish to change loaded control sequence or pedestal values for these modes
you must copy needed files in files with predefined names!
You can load any files only if the user defined mode was selected
in Readout configuration window! It may be useful at a tuning stage.
-
CTL file opens a file browser to select a control sequence file
for the load.
-
PED file opens a file browser to select a pedestal file.
-
THR file opens a file browser to select a threshold file.
-
CSR bits rounded buttons set ON or OFF corresponding bits in CSR
register, see MSGC electronics manual.
Important! At the moment you can open properly files which are placed
in a dedicated directory on VME host: ~run/param/RO/MSGC.
Content
Trigger selection
This window allows one to select a trigger file to be loaded. When the
file selector is opened the default trigger file (containing the copy of
last selected trigger file) is highlighted.
|
-
Rescan button serves to re-read the directory.
-
Cancel button lefts the default trigger file unchanged and
returns to the previous window.
-
Ready button copies selected file in the default trg.lst
one and returns to the Set run parameters
window.
|
The first line of each trigger file is used to identify a trigger type.
If pedestal word is met in the line but selected suppression is
default
or user defined - you will get a warning window.
Content
Run title
It is a last window opened when you pushed OK button in the Set
run parameters window. It provides additional information for a run
header event which is used in off-line analysis.
|
-
Target - to choice a target from a predefined list.
-
Proton flux input field for a PS beam intensity.
-
Magnet voltage - a value for the spectrometric magnet.
-
Trigger field - a brief description extracted from the trigger file.
-
Comment - optional input multi-line field, for additional information
concerning the run. Do not write too long comment: it will be difficult
to analyse it in off-line data handling.
-
OK button starts run.
-
CANCEL button returns to Set run parameters
window. Everything you did before in Set run parameters window is
stored.
|
Be careful!
-
You cannot start run until any field name is a red color(the field is not
updated).
-
Changes made in the window do not affect on the real parameters installed
by other instruments and serves only to include these data in the run header
event.
-
The loading of readout and trigger electronics parameters requires few
minutes, so be patient.
Content
Slow control button
This window is opened by Slow ctrl button in main Run
control panel.
|
-
Alarms button opens next level window to set a DAQ reaction on a
predefined diagnostic messages.
|
Content
Alarms
There are two kinds of predefined diagnostic messages:
-
warning serves only to inform one that something goes wrong, but
data are recorded in the data file and distributed to monitoring programs.
-
alarm - the data of corresponding burst are not recorded in the
file, but still distributed for monitoring programs to provide possibility
of analysis of met problems.
The messages may be generated on hardware and software levels. Both of
them may be treated as warning or alarm ones. This window
allows one to allow the data recording in case of specified alarms.
|
-
Check button highlighted means that in case of alarm detected the
burst data will not be recorded, grey coloured - the recording is
allowed in case of this alarm.
-
Accept stores a current settings and returns to main Run
control panel.
-
Cancel changes nothing and returns to main Run
control panel.
|
Please, ask experts if you wish add a hardware or software alarm.
Content
Configuration
and parameter files
These section is not necessary for the reading by most of shift personal
as it contains details useful in very rare cases.
Structures of these files was fixed at the beginning of the DAQ development.
Since that time many things were changed and now not all descriptions look
very well motivated and supported. For example, it was supposed that a
GUI for front-end and trigger electronics will be developed, but it is
not done yet.
Configuration
file for read-out electronics
The file contains a description of read-out electronics: subdetectors,
module position, to which subdetector and read-out branch the module belongs
and so on. The structure of the file is shown below:
Type Readout
Detector
1 description
Detector 2 description
.....
Detector N description
Type Front-end
Unit 1 description
Unit 2 description
.....
Unit N description
Type Service
Here keywords are shown by bold font and arguments by italic one, the
normal font displays strings which are described below.
Type string
The Type keyword starts a section of electronics description.
There are three possible arguments for the string:
-
Readout section contains a description of subdetectors,
VME buffer memories and modules which produce data to be read out over
FERA bus. The RC_gui works mainly with this section.
-
Front-end section foreseen for front-end electronics
-
Service section foreseen for auxiliary modules.
Really, the last two section contains everything that is not in Read-out
one.
Detector description
The structure of a subdetector description looks like:
Detector det_name
Memory
description
Unit
description
Unit description
......
Memory description
Unit description
Unit description
......
There are predefined subdetector names.
You cannot add a new subdetector description in configuration file without
corresponding change of software (DT, RC_gui and other).
The keyword Detector starts the section containing description
of all subdetector electronics modules to be read-out and their data are
placed in corresponding data block in the event.
Memory description
The keyword Memory starts a line which contains information to identify
a VME buffer memory modules and
allows one to determine which subdetctor module data are stored in
it. Electronics and, hence, the data and Memory line formats are slightly
different for MSGC, DC and FERA branches.
-
Memory MSGC_mem base_address
number ,
where
-
MSGC_mem - identificator of micro-strip gas chamber memory module,
-
base_address - base address of module on VME bus,
-
number - now it is a dummy parameter.
-
Memory DC_mem base_address
evf number_1 number_2 ,
where
-
DC_mem - identificator of drift chamber memory module,
-
base_address - base address of module on VME bus,
-
evf - identificator of event delimiter, now only evf must
be here.
-
number_1 - type of event delimiter, now it is dummy parameter.
-
number_2 - how many times the memory must be read-out, now
it is dummy parameter.
-
Memory hardware_type base_address
event_delimiter number_1 number_2
where:
-
Memory - keyword,
-
hardware_type - hardware type of VME buffer memory, for example,
LeCroy1190 for FERA branch,
-
base_address - base address of memory module on VME bus,
-
event_delimiter - symbolic name of electronics module which data
must be available in the beginning of each event. We use now LeCroy 2366
register/scaler modules. It allows event building procedure to identify
a beginning of subevent in each FERA branch.
-
number_1 - type of event delimiter, now it is dummy parameter.
-
number_2 - how many times the memory must be read-out, now
it is dummy parameter.
Few Memory lines may present in a subdetector section, as electronics
modules of one subdetector may be placed in different FERA branches and
their data than are stored in different VME memory modules.
Content
Unit description
The most of electronics module descriptions consist of one line:
Unit Name HW_type Computer Branch Crate
Slot N_ref Suppr State
where
-
Unit - keyword,
-
Name - symbolic name of module used for a module identification,
-
HW_type - hardware type of module, used to execute proper CAMAC
operations,
-
Computer - a computer which control the module, now it is always
c-eposly22
-
Branch - CAMAC branch in which the module installed,
-
Crate - CAMAC crate,
-
Slot - CAMAC slot,
-
N_ref - number of additional lines in the module description,
commonly it is 0,
-
Suppr - suppression mode: DEF_SUP, NO_SUP, USD_SUP,
-
State - is module ON or OFF for read-out,
Additional lines looks like:
Reference R_name
n1 n2
where
-
R_name - name of data, used for reference
-
n1, n2 - two numbers used to determine subaddresses, serial
number of data word and so on. Depends on type of module.
And used only for modules which data are not copied directly in the event
but placed in Event Data Block or somewhere else. Really it is used for
only for 3 variables: time of event in the burst, live-time measurement,
and for gamma monitor count.
Content
Parameter file for
read-out electronics
The file contains parameters to be set at start of run and for performing
of automatic calibrations.
The structure of file looks like:
Type Readout
Unit line
Standard
parameters
end
Calibration 1
parameters
end
.....
Calibration N
parameters
end
End
....
Unit
line
.....
End
END
Type Front-end
....
END
Type Service
....
END
Content
Auxiliary modules
There are modules which are used to provide a work of readout electronics
and which parameters depends on states of subdetector modules, suppression
mode, and so on. Hence, the RC_gui itself updates parameters of
these modules. In very rare cases it may be necessary to change something
concerning these modules by help of an editor. The last is allowed for
experts only!
Read-out control module
The module has symbolic name RO_ctrl and serves to mask signals
from the MSGC, FERA and DC branches to provide a correct synchronization
of read-out and trigger electronics independently from which branches are
participating in data taking. One may need to update a description of module
in few cases:
-
the module position was changed, or
-
the base address of any VME buffer memory or MSGC module was changed, or
-
the cabling for this module was changed.
As for any other read-out modules the module position is described
in file std.cfg (and in any other one with cfg extension).
So, if the module was moved in other CAMAC position, you must edit these
files (and trigger ones). See above.
At present a LeCroy 2365 matrix is used. The module is used also for
other purposes in a trigger control. So, the module parameters are updated
independently for read-out and trigger parts. An example of module description
in a parameter file is shown below.
Unit RO_ctrl LeCroy2365 - a standard line started a module description, see above.
Standard - starts description of standard parameters
Owner Readout 2 - list of outputs of the module for read-out control
Owner Trigger 0 1 3 4 5 6 7 - determines which outputs of the module are used for trigger control
Section Readout - starts description of read-out parameters of the module
INPUTS - starts the description of module inputs
3 Mem_0xC0000 - input number and name of VME memory, connected to the input
4 Mem_0xFF000001
5 Mem_0x140000
6 Mem_0x180000
7 Mem_0x0
8 Mem_0x40000
9 Mem_0x80000
10 Mem_0xCC0000
11 Mem_0xDC0000
12 Mem_0xEC0000
13 Mem_0xFC0000
OUTPUTS - starts the description of module outputs
2 BUSY AND 3ff8 0 - output number, name, performed function, two masks for inputs
end - end of standard set of parameters
end - end of module description
Two lines started from Owner keywords serves to escape interference
between readout and trigger software. Be careful, in a trigger software
there is no checks of this kind.
You may change by an text editor Owner, INPUTS and
partially OUTPUTS lines. The mask
words are formed by RC_gui automatically in a correspondence with
which subdetectors are switched on and off.
Content
Mode output register
The symbolic name of module is Mode_reg. It serves as a post-box
in order to trace the mode of suppression and loaded set of parameters
in each burst. An example of its parameter description is shown below.
At present a CES 1320 output register is used. Each time as a slow control
function re-loaded electronics, the contents of register will be changed.
DT
read out the register data and puts them in each event.
Unit Mode_reg CES1320
Standard
0 0
end
Calibration 1
0 0x5
end
Calibration 2
0 0x9
end
Calibration 3
0 0xd
end
End
First digit in parameter line determines is the register output signal
a potential or pulse one. The second hexadecimal value shows a suppression
mode in lowest 2 bits:
-
0 - default suppression
-
1 - user defined
-
2 - no suppression
-
3 - unknown, problems with register
and number of set of parameters in older bits:
-
0 - standard set,
-
1 - Calibration 1,
-
2 - Calibration 2, and so on.
So, 0x5 means that Calibration 1 and user defined mode are
set in electronics.
IMPORTANT! Parameters are set by RC_gui and you must not change it
by hands!
Content
CAMAC bus displays
BORER 1802 CAMAC bus displays are installed in each crate and serve to
check CAMAC bus during data taking. The symbolic names of these modules
are BusDisp_1,... BusDisp_11. Parameters of these modules
are dummy ones. You do not need change them.
Content
APPENDIX
Below you will find information which may help you to navigate through
the document and find out what you need.
Content
Subdetector names
-
MSGC0, MSGC1, MSGC2, MSGC3 - micro-strip gas chambers
-
SciFi - scintillation fibre detector
-
dEdX - forward ionization hodoscope
-
DC0, DC1, DC2 - drift chamber branches
-
VH - vertical scintillation hodoscopes
-
HH - horizontal scintillation hodoscopes
-
Cherenkov - Cherenov detectors
-
PreSh - preshower detector
-
Muon - scintillation detectors for muon identification
-
Monitors - monitor detectors
-
Dummy - for any modules which must be read-out and are
not included in other subdetectors
Content
Symbolic names
of read-out modules
BusDisp - CAMAC bus displays
Ch_adc1, Ch_adc2 - ADCs for Cherenkov detectors
DC_ctl - drift chamber control unit
DC_tr1, DC_tr2 - drift chamber track finders
eob_sc1, eob_sc2 - scalers for subdetector and trigger rates
HH_adc1, HH_adc2 - ADCs for time measurements
for horizontal hodoscopes
IH_adc1, IH_adc2 - ADCs for the forward
ionization hodoscope
IH_tdc1, ..., IH_tdc3 - TDCs for the forward
ionization hodoscope
Mode_reg - register indicates suppression
mode and set of parameters
MSGC0_csr, MSGC1_csr, MSGC2_csr, MSGC3_csr - MSGC's dummy modules
Mu_reg1, Mu_reg2 - subevent delimiters,
contain counting rates
Mu_tdc1, Mu_tdc2 - TDCs for muon detector
PrS_adc1, PrS_adc2 - ADCs for preshower
detectors
PrS_tdc1 - TDC for preshower
RO_ctrl - module controls the
read-out of FERA, MSGC and DC branches
SF_adc1, SF_adc2 - ADCs for last dynodes
of Scintillation Fibre detector
SF_reg1, SF_reg2 - subevent delimiters for
SciFi detector, contains live-time, event time, trigger number also
SF_tdc1, SF_tdc2, ..., SF_tdc17 -
time to digit converters for Scintillation Fibre detector
TRGB_tdc - trigger bit pattern unit
VH_adc1, VH_adc1, VH_adc2 - ADCs for
time measurements for vertical hodoscopes