fix(api): Speed up unnecessarily slow "prep" plunger motions #16022
Conversation
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
andySigler
deleted the
api-fix-speed-up-unnecessarily-slow-plunger-prep
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Overview
The "prep" plunger speeds were originally set to the slower aspirate/dispense speeds in an overly cautious attempt at avoiding moving inner-tip droplets around.
We had an oversight, however, in that moving droplets is ONLY a concern after a blow-out. Any other time, there is not a risk of droplets inside the tip.
Therefore, we can always move the plunger safely at max speed (without affecting pipetting performance at all), except under the following situation:
bottom(meaning a blow-out has occurred)Happy to discuss implications and concerns if there are any.
Test Plan and Hands on Testing
Changelog
Review requests
Risk assessment