-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
436 multiposition table focus needs to be ignored when switching from low to high res #437
436 multiposition table focus needs to be ignored when switching from low to high res #437
Conversation
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## develop #437 +/- ##
===========================================
- Coverage 41.81% 41.74% -0.07%
===========================================
Files 151 151
Lines 13855 13902 +47
===========================================
+ Hits 5793 5804 +11
- Misses 8062 8098 +36
Flags with carried forward coverage won't be shown. Click here to find out more.
|
@@ -63,6 +63,7 @@ MicroscopeState: | |||
timepoint_interval: 0 | |||
experiment_duration: 600.0899999999995 | |||
is_multiposition: False | |||
multipostion_count: 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we keep track of just the positions, without adding this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we could keep track of positions by using a specific LoopByPosition instead of a general LoopByCount feature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could LoopByCount
by default keep track of the number of things it iterates over? Seems like this could be useful for timepoints and channels as well as positions.
Notes from our conversation:
There could also be an edge case where the non-ideal focus is found (e.g., it exists out of the specified range). I guess if the range is large enough, this shouldn't be a problem (we should find it). |
I ran "Volume Search" and then "Decoupled Focus Stage Multiposition". The program threw a DAQ error
The stage moved to its zero position, the program took one image and then stopped. Logs attached. |
Hang on. I think this might be an issue with |
Nope, same issue. |
Still moving to the zero stage position and then stopping. |
Please add "robust_fit: True" under "AutoFocusParameters" in experiment.yml file. |
Same problem. |
Co-Authored-By: Annie Wang <6161065+annie-xd-wang@users.noreply.github.com>
Now working as expected. Let's add unit tests for the multi-position feature and the new flag in z-stack. |
Please test to see if it works with the device. Load feature "Decoupled Focus Stage Multiposition", run in "Customized" mode. Do not select "Enable Multi-Position" on the GUI. It works as (Loop) Move To the Next Position -> Autofocus -> ZStack.
Do not merge it. If-else for the Autofocus needs to be added in the feature sequence.