-
Notifications
You must be signed in to change notification settings - Fork 179
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
fix(api): Fix liquid getting homed into pipette after certain protocols end #17285
Merged
SyntaxColoring
merged 1 commit into
chore_release-8.3.0
from
do_not_home_plungers_when_run_ends
Jan 16, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
In the old code:
If
home_after_stop
wasTrue
, theself._hardware_api.stop(...)
call would home everything, including the plungers.I think this used to be safe when this code was originally written. The line immediately preceding it,
self._drop_tip()
, would have ensured that there were no tips attached, and therefore no liquid for the home to accidentally aspirate.But that assumption stopped holding for Flex protocols with PAPIv≥2.16; since then,
self._drop_tip()
has been a no-op (see the comments in_try_to_drop_tips()
.) So thisself._hardware_api.stop(...)
was accidentally homing with tips possibly still attached and liquid possibly still in them.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.
With my fix here, nothing in this file should ever home the plungers anymore.
We could try to be a little fancier than that. We could home the plungers specifically in the cases where the robot did drop tips. I haven't done that here because it doesn't seem worth the complexity. The plungers will home when the next run begins, anyway.
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.
no, i agree with this fix. let's just not home the damn things, it's too hard to pick the right behavior