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
It seems that the desired position of the default XY stage are set through the setX() and setY() functions. The default Z stage can be set using setZ(). Other stages (also including the default Z Stage ?) can be set through setStageCoordinate(String, double). However, there is no corresponding setXYStageCoordinate(String, double, double).
How are non-default XY stages handled? Also, what is the relation between setZ() and setStageCoordinate(String, double)?
The text was updated successfully, but these errors were encountered:
setStageCoordinate(String, double) was added after setZ() to, as you say, support non-default z stages. Obviously there's a possibility of a collision when you setStageCoordinate on the default stage. I can't remember how I resolved this (should be easy to find in the code), but I remember being unsure about what the correct behavior should be.
You're right, there's no setXYStageCoordinate(String, double, double). I've never encountered a microscope with multiple XY stages, so I never had a reason to add it. You could add it if you want.
If you do want to add something or have an idea of what the correct default behavior should be for one of both of those, you should write a test in pycromanager to ensure that it doesn't get broken in the future. Happy to advise more on how to do this.
It seems that the desired position of the default XY stage are set through the
setX()
andsetY()
functions. The default Z stage can be set usingsetZ()
. Other stages (also including the default Z Stage ?) can be set throughsetStageCoordinate(String, double)
. However, there is no correspondingsetXYStageCoordinate(String, double, double)
.How are non-default XY stages handled? Also, what is the relation between
setZ()
andsetStageCoordinate(String, double)
?The text was updated successfully, but these errors were encountered: