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

Fit ROI projection and use fit parameters as FOM #276

Open
ebadkamil opened this issue Aug 31, 2020 · 1 comment
Open

Fit ROI projection and use fit parameters as FOM #276

ebadkamil opened this issue Aug 31, 2020 · 1 comment
Labels
feature New feature

Comments

@ebadkamil
Copy link
Contributor

Users suggested to have a direct measurement of pulse/beam width via fitting the ROI projection curve with Gaussian and using the fit parameters (sigma, peak-position) as FOM and then eventually use it to correlate with motor positions. This is essential for beam alignment. There was a suggestion from our side to use already existing STD as FOM but users believe it to be quite indirect way.

@ebadkamil ebadkamil added the feature New feature label Aug 31, 2020
@CammilleCC
Copy link
Contributor

CammilleCC commented Apr 12, 2021

Hi all, bumping this feature request :D

SCS has a similar request, but they would also like to store and view the calculated values against different trains and pulses. I'm currently exploring the implementation of this feature with special-suite for the meantime, and I'm thinking how to store the values (e.g., whether to store inside a special-suite model object or to utilize a persistent DB, most likely Redis, and only retrieve the values on demand.)

Would you guys have any suggestions on how to implement this?

EDIT: Slept on it, and realized that Redis also uses RAM XD I tend to use model objects instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature
Projects
None yet
Development

No branches or pull requests

2 participants