| 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 [2016/02/29 11:49]
pereira [Mesytec CFD GUI] |
| * [[#Run Control Window]] | * [[#Run Control Window]] |
| * [[#EventBuilder Window]] | * [[#EventBuilder Window]] |
| | * [[#Mesytec CFD GUI]] |
| * [[#Delay Window]] | * [[#Delay Window]] |
| * [[#Trigger GUI]] | * [[#Trigger GUI]] |
| |
| |
| ==== Run Control Window ==== | ==== Readout GUI ==== |
| The Run Control GUI is invoked by either clicking the icon **RunControl** in the desktop of [[Software#u6pc5 (data U6)|u6pc5]] or by navigating in a Linux terminal to the directory **/user/s800/operations/daq/usb/TclXXUSB** and typing ''/usr/bin/wish RunControl.tcl''. The Run Control window and the EventBuilder window will appear. The image shows the typical configuration for stand-alone mode. | The S800 Readout GUI is invoked by either clicking the icon **S800 DAQ** in the desktop of [[Software#u6pc5 (data U6)|u6pc5]] or by navigating in a Linux terminal to the directory **/user/s800/converged_daq** and typing ''godaq''. The Readout GUI window will appear. |
| |
| Before beginning taking data is necessary to initialize the VME and CAMAC USB controllers. This is done by selecting the crate (either VM0079 for VME or CM0105 for CAMAC) and selecting the corresponding initialization file by clicking in the **Browsing** button. The initialization files are ''/user/s800/operations/daq/usb/Scripts/VM0079Init.tcl'' for VME and ''/user/s800/operations/daq/usb/Scripts/CM0105Init.tcl'' for CAMAC. Once the files are selected, the modules can be initialized by clicking in the button *Init*. After initializing the VME crate, the [[s800 daq tools#delay window|TDC delay window]] should pop out. Likewise, the [[s800 daq tools##Trigger GUI|Trigger GUI]] will appear after initializing the CAMAC crate. It is very important that both Save and Broadcast are checked. Failure to do so will result in settings files not being saved, data from the USB controllers not being broadcast to the eventbuilder, and the S800 evt files not being saved. | **IMPORTANT NOTE:** When running Readout GUI, make sure that the environment variables needed by the system are properly defined. This can be done from a Linux terminal by typing: ''. /usr/opt/nscldaq/xxxx/daqsetup.bash'', where ''xxxx'' is the nscldaq version (xxx = 11.0-020, on Feb 2016). |
| |
| | Before beginning taking data is necessary to initialize the system. This is done by clicking ''Start'' in the ReadoutGUI. After initializing the contollers, the ReadoutGUI window will show the ''Begin'' button active. In addition, three additional buttons should appear at the end of the window. They can be used to start the GUI associated with the [[#Mesytec CFD GUI|MCFD]], [[#Delay Window|Delay XLM]], and [[#Trigger GUI|Trigger ULM]] modules. Make sure that the system is fully initializing before opening those GUIs. |
| |
| {{:wiki:482px-Runcontrol.png|Run Control Window}} | The figure below shows the Readout GUI window after initializing the system. After clicking ''Begin'', the "Event Builder" window will pop out, displaying information about the Readout session. Data can be recorded on disk by checking out the box ''Record''. To end a data run, simply click ''End''. |
| |
| |
| |
| ==== EventBuilder Window ==== | {{:wiki:readoutgui2.png|Readout GUI Window}} |
| |
| {{:wiki:Eventbuilder.png|EventBuilder Window}} | |
| |
| The EventBuilder window will appear as part of starting the [[s800 daq tools#run control window|Run Control]]. This window will communicate statistics such as number of buffers read and number of events broadcast, and will also show error messages, should they occur. | |
| |
| | |
| | ==== Mesytec CFD GUI ==== |
| | The S800 electronics includes a Mesytec CFD (MCFD), used to "filter" the detector signals going to the Scaler and Mesytec TDC. The configuration parameters of the CFD (thresholds, delays, fraction, etc.) can be remotely adjusted via a MCFD GUI developed by the NSCL DAQ group. During tuning of the S800, one typically needs to adjust thresholds only. |
| | |
| | The MCFD GUI is invoked by either clicking the icon **MCFD GUI** in the desktop of [[Software#u6pc5 (data U6)|u6pc5]] or by navigating in a Linux terminal and typing ''$DAQBIN/MCFDControl16 --protocol usb --serialfile /dev/ttyUSB0''. The environment variable DAQBIN is defined by sourcing the **daqsetup.bash** file in directory **/usr/opt/nscldaq/xxxx/bin**, where xxxx is the nscldaq version number (11.0-015 on Oct 26, 2015). |
| | |
| | |
| | {{:wiki:mcfdgui.png|MCFD GUI}} |
| | |
| | |
| | * To load the default CFD configuration go to **Load Setting**, select file **MCFD16.tcl** in directory **/user/operations/daq/usb/Config**, and click **Load** |
| | * Alternatively, it is possible to load the configuration directly from the module by clicking **Update from Device**. However, the names of the channels will not be displayed. |
| | * By default, the CFD parameters can be adjusted individually for each of the 16 channels. It is also possible use the module in a "common" mode to set the same CFD parameters to all channels. Just check **common** |
| | * After modifying any of the CFD parameters, click **Commit to Device** |
| | * The MCFD module includes the possibility to send a periodic pulsing signal to all the channels. Two frequencies can be selected: 1.22 KHz, and 2.5 MHz |
| | |
| | |
| |
| ==== Delay Window ==== | ==== Delay Window ==== |
| | {{:wiki:delay-window.png|Delay GUI}} |
| | |
| | |
| | |
| |
| {{:wiki:Delay-Window.png|Delay Window}} | |
| |
| This window appears when the "Init" button is pressed on the VME crate controller tab as part of the initial setup of the [[s800 daq tools#run control window|S800 USB daq]]. It can also be accessed by pressing the "Show GUIs" button. The delay module allows software configurable delays to be applied to each of the signals indicated in the Channel column, which then form the TDC stops. It is configurable to enable delays to be set with beam on target, as the needed delay may change depending on experimental conditions. | This window appears when the "Init" button is pressed on the VME crate controller tab as part of the initial setup of the [[s800 daq tools#run control window|S800 USB daq]]. It can also be accessed by pressing the "Show GUIs" button. The delay module allows software configurable delays to be applied to each of the signals indicated in the Channel column, which then form the TDC stops. It is configurable to enable delays to be set with beam on target, as the needed delay may change depending on experimental conditions. |
| * 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 | |
| |
| |
| |
| ==== 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]]. |
