New example: scaler v. motor using sscan record

[prjemian]

• set the scaler count time (SCALER.preset_time)
• setup sscan record
  • number of points
  • motor (start, stop, step parameters)
  • time (as readback of positioner p4), to get timestamp of each step (sscan record feature!)
  • scaler channels
  • detector triggers
• run the scan and wait for finish
• get data as {signal_name, data_array}
  • Must coordinate signal names as assigned in the setup above.
• report as bluesky event documents

[prjemian]

Note apstools.plans.sscan_support.sscan_1D() might need to be updated based on this issue. That's why it is here rather than bluesky_training repo.

apstools/apstools/plans/sscan_support.py

Line 44 in 2ec146d

def sscan_1D(

[prjemian]

Also take note of BCDA-APS/bluesky_training#248 which also has setup and scanning with sscan record (and other records, too).

[prjemian]

Not seeing such a document under Plans. Just the source code documentation.

[prjemian]

Update of sscan_1D is not necessary for this issue.

But, it is worthwhile to replace (or create a new sscan_step_1d() plan that accepts a list of:

• detectors
• triggers
• positioners (readback, setpoint, start, finish, npts or step)

and assigns them to sscan record channels, runs the scan, then posts the data to databroker with meaningful names (such as the examples here).