Page History
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
usage: rix_bluesky_scan.py [-h] [-p {0,1,2,3,4,5,6,7}] [-C COLLECT_HOST] [-t TIMEOUT] [-c READOUT_COUNT] [-g GROUP_MASK] [--config ALIAS]
[--detname DETNAME] [--scantype SCANTYPE] [--seqctl SEQCTL [SEQCTL ...]] [--record] [-v]
optional arguments:
-h, --help show this help message and exit
-p {0,1,2,3,4,5,6,7} platform (default 2)
-C COLLECT_HOST collection host (default drp-neh-ctl001)
-t TIMEOUT timeout msec (default 10000)
-c READOUT_COUNT # of events to aquire at each step (default 120)
-g GROUP_MASK bit mask of readout groups (default 36)
--config ALIAS configuration alias (default BEAM)
--detname DETNAME detector name (default 'scan')
--scantype SCANTYPE scan type (default 'scan')
--seqctl SEQCTL [SEQCTL ...]
sequence control (e.g. DAQ:NEH:XPM:0:SeqReset 4 [DAQ:NEH:XPM:0:SeqDone])
--record enable recording of data
-v be verbose |
The optional "seqctl" argument is sent to the DAQ on the configure transition. The optional "detname" argument is used by the DAQ to determine which readout group to use to count events.
- The first argument to "seqctl" is the PV to restart the sequence
- The second argument is a bit mask of sequence engines to restart
- The third (optional) argument is which variable to use to detect that the sequence is complete. It defaults to "StepDone" in the daq code (control.py) when using "number of counts" to end the step. One uses "SeqDone" when using an XPM sequence, and the third case is when we're using the accelerator to burst, and this is set to listen to a variable from them telling them that the burst is complete.
step_value Handling
PV scans automatically generate a 1-based step counter named "step_value" and record it alongside motor positions, like so:
...
Overview
Content Tools