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
Similar to issue #166. The mirrors require an abstract class that should include the following:
-[ ] Get/Set position (already implemented but needs to be written in the abstract class)
-[ ] Get/Set relative position
-[ ]Get/Set Movement Limits
-[ ] Get/Set step resolution
-[ ] Set Home()
-[ ] Set Origin(). Do you think this should be per axis?
Should we standardize this to a specific unit of measurement (i.e deg or um)?
Should we have a position buffer or do we just generate that with some np.linspace()?
@AhmetCanSolak for the movement limits I meant the min/max range on the axis (i.e the optotune has some max degree of rotation, and the galvos also have a maximum scan angle).
For Origin, I guess that's a convenient function to move to the origin. Most devices probably to (0,0) or center?
@YangLiujames the abstract class as it states is for global use not just for the optotune mirror. These should be exposed at a higher level. Currently, the optotune only has the position() and none of the mentioned above.
Similar to issue #166. The mirrors require an abstract class that should include the following:
-[ ] Get/Set position (already implemented but needs to be written in the abstract class)
-[ ] Get/Set relative position
-[ ]Get/Set Movement Limits
-[ ] Get/Set step resolution
-[ ] Set Home()
-[ ] Set Origin(). Do you think this should be per axis?
Should we standardize this to a specific unit of measurement (i.e deg or um)?
Should we have a position buffer or do we just generate that with some
np.linspace()
?@AhmetCanSolak @YangLiujames
The text was updated successfully, but these errors were encountered: