Parameter 1027 channel number for x2
Parameter 1028 channel number for y1
Parameter 1029 channel number for y2
Parameter 1030 channel number for z1 (ignored if parameter 1002 = 0)
Parameter 1031 channel number for z2 (ignored if parameter 1002 = 0)
Parameter 1032 channel number for TOF (-1 if not used)
Parameter 1035 Offset for PosX
Parameter 1036 Offset for PosY
These two parameters are offset (additive) constants for shifting the detector image in the
X/Y plane. Note, that in case of the Hexanode these values define the offsets for the
calculated x and y and not for the raw u and v values.
Parameter 1037 Offset for third anode layer (added to w, only for Hexanode)
Parameter 1038 Offset for Sum/Diff coordinate calculations.
This offset value is an additive constant to all time Sum/Diff coordinates
Parameter 1039 Anti-Moire (0 = no, 1 = yes)
Parameter 1040 Reset EventCounter (1: reset after "new" command, 0: no reset)
Parameter 1041 Integration time in seconds for RealTriggerRate coordinate
Parameter 1060 Condition flag: value will appear as value in coordinate Condition1
The following DAn coordinates are by definition only the additional coordinates that are computed from the (raw) DAq
coordinates retrieved from the hardware or from a previously accumulated event file (not part of a list mode file). Here, only
one set of delay-line coordinates for one of the hits (default: first hit, see parameter 1005) is selected and position and time
coordinates are calculated. If you have changed parameter 2, 32 or 33 from their default value (first hit only) or if you sort a
list-mode file acquired with a non-default parameter settings you need to adjust the (pointer) parameters 1005 and 1006. It is
such possible to apply the position and time calculations to the next hits if such are (or have been) acquired. The DAn module
will read the values of the status registers and the value in the 4 (Hexanode: 6) raw position coordinates (and optional TOF)
defined by parameter 1005 (default: first hits) and calculate the desired position and time information. Note that even for the
use of a DLD (4 delay-line signals only), the coordinates for two additional delay-line signals (as from a Hexanode) are defined
but set to 0. A set of DAn coordinates is created by using the defined set of DAq coordinates:
Coordinate AbsoluteEventTime defines the absolute event time and
Coordinate DeltaEventTime the time between one event and the next
Coordinate EventCounter event number since start or last event number reset
Coordinate True internal coordinate
Coordinate False internal coordinate
Coordinate ConsistencyIndicator The value of this coordinate is: ∑ u ⋅2
i-1
, i is the TDC channel,
u =1, if at least one hit in the TDC channel i was registered,
otherwise 0. If each TDC-channel for the selected hit number
has received at least one hit of the value is 15 for a DLD and
63 for a Hexanode. This assumes that the first TDC channels
are used for the delay-line signals.
Coordinate PLLStatusLocked internal coordinate for HM1 (see manual), must always be
defined
Coordinate RealTriggerRate calculates the trigger (count) rate (please see parameter 1041)
Coordinate Condition1 the value of this coordinate is set by a condition command
Coordinate n1,n2,n3,n4,n5,n6,n7,n8 number of hits in the TDC channels 1-8 (not higher than
parameter 33)
Coordinate x1,x2 Values in the TDC channels 1-6, “position calibrated” in mm.
Coordinate y1,y2 If parameter 1010 to 1012 are set to 1 these values correspond
to time calibrated
Coordinate z1,z2 values (in ns).
Coordinate TOF Values in the TOF-TDC time calibrated in ns (please see
parameter 1032)
Coordinate raw_x,raw_y,raw_w difference of TDC channel values 1&2, 3&4, 5&6
(uncalibrated)
Coordinate raw_sumx,raw_sumy,raw_sumw sum of TDC channel values 1&2, 3&4, 5&6 (uncalibrated)
Coordinate raw_sumxyw sum of TDC channel values 1 to 6 (uncalibrated)
Page 64 of 83 MCP Delay Line Detector Manual (11.0.1304.1)
To Next Page
Loading...