Starting the LCLS-II interface
The following description assumes you are working as the detopr at det-daq. All the relevant scripts to set up the environment and start the DAQ are located in the folder daq folder:
while all the scripts to change the frame rates, perform charge injection, load configuration files etc, are located under daq/epixhr:
To start up the DAQ, we first have to source the correct environment (from the daq folder). This is done with the following command:
source setup_env.sh
Once the correct environment is set up, the LCLS-II GUI interface is launched using the following command:
./restart_daq.sh
This launches the following windows seen in the following slide: DAQ control, ProcStat, DAQ:ASC,xpmpva and the AMI client hutch: asc. It is worth noting that the DAQ is running on server drp-det-cmp002. For power cycling the server:
serverStat drp-det-cmp002 cycle
When launching the DAQ the following windows show up:
Figure 1. GUI windows that appear when launching the LCLS-II DAQ
The above windows have a lot of similarity to the windows available in the LCLS-I DAQ. The DAQ control allows you to choose what devices to include in the partition, move been between target states (configure, run, etc.), vary the register settings, choose to save data, or just view in the online AMI. The ProcStat allows you to see the status of all the relevant processes running in the DAQ. The DAQ:ASC monitors the detector, with the L0InpRate being the number of received triggers (i,.e frame rate we are running at), and the L0AccRate being the number of frames coming from the detector. These should be the same value. The DAQ:ASC window labeled Group 6 controls the Run trigger, while the window labeled group 0 controlls the DAQ trigger. The AMI client is the online AMI environment. It has a LabView like approach to working with the data, which is described briefly in the following slides. A more detailed description of how to set up different analysis chains in this environment can be found here: https://confluence.slac.stanford.edu/display/LCLSIIData/ami
Partition and change the detector state; look at the detector data
To select devices to include in the partition, press the select button in the partition section (red box in 1).
Figure 2. Procedure to partition and change the state of the detector.
This opens a new window where the default selections are for the ePixHR detector (see 2). Press apply to load in the devices into the partition. The state now changes from unallocated to allocated (green boxes in the centre). Then click the scroll down selector Target state. This open a number of detector target state options to choose from (see 4). To start up and run the detector, follow this sequence of states:
1.Connected;
2.Configured;
3.Running.
The detector is now running without collecting the data. To go back and select to save the data, change the target state to configured and unselect the box in the middle (see 5, red circle), and then go back to Running to start collecting the data. The experiment name and run number the data is saved under is seen in the info section in the center of the GUI. When running, the frame rate and the number of good events, and run time can all be seen in the DAQ:ASC window (see 6). To view the response from the detector in the AMI when running, go to the AMI client and create the visualization you want.
Figure 3. The process to launch the data visualization.
Two default visualizations have been created in the ASC lab. To find these click open, which opens the window seen in 2, and then select the desired fc file. When loading the image_look2.fc option the flow seen in 3 gets loaded, and windows containing an image of the raw data, an image of the RMS of the raw data, an image of the median of the raw data, an image of the image data, and a histogram of the image data. The raw data image of the HR detector can be seen in 4.