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 [2016/02/29 11:45]
pereira [Readout GUI]
s800_daq_tools [2016/02/29 11:51]
pereira [S800 DAQ status tool]
Line 23: Line 23:
  
 ==== Readout GUI ==== ==== Readout GUI ====
-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.+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. **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).
  
-**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-020on Feb 2016).+Before beginning taking data is necessary to initialize the system. This is done by clicking ''Start'' in the ReadoutGUI. After initializing the contollersthe ReadoutGUI window will show the ''Begin'' button active. In addition, three additional buttons should appear at the end of the windowThey 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.
  
-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 XLM, and Trigger ULM modules. Make sure that the system is fully initializing before opening those GUIs. +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''
- +
-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 clock ''End''+
  
  
Line 44: Line 42:
  
  
-{{:wiki:mcfd16gui.jpg|MCFD GUI}}+{{: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**   * 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 lead the configuration directly from the module by clicking **Update from Device**+   * 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**   * 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**   * After modifying any of the CFD parameters, click **Commit to Device**
Line 96: Line 94:
 ==== Troubleshooting ==== ==== Troubleshooting ====
 In the rare case that the RunControl GUI gets "frozen", it is possible to reboot the whole system manually. This operation requires to turn off the VME and CAMAC crates, and the spdaq computer, all them located in the rack seating near the FP box in the S3 vault. Then, the system must be turned back on in the following order. First, CAMAC crate, second VME crate, and third spdaq. In the rare case that the RunControl GUI gets "frozen", it is possible to reboot the whole system manually. This operation requires to turn off the VME and CAMAC crates, and the spdaq computer, all them located in the rack seating near the FP box in the S3 vault. Then, the system must be turned back on in the following order. First, CAMAC crate, second VME crate, and third spdaq.
-===== S800 DAQ status tool ===== 
-In order to remotely monitor the status of the S800 DAQ, a tool has been created which can show statistics and current information about the present running instances of the Readout GUI and eventbuilder programs. This is accessed by the following: 
- 
-1. On spdaq48 do: 
- 
-**/user/s800/operations/daq/usb/s800status/comms** 
- 
-which will open the status GUI. 
- 
-There are tabs for connections to the Readout GUI, the eventbuilder and a controls tab. 
- 
  
 ==== Readout GUI tab ==== ==== Readout GUI tab ====
Line 141: Line 128:
  
 If the eventbuilder is hanging, which is evidenced by non-increasing statistics and no data/triggers, then it is possible that one of these processes has crashed in a manner that holds open the tcp connection to the eventbuilder. The process can be killed, which will return the DAQ to a normal running mode. If the eventbuilder is hanging, which is evidenced by non-increasing statistics and no data/triggers, then it is possible that one of these processes has crashed in a manner that holds open the tcp connection to the eventbuilder. The process can be killed, which will return the DAQ to a normal running mode.
- 
- 
-==== Controls tab ==== 
-This tab allows forced control of the Readout GUI, and is for advanced users only. In the event that the run must be stopped, or the DAQ software exited without access to the Readout GUI itself these buttons may be used to perform these actions. The run MUST be ended before using the Force Exit button, or it is likely that the USB crate controllers will become stuck in DAQ mode and the crates will have to be reset. 
- 
-{{:wiki:controls.png?500|Controls tab}} 
  
  
s800_daq_tools.txt · Last modified: 2023/10/19 17:25 by swartzj