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
When performing optical optimization (confocal), it’s possible that the center of the fit lies outside the actual ‘optimization window,’ causing the scanner to jump a considerable distance. I’ve observed jumps exceeding three times the range of the optimization window, often due to noise. In most cases, this behavior is undesirable.
My suggestion is to prevent the scanner position from moving outside the optimization window. There are several ways to achieve this:
No Movement: If the fit center lies outside the window, the scanner should remain stationary.
Edge Limitation: Alternatively, limit the scanner movement to the edges of the optimization window.
Fit Parameter Constraints: Consider restricting the fit parameter ranges to ensure the center remains within the optimization window.
Related Problem
see above
Considered Alternatives
keep the existing behaviour
Additional Context
No response
Contact Details
No response
The text was updated successfully, but these errors were encountered:
I like this idea! We are encountering the same issue in our lab. I would be in favor of treating an optimized position outside the optimizer area as a failed fit, i.e. the first of your three suggestions. As a user, I would expect the optimization to happen within the specified area and not beyond.
Feature Description
When performing optical optimization (confocal), it’s possible that the center of the fit lies outside the actual ‘optimization window,’ causing the scanner to jump a considerable distance. I’ve observed jumps exceeding three times the range of the optimization window, often due to noise. In most cases, this behavior is undesirable.
My suggestion is to prevent the scanner position from moving outside the optimization window. There are several ways to achieve this:
Related Problem
see above
Considered Alternatives
keep the existing behaviour
Additional Context
No response
Contact Details
No response
The text was updated successfully, but these errors were encountered: