Anytime the wavelength of the M Squared is changed, the beam alignment of the SolsTiS resets to its default values.
When does this occur?
Any time the wavelength is changed, both in Qudi and in the browser.
Where on the platform does it happen?
At the SolsTiS.
How do we replicate the issue?
Change the wavelength and see what happens.
Expected behavior (i.e. solution)
Short term: store the Beam X and Beam Y positions, then set them after the wavelength is changed.
Long term: write own 'One Shot' beam realignment to run on wavelength change.
Other Comments
'One Shot' beam alignment is slow, possibly don't do this every time - make a separate function to change and maximise beam alignment.
What is affected by this bug?
Anytime the wavelength of the M Squared is changed, the beam alignment of the SolsTiS resets to its default values.
When does this occur?
Any time the wavelength is changed, both in Qudi and in the browser.
Where on the platform does it happen?
At the SolsTiS.
How do we replicate the issue?
Change the wavelength and see what happens.
Expected behavior (i.e. solution)
Short term: store the Beam X and Beam Y positions, then set them after the wavelength is changed. Long term: write own 'One Shot' beam realignment to run on wavelength change.
Other Comments
'One Shot' beam alignment is slow, possibly don't do this every time - make a separate function to change and maximise beam alignment.