| Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
s800_daq_tools [2017/06/16 19:03]
pereira [Running in Slave mode with multilogger] |
s800_daq_tools [2020/03/04 17:57]
pereira [Readout GUI] |
| |
| ==== 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 with three tags labeled "main", "SSHPipe@localhost:0", and "SSHPipe@localhost:1". The first one provides general information about the ReadoutGUI. The second and third tabs provide information about the data sources (from the CCUSB and VMUSB controllers). **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 session connected to spdaq19 by typing: ''. /usr/opt/nscldaq/xxxx/daqsetup.bash'', where ''xxxx'' is the nscldaq version (xxx = 11.0-020, on Feb 2016). | 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/s800daq** and typing ''godaq''. The Readout GUI window will appear with three tags labeled "main", "SSHPipe@localhost:0", and "SSHPipe@localhost:1". The first one provides general information about the ReadoutGUI. The second and third tabs provide information about the data sources (from the CCUSB and VMUSB controllers). |
| |
| Before beginning taking data is necessary to initialize the system. This is done by clicking ''Start'' in the ReadoutGUI. You can inspect the status of each source during their initialization by clicking in one of the tabs "SSHPipe@localhost:0" or "SSHPipe@localhost:1". You will see a series of messages about the different initialization steps. The last message should be "Done". During the initialization process, a fourth tab labeled "ActionFilter" may appear with information from the S800 filter. Sometimes, you may see a warning message about an old "still-running" S800 filter session being killed. That's ok. | Before beginning taking data is necessary to initialize the system. This is done by clicking ''Start'' in the ReadoutGUI. You can inspect the status of each source during their initialization by clicking in one of the tabs "SSHPipe@localhost:0" or "SSHPipe@localhost:1". You will see a series of messages about the different initialization steps. The last message should be "Done". During the initialization process, a fourth tab labeled "ActionFilter" may appear with information from the S800 filter. Sometimes, you may see a warning message about an old "still-running" S800 filter session being killed. That's ok. |
| |
| 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 completely initializing before opening those GUIs. | 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 completely initializing before opening those GUIs. |
| | |
| | Before beginning a run, you have to make sure that the ULM trigger module is properly configured. This can be done by clicking the button [[#Trigger GUI|Launch ULM GUI]] in the ReadoutGUI 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. (Note that the tab "ActionFilter" may appear if it didn't show up before, when you clicked ''Start''.) 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. (Note that the tab "ActionFilter" may appear if it didn't show up before, when you clicked ''Start''.) Data can be recorded on disk by checking out the box ''Record''. To end a data run, simply click ''End''. |
| By default, when running in Slave mode, data are recorded in the stagearea of the Master DAQ (experiment account). It is however possible to record simultaneously data from the S800 into the S800 stagearea, using the ''multilogger'' option (see ReadoutGUI figure above). The S800 ReadougGUI offers the possibility to record data from four different S800 ring-buffers: rawccusb, rawvmusb, s800built, and s800filter. The later is the most important since data from this ring buffer can be immediately processed by the S800 SpecTcl. | By default, when running in Slave mode, data are recorded in the stagearea of the Master DAQ (experiment account). It is however possible to record simultaneously data from the S800 into the S800 stagearea, using the ''multilogger'' option (see ReadoutGUI figure above). The S800 ReadougGUI offers the possibility to record data from four different S800 ring-buffers: rawccusb, rawvmusb, s800built, and s800filter. The later is the most important since data from this ring buffer can be immediately processed by the S800 SpecTcl. |
| |
| Before running an experiment with a Master system (e.g. GRETINA), it is recommendable to run the S800 DAQ in Slave mode with the s800filter multilogger enabled. This can be done following the steps: | When running XDT for an experiment with a Master DAQ (e.g. GRETINA), it is recommendable to run the S800 DAQ in Slave mode with the s800filter multilogger enabled. This can be done following the steps: |
| |
| * Click to the tab ''multilogger'' in the **ReadoutGUI** | * Click to the tab ''multilogger'' in the **ReadoutGUI** |
| * Select the option "always record" | * Select the option "always record" |
| |
| * Click again on the tab ''multilogger'' and select "enable loggers". A window will pop out with a list of ring-buffers that can be muti-logged | * Click again on the tab ''multilogger'' and select "enable loggers". A window will pop out with a list of ring-buffers that can be muti-logged {{:wiki:multilogger.png|Multilogger window}} |
| |
| * Check out the ring-buffer ''tcp://spdaq50/s800filter'' to enable recording data from **s800filter** {{:wiki:multilogger.png|Multilogger window}} | * Check out s800filter to enable recording data from this ring buffer |
| |
| * After this, S800 data from every run recorded by the experimenters, will also be recorded in the S800 stagearea. | * After this, S800 data from every run recorded by the experimenters, will also be recorded in the S800 stagearea. |
| |
| | * After finishing XDT, it is better to disable the s800filter ring-buffer in the multilogger menu so the S800 stagearea doesn't record all data from the experiment. |
| |
| |
| |
| ===== Troubleshooting ===== | ===== Troubleshooting ===== |
| There are several common reasons why the S800 DAQ may fails to start. The list below describes what to do to fix these problems. | There are several common reasons why the S800 DAQ may fail. The list below describes what to do to fix some of these problems. |
| * [[#Old processes still running]] | * [[#Old processes still running|Error message "Socket ID already in use"]] |
| * [[#No data sources defined]] | * [[#No data sources defined|Error message "No data sources are running so a run cannot be started"]] |
| * [[#CCUSB and/or VMUSB claimed by existing programs]] | * [[#CCUSB and/or VMUSB claimed by existing programs]] |
| * [[#Manual rebooting]] | * [[#Manual rebooting]] |
| |
| ==== Old processes still running ==== | ==== Old processes still running ==== |
| Sometimes, particularly if the previous S800 DAQ session ended in an uncontrolled way, there may be old processes running (CCUSB and/or VMUSB and/or S800 event builder) that will prevent Readout GUI to begin a run. Whenever this happens (typically after clicking ''Begin'' in Readout GUI), the system sends an error message complaining about one of these processes still running. If you find yourself in this situation try: | Sometimes, particularly if the S800 DAQ session ended in an uncontrolled way (e.g. you tried to "kill" it), there may be old processes running (CCUSB and/or VMUSB and/or S800 event builder) that will prevent Readout GUI to begin a run. Whenever this happens (typically after clicking ''Begin'' in Readout GUI), the system sends an error message complaining about one of these processes still running (for instance "Socket ID already in use"). If you find yourself in this situation try: |
| - Exit your Readout GUI properly | - Exit your Readout GUI |
| - On a Linux session, connect to spdaq19 by typing ''ssh -Y s800@spdaq19'' (the S800 password can be found in the S800 binder that is kept in the data-U1 logbook cabinet) | - On a Linux session, connect to the S800 spdaq by typing ''ssh -Y s800@spdaqXX'' (Contact the Device Physicist to get the spdaq number XX and S800 password) |
| - Type ''ps aux | grep Readout'' to ensure that Readout is indeed not running | - Type ''ps aux | grep Readout'' to ensure that Readout is indeed not running. If "Readout" is still running, use ''kill -9 PID'', where PID identifies the Readout process ID |
| - Type ''/usr/opt/nscldaq/xxxx/bin/ringbuffer status'', where xxxx is the daq version, e.g. 11.0-020 | - Type ''/usr/opt/nscldaq/xxxx/bin/ringbuffer status'', where xxxx is the daq version, e.g. 11.0-020 |
| - You will see a list of ringbuffers with information about their status (see figure below). Check that the producer value of each ringbuffer (see column ''producer'') is **-1**. (Don't worry about the ringbuffer **s800filter**, which is automatically killed when starting ReadoutGUI) | - You will see a list of ringbuffers with information about their status (see figure below). Check that the producer value of each ringbuffer (see column ''producer'') is **-1**. (Don't worry about the ringbuffer **s800filter**, which is automatically killed when starting ReadoutGUI) |
| ==== CCUSB and/or VMUSB claimed by existing programs ==== | ==== CCUSB and/or VMUSB claimed by existing programs ==== |
| One of the most common reasons why the S800 DAQ fails to start is because the CCUSB and/or VMUSB are claimed by existing programs. This is shown by the error messages displayed by the system. If you find yourself in this situation try the following: | One of the most common reasons why the S800 DAQ fails to start is because the CCUSB and/or VMUSB are claimed by existing programs. This is shown by the error messages displayed by the system. If you find yourself in this situation try the following: |
| - Log on to S800 spdaq (spdaq19 as of October 2015) | - Log on to S800 spdaq (spdaqXX as of October 2015) |
| - Type ''ps aux | grep Readout'' | - Type ''ps aux | grep Readout'' |
| - Use ''kill -9 PID'', where PID identifies any CCUSBReadout or VMUSBReadout processes that show up | - Use ''kill -9 PID'', where PID identifies any CCUSBReadout or VMUSBReadout processes that show up |
