Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add a sscan_1d_step() plan #941

Open
prjemian opened this issue Mar 17, 2024 · 0 comments
Open

add a sscan_1d_step() plan #941

prjemian opened this issue Mar 17, 2024 · 0 comments
Milestone

Comments

@prjemian
Copy link
Contributor

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).

Originally posted by @prjemian in #940 (comment)

@prjemian prjemian added this to the 1.6.20 milestone Mar 17, 2024
@prjemian prjemian modified the milestones: 1.6.20, 1.6.21 May 24, 2024
@prjemian prjemian modified the milestones: 1.7.0, 1.7.1 Aug 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

1 participant