For details about the definition of spectra and conditions, for spectrum manipulation options and data I/O to other programs
please refer to the
manual. In the following you find some pre-defined conditions (as examples) and spectra as part
of the “startup.ccf” that will allow you to view the most important coordinates. For example, you will immediately be able to
see a position spectrum. You may later edit the “startup.ccf” and all sub-scripts to adjust them to your needs, e.g. setting the
right condition gates on the time sum peak(s), omitting spectra that you do not need, adjust parameters (for shifting or rotating
the spectra, calibrating position and time), changing or appending spectrum definitions. For the Hexanode an extra software
package is available to optimize its function. Please contact
RoentDek on the availability of specific software packages for
your application.
The following condition and spectra definition commands are recommended for first time users. Those definitions disabled by
the “;” may also be of use and can be activated by removing the “;” in front of each command line:
condition ConsistencyIndicator,14.5,15.5,four; true if x1,x2,y1 and y2 signals were registered
condition ConsistencyIndicator,62.5,63.5,six; true if x1,x2,y1,y2 and z1,z2 signals were registered
condition four,or,six,clean_hit
Note that for the Hexanode it is recommended to rename the condition six by clean_hit here and comment out 2 lines:
;condition ConsistencyIndicator,14.5,15.5,four; true if x1,x2,y1 and y2 signals were registered
condition ConsistencyIndicator,62.5,63.5,clean_hit; true if x1,x2,y1,y2 and z1,z2 signals were registered
;condition four,or,six,clean_hit
condition sumx,1,10000,sumx
condition sumy,1,10000,sumy
;condition sumy,1,10000,sumw
condition sumx,and,sumy,sumxy
This defines a more specific filtering for “clean” events. The boundary parameters in the condition for sumx and sumy
conditions should be narrowed according to the actual time peak widths/positions.
new
;new hardware
This command is defining the type of session but also validates/checks many parameters and coordinate commands on
consistency.
define1 0,32,1,T1Ch01n,,none,always,T1Ch01n
define1 0,32,1,T1Ch02n,,none,always,T1Ch02n
define1 0,32,1,T1Ch03n,,none,always,T1Ch03n
define1 0,32,1,T1Ch04n,,none,always,T1Ch04n
define1 0,32,1,T1Ch05n,,none,always,T1Ch05n
define1 0,32,1,T1Ch06n,,none,always,T1Ch06n
define1 0,32,1,T1Ch07n,,none,always,T1Ch07n
define1 0,32,1,T1Ch08n,,none,always,T1Ch08n
define1 -2,66,1,ConsistencyIndicator,,none,always,ConsistencyIndicator
define2 0.,9.,1.,n_matrix_x,,0.,8.,1.,n_matrix_y,,none,always,hit statistics
These spectra display the number of hits per TDC channels in various representations.
define1 -12000,12000,1,T1Ch01S01,T1Ch01S01 (x1 raw),none,always,T1Ch01S01,,true
define1 -12000,12000,1,T1Ch02S01,T1Ch02S01 (x2 raw),none,always,T1Ch02S01,,true
define1 -12000,12000,1,T1Ch03S01,T1Ch03S01 (y1 raw),none,always,T1Ch03S01,,true
define1 -12000,12000,1,T1Ch04S01,T1Ch04S01 (y2 raw),none,always,T1Ch04S01,,true
define1 -12000,12000,1,T1Ch05S01,T1Ch05S01 (z1 raw),none,always,T1Ch05S01,,true
define1 -12000,12000,1,T1Ch06S01,T1Ch06S01 (z2 raw),none,always,T1Ch06S01,,true
define1 -12000,12000,1,T1Ch07S01,T1Ch07S01 (TOF raw),none,always,T1Ch07S01,,true
;define1 -12000,12000,1,T1Ch08S01,T1Ch08S01 (Trigger),none,always,T1Ch08S01,,true
These spectra show the “raw” (uncalibrated) values of the first hits in the TDC channels
;define1 0,10000,1,AbsoluteEventTime,AbsoluteEventTime [s],none,always,Time since Start,,true
define1 0,0.005,0.00001,DeltaEventTime,DeltaEventTime [s],none,always,Time between Events,,true
define1 0,10000000,1000,EventCounter,,none,always,EventCounter
define1 0,100000,10,RealTriggerRate,,none,always,RealTriggerRate,true
;define2 0,100000,100,AbsoluteEventTime,,0,100000,100,RealTriggerRate,,none,always,Rate (time)
;define2 0,1000000,1000,EventCounter,,0,100000,100,RealTriggerRate,,none,always,Rate (eventnumber)
Page 66 of 83 MCP Delay Line Detector Manual (11.0.1304.1)
To Next Page
Loading...