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
Should the control for the two separate slit pairs also be cleanly separated in the code? E.g. each slit pair has its own instance of a control. Alternatively, one could just ignore the second slit pair and make it impossible (error) when trying to access it. As the used DAC has 4 channels as of now, one would have to implement such a way there anyway as both controls would share the DAC, but not its channels obviously.
The text was updated successfully, but these errors were encountered:
I think that is a good idea: the most minimal yet complete control flow contains 2 slits for control of 1 respective dimension. In the code, you can have something like a PlaneController which controls exactly one plane e.g. has input of two corresponding quantities and outputs one control quantity.
Then, in the software interface, we define the how many pairs are connected to the controller: either 1 or 2.
Should the control for the two separate slit pairs also be cleanly separated in the code? E.g. each slit pair has its own instance of a control. Alternatively, one could just ignore the second slit pair and make it impossible (error) when trying to access it. As the used DAC has 4 channels as of now, one would have to implement such a way there anyway as both controls would share the DAC, but not its channels obviously.
The text was updated successfully, but these errors were encountered: