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(api): Handle overpressures in AspirateInPlace, DispenseInPlace #15791

Merged
merged 2 commits into from
Jul 26, 2024

Conversation

sfoster1
Copy link
Member

@sfoster1 sfoster1 commented Jul 24, 2024

Use DefinedErrorData for pipette overpressures in AspirateInPlace and DispenseInPlace.

This is mostly similar to adding the same handling for Aspirate and Dispense, but the big difference is that these commands are not associated with wells or with points via their params.

We get the current point by asking the hardware where it is; it's important to do this rather than getting it from the state because someone could conceivably have called AspirateInPlace/DispenseInPlace as the first command after a move command with a different pipette, and we wouldn't have the point in state.

We don't get the current well at all. That's because this command isn't associated with a well, so there's not really anything to change.

Closes EXEC-496
Closes EXEC-622

Testing

  • Run a protocol that uses in place aspirate and dispense
  • cause an overpressure error and make sure it now goes into error recovery
  • make sure that error recovery moves back to the right place when retrying

Use DefinedErrorData for pipette overpressures in AspirateInPlace.

This is mostly similar to adding the same handling for Aspirate and
Dispense, but the big difference is that these commands are not
associated with wells or with points via their params.

We get the current point by asking the hardware where it is; it's
important to do this rather than getting it from the state because
someone could conceivably have called AspirateInPlace as the first
command after a move command with a different pipette, and we wouldn't
have the point in state.

We don't get the current well at all. That's because this command isn't
associated with a well, so there's not really anything to change.

Closes EXEC-496
@sfoster1 sfoster1 requested a review from a team as a code owner July 24, 2024 21:04
@sfoster1 sfoster1 changed the title feat(api): Handle overpressures in AspirateInPlace feat(api): Handle overpressures in AspirateInPlace, DispenseInPlace Jul 25, 2024
@sfoster1
Copy link
Member Author

Tested on a robot and it does seem to work!

Copy link
Contributor

@SyntaxColoring SyntaxColoring left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sweet. Good call on getting the position from the HW API instead of PE state.

@sfoster1 sfoster1 merged commit 2e11766 into edge Jul 26, 2024
21 checks passed
@sfoster1 sfoster1 deleted the exec-496-in-place-commands branch July 26, 2024 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants