You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Video Demo

A video demo from Matt Weaver on Oct. 9, 2020: https://pswww.slac.stanford.edu/swdoc/tutorials/lcls2_daq_demo.mp4

Launching

From the hutch console (or remotely after "ssh tmo-daq -l tmoopr"):

cd /cds/group/pcds/dist/pds/tmo/scripts
source setup_env.sh
./restart_daq.sh  (for TMO DAQ)
./restart_fee.sh  (for FEE DAQ)

Launching the DAQ opens the GUI windows:

  1. ProcStat
  2. DAQ Control
  3. Trigger Monitoring
  4. AMI Client


Closing

./stop_daq.sh  (for TMO DAQ)

./stop_fee.sh   (for FEE DAQ)

ProcStat

This window summarizes the status of the running processes used by the DAQ.  Interaction with this GUI is only for diagnostic purposes.

ProcStat

DAQ Control

This window is used to manage detector readout configuration, select detectors which are included in the DAQ, and control the running and recording of the detector readouts.

The "Configuration" section has an "Edit" button for opening the detector configurations, as seen on the right.  The operator may select from any of the detectors supported.  The resulting GUI is a tree of configuration parameters with typically three sections: "help", "user", and "expert".  The help section is a read-only textual description of the user fields, those used most often.  Changes may be entered and saved with the "Apply" button.




The "Partition" section is for choosing the detectors that will take part in the DAQ.  The "Select" button opens the selection GUI.  It's important that all the required detectors are selected.  Also, a readout group "grp" may be assigned.  Detectors in the same readout group are triggered by the same eventcode.  Currently, the "Select" window may not show all of the available detectors.  In this case, close the window and open again.  One retry is all that is needed.



Once the set of detectors is selected, the running and recording is managed by the "Control" section of the GUI.  The partition automatically enters the "Allocated" state.  The user may advance to the RUNNING state to begin acquiring data.  Detector readouts will be configured when passing through the CONFIGURED state.  The option to record data is selected by clicking the cylindrical hard disk icon; no recording is indicated by a bold X through the icon.  A new recorded run may be started by backing out to the CONFIGURED state before entering the RUNNING state again.  The RESET state is used to recover from errors, after which the partition must be selected again (above paragraph).  Note that BLD may not configure if it is not being generated by the sources, for example, if beam is not being delivered to the soft x-ray line.

DAQ Control

DAQ Monitoring

To monitor the status of the DAQ, open a browser and go to one of the following "grafana" web pages:

TMO Grafana Web Page

RIX Grafana Web Page

It is important to watch for large dead time and large damage.  These can be caused by crashing DAQ processes or incorrect DAQ configuration (e.g. event codes used to trigger the DAQ).

There are drop-down menus on the top left for the instrument (tmo, rix, ued, ...) partition number (also called "platform number" in, for example, tmo.cnf) and readout groups (described above).  There are four plots the should be monitored:  the top-right shows the trigger rates for various detectors, middle-right shows the integrated number of damaged events for each detector (reset at each run boundary) the bottom-right shows the instantaneous damage-rate for each detector, and the left plot shows overall trigger rates and deadtime.  On the upper right one can also select the time range to display and update interval.

AMI: Graphical Realtime Data Analysis

This window is used to operate the online monitoring.  Instructions for the use of AMI may be found here (ami).


AMI Client

  • No labels