You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: