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(shared-data) Update tip overlap values for Flex Pipettes #15147

Merged
merged 5 commits into from
May 10, 2024

Conversation

Carlos-fernandez
Copy link
Contributor

Overview

After conducting hardware testing, we've formulated updated tip overlap values for every tip size and pipette model. These adjustments apply to 1-channel, 8-channel, and 96-channel pipettes. These revised values aim to mitigate overpressure occurrences in ABR.

https://docs.google.com/spreadsheets/d/16dEmqulO4SIKU6E0aYTfVQEnZRTn3MwNF_WB8K1KmRM/edit#gid=0

Test Plan

None

Changelog

Pipette shared data

P1KS Single Channel

  • Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
  • Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips.

P50S Single Channel Pipette

  • Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
  • Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips.

P1KM 8 Channel Pipette

  • Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
  • Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips.

P50M 8 Channel Pipette

  • Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
  • Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips

P1H 95-Channel Pipette

  • Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
  • Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips

Review requests

Risk assessment

Low

@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 May 9, 2024
@y3rsh
Copy link
Member

y3rsh commented May 9, 2024

Meeting 5/10 to discuss confidence and testing before merging. Added DO NOT MERGE label for now.

@Carlos-fernandez Carlos-fernandez requested a review from a team as a code owner May 9, 2024 20:18
@y3rsh y3rsh removed the DO NOT MERGE Indicates a PR should not be merged, even if there's a shiny green merge button available label May 10, 2024
Copy link
Member

@y3rsh y3rsh left a comment

Choose a reason for hiding this comment

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

:shipit:

@y3rsh y3rsh merged commit 0096c12 into chore_release-7.3.0 May 10, 2024
46 checks passed
@y3rsh y3rsh deleted the chore-shared-data-update-overlap-values branch May 10, 2024 20:05
sfoster1 added a commit that referenced this pull request May 14, 2024
…15147)"

This reverts commit 0096c12.

The above commit needs to be gated behind a protocol API version.
sfoster1 added a commit that referenced this pull request May 14, 2024
#15178)

…(#15147)"

This reverts commit 0096c12.

The above commit needs to be gated behind a protocol API version.
sfoster1 added a commit that referenced this pull request May 29, 2024
<!--
Thanks for taking the time to open a pull request! Please make sure
you've read the "Opening Pull Requests" section of our Contributing
Guide:


https://github.com/Opentrons/opentrons/blob/edge/CONTRIBUTING.md#opening-pull-requests

To ensure your code is reviewed quickly and thoroughly, please fill out
the sections below to the best of your ability!
-->

# Overview
After conducting hardware testing, we've formulated updated tip overlap
values for every tip size and pipette model. These adjustments apply to
1-channel, 8-channel, and 96-channel pipettes. These revised values aim
to mitigate overpressure occurrences in ABR.


[https://docs.google.com/spreadsheets/d/16dEmqulO4SIKU6E0aYTfVQEnZRTn3MwNF_WB8K1KmRM/edit#gid=0](url)


<!--
Use this section to describe your pull-request at a high level. If the
PR addresses any open issues, please tag the issues here.
-->

# Test Plan
None
<!--
Use this section to describe the steps that you took to test your Pull
Request.
If you did not perform any testing provide justification why.

OT-3 Developers: You should default to testing on actual physical
hardware.
Once again, if you did not perform testing against hardware, justify
why.

Note: It can be helpful to write a test plan before doing development

Example Test Plan (HTTP API Change)

- Verified that new optional argument `dance-party` causes the robot to
flash its lights, move the pipettes,
then home.
- Verified that when you omit the `dance-party` option the robot homes
normally
- Added protocol that uses `dance-party` argument to G-Code Testing
Suite
- Ran protocol that did not use `dance-party` argument and everything
was successful
- Added unit tests to validate that changes to pydantic model are
correct

-->

# Changelog
### **Pipette shared data**
### P1KS Single Channel
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips.
### P50S Single Channel Pipette
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips.
### P1KM 8 Channel Pipette
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips.
### P50M 8 Channel Pipette
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips
### P1H 95-Channel Pipette
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips

<!--
List out the changes to the code in this PR. Please try your best to
categorize your changes and describe what has changed and why.

Example changelog:
- Fixed app crash when trying to calibrate an illegal pipette
- Added state to API to track pipette usage
- Updated API docs to mention only two pipettes are supported

IMPORTANT: MAKE SURE ANY BREAKING CHANGES ARE PROPERLY COMMUNICATED
-->

# Review requests

<!--
Describe any requests for your reviewers here.
-->

# Risk assessment
Low
<!--
Carefully go over your pull request and look at the other parts of the
codebase it may affect. Look for the possibility, even if you think it's
small, that your change may affect some other part of the system - for
instance, changing return tip behavior in protocol may also change the
behavior of labware calibration.

Identify the other parts of the system your codebase may affect, so that
in addition to your own review and testing, other people who may not
have the system internalized as much as you can focus their attention
and testing there.
-->

---------

Co-authored-by: Seth Foster <[email protected]>
sfoster1 added a commit that referenced this pull request May 29, 2024
sfoster1 added a commit that referenced this pull request May 31, 2024
<!--
Thanks for taking the time to open a pull request! Please make sure
you've read the "Opening Pull Requests" section of our Contributing
Guide:


https://github.com/Opentrons/opentrons/blob/edge/CONTRIBUTING.md#opening-pull-requests

To ensure your code is reviewed quickly and thoroughly, please fill out
the sections below to the best of your ability!
-->

# Overview
After conducting hardware testing, we've formulated updated tip overlap
values for every tip size and pipette model. These adjustments apply to
1-channel, 8-channel, and 96-channel pipettes. These revised values aim
to mitigate overpressure occurrences in ABR.


[https://docs.google.com/spreadsheets/d/16dEmqulO4SIKU6E0aYTfVQEnZRTn3MwNF_WB8K1KmRM/edit#gid=0](url)


<!--
Use this section to describe your pull-request at a high level. If the
PR addresses any open issues, please tag the issues here.
-->

# Test Plan
None
<!--
Use this section to describe the steps that you took to test your Pull
Request.
If you did not perform any testing provide justification why.

OT-3 Developers: You should default to testing on actual physical
hardware.
Once again, if you did not perform testing against hardware, justify
why.

Note: It can be helpful to write a test plan before doing development

Example Test Plan (HTTP API Change)

- Verified that new optional argument `dance-party` causes the robot to
flash its lights, move the pipettes,
then home.
- Verified that when you omit the `dance-party` option the robot homes
normally
- Added protocol that uses `dance-party` argument to G-Code Testing
Suite
- Ran protocol that did not use `dance-party` argument and everything
was successful
- Added unit tests to validate that changes to pydantic model are
correct

-->

# Changelog
### **Pipette shared data**
### P1KS Single Channel
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips.
### P50S Single Channel Pipette
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips.
### P1KM 8 Channel Pipette
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips.
### P50M 8 Channel Pipette
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips
### P1H 95-Channel Pipette
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips

<!--
List out the changes to the code in this PR. Please try your best to
categorize your changes and describe what has changed and why.

Example changelog:
- Fixed app crash when trying to calibrate an illegal pipette
- Added state to API to track pipette usage
- Updated API docs to mention only two pipettes are supported

IMPORTANT: MAKE SURE ANY BREAKING CHANGES ARE PROPERLY COMMUNICATED
-->

# Review requests

<!--
Describe any requests for your reviewers here.
-->

# Risk assessment
Low
<!--
Carefully go over your pull request and look at the other parts of the
codebase it may affect. Look for the possibility, even if you think it's
small, that your change may affect some other part of the system - for
instance, changing return tip behavior in protocol may also change the
behavior of labware calibration.

Identify the other parts of the system your codebase may affect, so that
in addition to your own review and testing, other people who may not
have the system internalized as much as you can focus their attention
and testing there.
-->

---------

Co-authored-by: Seth Foster <[email protected]>
sfoster1 added a commit that referenced this pull request May 31, 2024
sfoster1 pushed a commit that referenced this pull request Jun 4, 2024
After conducting hardware testing, we've formulated updated tip overlap
values for every tip size and pipette model. These adjustments apply to
1-channel, 8-channel, and 96-channel pipettes. These revised values aim
to mitigate overpressure occurrences in ABR.

[https://docs.google.com/spreadsheets/d/16dEmqulO4SIKU6E0aYTfVQEnZRTn3MwNF_WB8K1KmRM/edit#gid=0](url)

- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips.
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips.
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips.
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips
sfoster1 pushed a commit that referenced this pull request Jun 4, 2024
After conducting hardware testing, we've formulated updated tip overlap
values for every tip size and pipette model. These adjustments apply to
1-channel, 8-channel, and 96-channel pipettes. These revised values aim
to mitigate overpressure occurrences in ABR.

[https://docs.google.com/spreadsheets/d/16dEmqulO4SIKU6E0aYTfVQEnZRTn3MwNF_WB8K1KmRM/edit#gid=0](url)

- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips.
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips.
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips.
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips
- Updated V3_5 Tip Overlap values for 50uL, 200uL, and 1000uL tips.
- Updated V3_6 Tip Overlap values for 50uL 200uL, and 1000uL tips
sfoster1 pushed a commit that referenced this pull request Jun 4, 2024
After conducting hardware testing, we've formulated updated tip overlap
values for every tip size and pipette model. These adjustments apply to
1-channel, 8-channel, and 96-channel pipettes. These revised values aim
to mitigate overpressure occurrences in ABR.

[https://docs.google.com/spreadsheets/d/16dEmqulO4SIKU6E0aYTfVQEnZRTn3MwNF_WB8K1KmRM/edit#gid=0](url)

- Added v2 tip overlap values for all flex pipette-tip combos
sfoster1 pushed a commit that referenced this pull request Jun 4, 2024
After conducting hardware testing, we've formulated updated tip overlap
values for every tip size and pipette model. These adjustments apply to
1-channel, 8-channel, and 96-channel pipettes. These revised values aim
to mitigate overpressure occurrences in ABR.

[https://docs.google.com/spreadsheets/d/16dEmqulO4SIKU6E0aYTfVQEnZRTn3MwNF_WB8K1KmRM/edit#gid=0](url)

- Added v2 tip overlap values for all flex pipette-tip combos
sfoster1 added a commit that referenced this pull request Jun 5, 2024
#15147) (#15284)

This is #15147 again but this time outside the context of an extremely
imminent release.

While this code needs to be merged, we should carefully consider how we
do so. We can't ship this until we can separate this behavior by API
level so that customers who may have tuned in offsets based on the old
incorrect tip offsets won't have their protocols invalidated - this data
needs to be loaded by API level.

Closes EXEC-452

---------

Co-authored-by: Carlos-fernandez <[email protected]>
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.

3 participants