| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
sweeper_daq_tools [2017/07/06 17:41]
pereira [Level-3 Trigger GUI] |
sweeper_daq_tools [2017/07/07 13:01] (current)
pereira [Level-3 Trigger GUI] |
| |
| ==== Level-3 Trigger GUI ==== | ==== Level-3 Trigger GUI ==== |
| The Level-3 trigger GUI gets started by clicking the button ''Launch Level3 Trigger GUI''. It can be used to select the trigger mode: (1) Sweeper standalone (Sweeper data are processed when there is a Sweeper trigger, typically coming from the Thin left-up PMT of the FP scintillator); (2) Sweeper singles (Sweeper, MoNA and LISA data are processed whenever there is a Sweeper trigger); and (3) Coincidence Sweeper (Sweeper, MoNA and LISA data are processed whenever there is a coincidence between the Sweeper and MoNA/LISA triggers). | The Level-3 trigger GUI gets started by clicking the button ''Launch Level3 Trigger GUI''. It can be used to select the trigger mode: (1) **Sweeper standalone** [Sweeper data are processed when there is a Sweeper trigger, typically coming from the Thin left-up PMT (''thin_LU'') of the FP scintillator]; (2) **Sweeper singles** (Sweeper, MoNA and LISA data are processed whenever there is a Sweeper trigger); and (3) **Coincidence Sweeper** (Sweeper, MoNA and LISA data are processed whenever there is a coincidence between the Sweeper and MoNA/LISA triggers). |
| |
| {{:wiki:l3gui-start.png|L3 GUI}} | {{:wiki:l3gui-start.png|L3 GUI}} |
| In order to set this module you must: | In order to set this module you must: |
| |
| * Select one of the three possible trigger configurations. | * Select one of the three possible trigger configurations. IMPORTANT NOTE: When running the Sweeper DAQ in standalone mode always select **Sweeper standalone**. When running in Slave mode with MoNA/LISA, you can use either **Sweeper singles** or **Coincidence Sweeper** |
| | * Go to the tab ''FPGA Configure''. If the VME crate was power cycled you will need to load the firmware by clicking ''Load'' |
| | * In the tab ''FPGA Configure'', verify that the Coincidence Gate is set to the value 38 {{:wiki:l3gui-fpga.png|L3 GUI FPGA control}} |
| * Click the buttons ''Set XLM'', followed by ''Write File'' | * Click the buttons ''Set XLM'', followed by ''Write File'' |
| * You can click on ''Check XLM'' to verify that the module is set properly. The GUI looks like this: {{:wiki:l3gui-control.png|L3 GUI control}} | * You can click on ''Check XLM'' to verify that the module is set properly. The ''Control page'' tab should look like this: {{:wiki:l3gui-control.png|L3 GUI control}} |
| * Go to the tab ''FPGA Configure'' and verify that the Coincidence Gate is set to the value 38 {{:wiki:l3gui-fpga.png|L3 GUI FPGA control}} | |
| * Finally, it is possible to select a series of up to four different DAQ signals in the tab ''Signal Routing'' {{:wiki:l3gui-signalrouting.png|L3 GUI signal routing}} | * Finally, it is possible to select a series of up to four different DAQ signals in the tab ''Signal Routing'' {{:wiki:l3gui-signalrouting.png|L3 GUI signal routing}} |
| |
| The Trigger GUI appears when the ''Launch ULMTriggerGUI'' button is pressed on [[#Readout GUI]]. The Trigger GUI is a visual display of the various Gate and Delay Generators and logic elements that make up the configurable trigger of the Sweeper. The logic of the trigger decision is readily discerned from a visual inspection of this GUI. Setting the trigger configuration is also done using this GUI. In the standard configuration, the ULM trigger is provided by ''External2'', which comes from the Level3 module. This module provides the trigger condition and a vetoed timestamp used to synchronize events registered by the CCUSB and VMUSB controllers. | The Trigger GUI appears when the ''Launch ULMTriggerGUI'' button is pressed on [[#Readout GUI]]. The Trigger GUI is a visual display of the various Gate and Delay Generators and logic elements that make up the configurable trigger of the Sweeper. The logic of the trigger decision is readily discerned from a visual inspection of this GUI. Setting the trigger configuration is also done using this GUI. In the standard configuration, the ULM trigger is provided by ''External2'', which comes from the Level3 module. This module provides the trigger condition and a vetoed timestamp used to synchronize events registered by the CCUSB and VMUSB controllers. |
| |
| The different signal going through the trigger scheme can be inspected in th Data-U5 oscilloscope. Simply right click on any of the wires to put that signal onto one of the four "Trigger Inspect" channels available at the patch panel of Data-U5, and connect that patch-panel cable to the oscilloscope. By inspecting the various delays, widths and overlaps the user trigger can be configured. | The different signal going through the trigger scheme can be inspected in th Data-U5 oscilloscope. Simply right click on any of the wires to put that signal onto one of the four "Trigger Inspect" channels available at the patch panel of Data-U5, and connect that patch-panel cable to the oscilloscope. By inspecting the various delays, widths and overlaps the user trigger can be configured. In the figure shown above, the trigger inspect channel 1 corresponds to "External 2"; inspect channel 2 corresponds to Sweeper raw trigger (labeled "S800); and inspect channel 3 corresponds to "Live trigger". |
| |
| |
| |
| ==== 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]]. Alternatively, open a terminal on u6pc5, and type **./goscalers** from directory **/user/s800/converged_daq/scalers**. | The GUI used to display scalers rates can be open from the icon **Scalers Sweeper** in the desktop of [[Software#u5pc4 (data U5)|u5pc4]]. Alternatively, open a terminal on u5pc4, and type **./goscalers** from directory **/user/sweeper/develop/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. | The GUI includes three pages labeled "sweeper", "scaler 2", and "ratios" (see figure below). Page "sweeper" includes all the scaler channels; page "scaler 2" includes scaler signal from MoNA/LISA (ask MoNA/LISA group for further details); 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]]. |
| |
| {{:wiki:Scalers.jpg?700|Scaler Display}} | {{:wiki:scalergui.png?700|Scaler Display}} |
| |
| |
| ==== Running in Slave mode with multilogger ==== | ==== Running in Slave mode with multilogger ==== |
| The S800 DAQ can be run in Standalone mode (as described above), or in Slave mode. The later means that the S800 DAQ is controlled by an external DAQ (e.g. GRETINA). In this mode, the S800 ULM receives external clock and external synchronization signals from the master DAQ. Running in Slave mode requires to change the script **CC0105Begin.tcl** in directory **/user/s800/converged_daq/Scripts**. In this file, there are two variables ''extsynch'' and ''extclock'' to define if the external synchronization and clock signals are enabled (=1) or disabled (=0). Make sure that you set these variables to 1 if you want to run in Slave mode. | The Sweeper DAQ can be run in Standalone mode (as described above), or in Slave mode. The later means that the Sweeper DAQ is controlled by an external Master DAQ. This is the standard DAQ configuration when running the Sweeper DAQ along with the MoNA and LISA DAQs. |
| |
| | 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 Sweeper ringbuffer (called ''sweeper'') into the Sweeper stagearea, using the ''multilogger'' option (see ReadoutGUI figure above). |
| |
| 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. | When running XDT for an experiment with a Master DAQ, it is recommendable to run the Sweeper DAQ with the sweeper 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 Sweeper **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 {{:wiki:multilogger.png|Multilogger window}} | * 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-sweeper.png|Multilogger window}} |
| |
| * Check out s800filter to enable recording data from this ring buffer | * Check out ''sweeper'' 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, Sweeper data from every run recorded by the experimenters, will also be recorded in the Sweeper 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. | * After finishing XDT, it is better to disable the sweeper ring-buffer in the multilogger menu so the Sweeper 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 Sweeper DAQ may fail to start. The list below describes what to do to fix these problems. |
| * [[#Old processes still running]] | * [[#Old processes still running]] |
| * [[#No data sources defined]] | * [[#No data sources defined]] |
| |
| ==== 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 previous Sweeper DAQ session ended in an uncontrolled way, there may be old processes running (CCUSB and/or VMUSB and or Sweeper 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: |
| - Exit your Readout GUI properly | - Exit your Readout GUI properly |
| - 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 spdaq34 by typing ''ssh -Y sweeper@spdaq34'' (ask the Device Physicist to get the Sweeper 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 |
| - 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.2-004 |
| - 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**. |
| - If the producer value of a ringbuffer is not -1, take note of the PID, and kill the process by typing ''kill -9 PID'' | - If the producer value of a ringbuffer is not -1, take note of the PID, and kill the process by typing ''kill -9 PID'' |
| - You should now be able to run Readout GUI and begin a run without problem | - You should now be able to run Readout GUI and begin a run without problem |
| |
| |
| {{:wiki:ringbuffer1.png?650|Ringbuffer status}} | {{:wiki:ringbufferstatus.png?850|Ringbuffer status}} |
| |
| ==== No data sources defined ==== | ==== No data sources defined ==== |
| When clicking ''Begin'' in the S800 Readout GUI, you get the error message: "No data sources are running so a run cannot be started". Very likely, the setting file **.settings.tcl** is missing. On a Linux session in u6pc5, type ''ls -lisa ~/stagearea''. You should see a hidden file **.settings.tcl**. If no, try the following: | When clicking ''Begin'' in the Sweeper Readout GUI, you get the error message: "No data sources are running so a run cannot be started". Very likely, the setting file **.settings.tcl** is missing. On a Linux session in u5pc4, type ''ls -lisa ~/stagearea''. You should see a hidden file **.settings.tcl**. If no, try the following: |
| - Go to **/mnt/daqtesting/s800/exxxxlast**, where **exxxxlast** corresponds to the experiment number of the last (successfully) run experiment | - Go to **/mnt/daqtesting/sweeper/exxxxlast**, where **exxxxlast** corresponds to the experiment number of the last (successfully) run experiment |
| - Copy the file **.settings.tcl** from that directory to the current stagearea. **NOTE**: we are assuming that the stagearea is pointing to the new experiment directory **/mnt/daqtesting/s800/exxxxnew** | - Copy the file **.settings.tcl** from that directory to the current stagearea. **NOTE**: we are assuming that the stagearea is pointing to the new experiment directory **/mnt/daqtesting/sweeper/exxxxnew** |
| - If you cannot find that file, there is an old version that can be copied from the directory **/user/s800/converged_daq** | - If you cannot find that file, contact the Device Physicist |
| - You should now be able to run ReadoutGUI without problem | - You should now be able to run ReadoutGUI without problem |
| ==== 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 Sweeper 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 Sweeper spdaq |
| - 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 |
| - Use ''kill -9 PID'', where PID identifies any tclsh ReadoutShell process that might show up | - Use ''kill -9 PID'', where PID identifies any tclsh ReadoutShell process that might show up |
| - Try ''godaq'' to see if this works now | - Try ''godaq'' to see if this works now |
| - If this didn't help try rebooting the S800 DAQ manually (see below) | - If this didn't help, contact the Device Physicist |
| ==== Manual rebooting ==== | ==== Manual rebooting ==== |
| 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 Sweeper vault. Then, the system must be turned back on in the following order. First, CAMAC crate, second VME crate, and third spdaq. PLEASE, contact the Device Physicist before trying this last-resource operation. |
| |
| |
| |
| |
