Page History
...
As of April 1, 2024, another detector (0016778240-0176075265-0452984854-4021594881-1962934296-0177446913-0402653206) is being readied for an upcoming beam test. With the delays provided by the detector-specific .yml file and the automatic bad lane disablment done by the Root class on Configure, the third and (later) fourth images above were obtained.
Running the DAQ
In a nutshell, log in to drp-neh-ctl002. You can use your own account or detopr (if you can make it work), but avoid rixopr for now. Change directory to where you want to work and execute the following:
Code Block | ||
---|---|---|
| ||
ln -s ~rixopr/git/lcl2_040324/setup_env.sh
cp ~rixopr/git/lcl2_040324/psdaq/psdaq/cnf/epixM.cnf . |
You can modify the .cnf
copy as you see fit. Prior to running the DAQ, source the setup_env file. Run the DAQ with procmgr start epixM.cnf
. There are a set of scan scripts available which can be run as:
Code Block | ||
---|---|---|
| ||
python ~rixopr/git/lcls2_040324/psdaq/psdaq/cas/epixhr_timing_scan.py -p 3 -C drp-neh-ctl002 --hutch tst --config BEAM --detname epixm_0 --scantype timing --events 2000 --record 1
python ~rixopr/git/lcls2_040324/psdaq/psdaq/cas/epixm_pedestal_scan.py -p 3 -C drp-neh-ctl002 --hutch tst --config BEAM --detname epixm_0 --scantype pedestal --events 2000 --record 1
python ~rixopr/git/lcls2_040324/psdaq/psdaq/cas/epixm_chargeinj_scan.py -p 3 -C drp-neh-ctl002 --hutch tst --config BEAM --detname epixm_0 --scantype chargeinj --events 2000 --record 1 |
Move the DAQ in the ALLOCATED
or CONNECTED
state prior to executing one of them.
Details
The beam-test ePixM is currently in the FEE test stand. Run the DAQ as follows:
Code Block | ||
---|---|---|
| ||
ssh rixdrp-daq -l rixoprneh-ctl002 cd scripts . ./setup_env_epixm.sh procmgr start fee_epixM.cnf |
A bunch of windows will come up after the procmgr start
command is given. Usually the first thing to do is to click the Select
button in the Partition
area of the DAQ Control
GUI. It may take a few moments before the Select partition
window pops up (called Rollcall
), depending on previous history and the state of the system. Once the window appears, select the detectors you want to include in your run. The detectors will by default be assigned to the readout group (grp
) for the platform on which you launched the DAQ (nominally 2). Under some circumstances, this must be changed, but can be left alone for now. Optionally select ami-meb0
if you plan to use AMI. It should look like the first screen-shot below:
...
Code Block | ||
---|---|---|
| ||
python ~~rixopr/git/lcls2_040324/psdaq/psdaq/cas/epixhr_timing_scan.py -p 3 -C drp-neh-ctl002 --hutch tst --config BEAM --detname epixm_0 --scantype timing --events 2000 --record 1 python ~~rixopr/git/lcls2_040324/psdaq/psdaq/cas/epixm_pedestal_scan.py -p 3 -C drp-neh-ctl002 --hutch tst --config BEAM --detname epixm_0 --scantype pedestal --events 2000 --record 1 python ~~rixopr/git/lcls2_040324/psdaq/psdaq/cas/epixm_chargeinj_scan.py -p 3 -C drp-neh-ctl002 --hutch tst --config BEAM --detname epixm_0 --scantype chargeinj --events 2000 --record 1 |
...