Devices
A variety of devices are available for use at SSRL-1-5. Currently only High Throughput (HiTp) diffraction is supported, but more functionality will be added in the future.
While most PV’s are accessible from the ipython session, it’s generally advised to use the GUI elements to adjust parameters like exposure time or frame rates.
Area detectors
Dexela Area Detector: dexDet [Currently not connected]
The Dexela area detector requires dark field correction. We have already included a plan for this purpose.
In [1]: RE( bp.count([dexDet]) ) # basic count plan
In [2]: uids = RE(dark_light_plan([dexDet], shutter)) # take a dark image followed by a light image
MarCCD Area Detector: marDet
The MarCCD area detector does not require any dark field correction and can be used directly
In [1]: RE( bp.count([marDet]) ) # basic count plan
In [2]: RE(mesh_circ_grid([marDet], s_stage.px, -10, 10, 4.5,
s_stage.py, -10, 10, 4.5,
radius=10, skip=4 ))
More to come later?
Fluorescence detectors
Xspress3 Fluorescence Detector: xsp3
The Xspress3 detector writes .h5 files on each acquisition. Both the full multi-channel arrays (MCA’s) and integrated ROI values are accessible via PV access, and can be inspected directly on the python interpreter. Normally ROI ranges should be adjusted from the EDM display.
In [1]: xsp3.channel1.rois.roi01.read()
Out[1]:
OrderedDict([('xsp3_channel1_rois_roi01_value',
{'value': 0.0, 'timestamp': 1598804648.400984})])
Taking single measurements via bp.count is valid.
In [1]: RE(bp.count([xsp3]))
If taking multiple acquisitions in one run, we must make sure the xsp3.total_points
variable matches the number of acquisitions to be taken. This ensures that all MCA’s
in one run will be placed in a single h5 file. Bluesky and Databroker assume
this behavior when accessing saved data. We have done our best to create plans
that cover this use case, but if needed this value can be adjusted manually.
Taking a single acquisition with bp.count requires you to reset
xsp3.total_points to 1.
In [1]: RE(bps.mv(xsp3.total_points, 5))
In [2]: RE(bp.scan([xsp3], motor, -1, 1, 5))
Transient Scan ID: 2 Time: 2020-09-02 09:57:51
Persistent Unique Scan ID: 'f0c7917f-f8bf-4d00-88a6-a9383f0920bb'
New stream: 'primary'
+-----------+------------+------------+
| seq_num | time | motor |
+-----------+------------+------------+
| 1 | 09:57:53.2 | -1.000 |
| 2 | 09:57:54.5 | -0.500 |
| 3 | 09:57:55.6 | 0.000 |
| 4 | 09:57:56.6 | 0.500 |
| 5 | 09:57:57.7 | 1.000 |
+-----------+------------+------------+
generator scan ['f0c7917f'] (scan num: 2)
In [3]: db[-1].table(fill=True)
Out[5]:
time ... xsp3_channel2
seq_num ...
1 2020-09-02 16:57:53.278821945 ... [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, ...
2 2020-09-02 16:57:54.541794538 ... [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, ...
3 2020-09-02 16:57:55.604745626 ... [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, ...
4 2020-09-02 16:57:56.668115139 ... [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, ...
5 2020-09-02 16:57:57.731433153 ... [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, ...
[5 rows x 11 columns]
In [4]: # A more consolidated command
... num=60; xsp3.total_points.put(num); RE(bp.rel_scan([xsp3], px, -40,40, num=num)
Motors
Sample Stage: s_stage
s_stage has the following components, used to control the sample setup.
These can be accessed either from the parent s_stage object or for
convenience by their individual names (px, py, etc)
Component name |
Motor name |
Units |
|---|---|---|
|
Plate x |
mm |
|
Plate y |
mm |
|
Plate z |
mm |
|
Vert x |
steps |
|
Vert x |
steps |
In [1]: RE( bps.mv(s_stage.px, 0) ) # move stage plate x to 0
In [2]: RE( bps.mvr(pz, -1) ) # move stage height -1 from current position
In [3]: %movr pz -1 # Same as above, move relative stage height by -1