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

chore(api): only auto liquid probe with clean tips #17808

Merged
merged 6 commits into from
Mar 20, 2025

Conversation

ryanthecoder
Copy link
Contributor

Overview

If a tip is "wet" it can trigger a false positive, or worse, pull up any remnant drops into the stem.

This adds a variant of the "empty" state of to the pipette state called "clean". When a tip is picked up it now marks it as "clean" instead of empty. This just sets the clean flag in the state and otherwise does the same thing as empty.

Any subsequent liquid action marks the "clean" state as false.

Test Plan and Hands on Testing

Changelog

Review requests

Risk assessment

@ryanthecoder ryanthecoder requested a review from a team as a code owner March 18, 2025 18:31
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.

I see the intent with clean being part of the fluid state because it is sort of "empty but also never has been other than empty", but it's really confusing to have it in the fluid state and to have all the functions that it set it be like set_fluid_clean(). Can we break it out into its own boolean state please? That way we can have empty and clean, or empty and not clean.

We also probably should extend this to tracking the clean state of tips that have been returned, but I don't think we track tip return state at all in the engine so we can do that in another pr.

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.

Excellent, thank you!

@sfoster1 sfoster1 added the gen-analyses-snapshot-pr Generate a healing PR if the analyses snapshot test fails label Mar 20, 2025
Copy link
Contributor

A PR has been opened to address analyses snapshot changes. Please review the changes here: #17840

…ean-tips snapshots (#17840)

This PR was requested on the PR
#17808

Co-authored-by: sfoster1 <[email protected]>
@ryanthecoder ryanthecoder requested a review from a team as a code owner March 20, 2025 20:32
@ryanthecoder ryanthecoder merged commit e76cde2 into edge Mar 20, 2025
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gen-analyses-snapshot-pr Generate a healing PR if the analyses snapshot test fails
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants