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

fix(api): Restrict 96ch single tip pickup to only support 1000ul #16195

Open
wants to merge 2 commits into
base: chore_release-8.0.0
Choose a base branch
from

Conversation

CaseyBatten
Copy link
Contributor

Overview

This PR should only be merged if it is deemed by hardware testing that allowing the 96ch to pickup 50ul tips in single channel pickup configuration would cause damage or undesired behavior.

This PR introduces a "NotImplementedError" for the specific case mentioned above. All other 96ch configurations support 50ul tips. All 8ch configurations support 50ul tips.

Test Plan and Hands on Testing

Ensure that no other configuration/tip type pair has been interuppted by this.
Ensure that we raise an error during analysis

Ensure that we raise an error on robot-side analysis

Changelog

Introduced a new error case to the engine side pick up tip function.

Review requests

If hardware testing and QA agree that this is appropriate, feel free to review and merge.

Risk assessment

Low - forbids a new edge case feature we were introducing.

Copy link
Member

@sfoster1 sfoster1 left a comment

Choose a reason for hiding this comment

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

Looks good

@y3rsh y3rsh added the DO NOT MERGE Indicates a PR should not be merged, even if there's a shiny green merge button available label Sep 10, 2024
@y3rsh
Copy link
Collaborator

y3rsh commented Sep 10, 2024

Testing on alpha.5 looked good. Added label but not closing yet.

@CaseyBatten CaseyBatten changed the title fix(api): Restrict 96ch single tip pickup to only support 1000ul and 200ul fix(api): Restrict 96ch single tip pickup to only support 1000ul Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DO NOT MERGE Indicates a PR should not be merged, even if there's a shiny green merge button available
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants