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.

Sign up for GitHub

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

Jump to bottom

multi_pass_tune should use FWHM for next scan #320

Closed
prjemian opened this issue Jun 1, 2020 · 0 comments · Fixed by #321
Closed

multi_pass_tune should use FWHM for next scan #320

prjemian opened this issue Jun 1, 2020 · 0 comments · Fixed by #321
Assignees
@prjemian
Labels
enhancement
Milestone
1.2.5

Comments

@prjemian
Copy link
Contributor

prjemian commented Jun 1, 2020

Presently, the multi_pass_tune() reduces the scan width on each iteration. It has been found empirically to be faster to use the determined FWHM instead.
@prjemian prjemian added this to the 1.2.4 milestone Jun 1, 2020
@prjemian prjemian self-assigned this Jun 1, 2020
prjemian added a commit that referenced this issue Jun 1, 2020
@prjemian
fixes #320
0f22934
@prjemian prjemian mentioned this issue Jun 1, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@prjemian prjemian

Labels
enhancement
Projects
None yet
Milestone
1.2.5
Development

Successfully merging a pull request may close this issue.

multi-pass tune uses FWHM for next scan BCDA-APS/apstools
1 participant
@prjemian