User Tools

Site Tools


s800_daq_tools

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
Next revision Both sides next revision
s800_daq_tools [2015/10/25 16:42]
pereira [Delay Window]
s800_daq_tools [2015/10/26 15:46]
pereira
Line 48: Line 48:
   * There are four "Delay Inspect" channels (routed to the patch panel in data U6) which can be selected using the Delay GUI     * There are four "Delay Inspect" channels (routed to the patch panel in data U6) which can be selected using the Delay GUI  
   * These "Delay Inspect" signals can be compared with any one of the four "Trigger Inspect" channels in order to set proper delays for the TDCs. The "Trigger Inspect" channels can be selected using the [[S800 DAQ tools#Trigger GUI|ULM trigger GUI]]   * These "Delay Inspect" signals can be compared with any one of the four "Trigger Inspect" channels in order to set proper delays for the TDCs. The "Trigger Inspect" channels can be selected using the [[S800 DAQ tools#Trigger GUI|ULM trigger GUI]]
 +  * TDCs of last 4 listed signals (including XF and object scintillators) are bypassed with cable delays and thus their delays cannot be controlled with the GUI. They can be inspected, however using the GUI
 +  * It is possible to bypass the delay of a given channel by checking the "bypass" check box in the GUI
 +  * The TDC delays can only be changed when the run control is stopped; must SAVE settings before starting run control not to overwrite adjustments being made
 +  * The S800 trigger used as reference to calculate the ToF is from E1 up signal
 +  * The signal delays controlled by the GUI (and not by cable delays) are not “pipelined” -- i.e., any new signals that arrive during the delay time of a previous signal are lost and thus deadtime is introduced into the system.  The signals delayed passively by cables are “pipelined” and thus are not subject to deadtime losses
  
- 
-  * Information 
-      * The signal delays controlled by the GUI (and not by cable delays) are not “pipelined” -– i.e., any new signals that arrive during the delay time of a previous signal are lost and thus deadtime is introduced into the system.  The signals delayed passively by cables are “pipelined” and thus are not subject to deadtime losses 
-      * All of the trigger signals are not pipelined and are thus subject to deadtime 
  
  
Line 64: Line 65:
  
 ==== Scaler Display ==== ==== Scaler Display ====
-The GUI used to display scalers rates can be open from the icon **S800 Scalers** in the desktop of [[Software#u6pc5 (data U6)|u6pc5]]. The GUI includes two pages labeled "s800" and "ratios". Page "s800" includes all the scaler channels; page "ratios" displays ratio values calculated between several pairs of channels. In addition, the GUI includes a panel showing the time evolution of the live time calculated from the live-to-raw trigger ratio, and the live-to-raw clock ratio. The figure below shows the page "ratios" from the scaler GUI.+The GUI used to display scalers rates can be open from the icon **S800 Scalers** in the desktop of [[Software#u6pc5 (data U6)|u6pc5]]. Alternatively, open a terminal on u6pc5, and type **./goscalers** from directory **/user/s800/converged_daq/scalers**. 
 + 
 +The GUI includes two pages labeled "s800" and "ratios". Page "s800" includes all the scaler channels; page "ratios" displays ratio values calculated between several pairs of channels. In addition, the GUI includes a panel showing the time evolution of the live time calculated from the live-to-raw trigger ratio, and the live-to-raw clock ratio. The figure below shows the page "ratios" from the scaler GUI.
  
 A list of scaler channels can be found [[Scaler Channel Description|here]]. A list of scaler channels can be found [[Scaler Channel Description|here]].
s800_daq_tools.txt · Last modified: 2023/10/19 17:25 by swartzj