Skip to content
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

feat: aspirate should check volume and tip attached before moving to location #13197

Open
geographybuff opened this issue Jul 29, 2023 · 0 comments
Labels
feature-request A request for a new feature or a change that isn't a bug. May require further triage or scoping.

Comments

@geographybuff
Copy link

Overview

Using the Jupyter Notebook with API version 2.11, the pipette.aspirate command first moves to the location, then checks if a tip is attached, and then checks if the volume exceeds the max. This code returns an error first if a tip is not attached, and then if the volume is too high. This can create problems when the pipette moves to a well containing sensitive materials, and risks unnecessarily contacting a well or unnecessarily spreading its contents due to a command for a transfer that cannot complete due to excessive volume. Instead, the protocol should have recognized that the aspiration was impossible as soon as the aspirate command was made with excessive volume. This seems to be related to the commit b97846b, in which an error is now returned after a command to aspirate more than the allowed volume. However, this maximum volume error, or a tip not attached error, should be returned before the pipette moves to the location, to avoid unnecessary motion.

Implementation details

No response

Design

No response

Acceptance criteria

No response

@geographybuff geographybuff added the feature-request A request for a new feature or a change that isn't a bug. May require further triage or scoping. label Jul 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A request for a new feature or a change that isn't a bug. May require further triage or scoping.
Projects
None yet
Development

No branches or pull requests

1 participant