fix(protocol-designer): fix logic in safePipetteMovements collision detection #15602
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…etection Several errors in `safePipetteMovements` collision logic were causing errors to be raised in `transfer` command creator calls using a 96-channel pipette with COLUMN configuration. This PR addresses these errors by 1) passing `wellLocationPoint` to `getPipetteBoundsAtSpecifiedMoveToPosition` to get correct pipette bounds, 2) passing the surrounding labware ID rather than the target labware ID to `getHighestZInSlot`, and 3) not early-returning if the highest Z in the surrounding slot does not exceed to the pipette bounds at that slot. Closes RAUT-1046
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes RAUT-1046
Overview
Several errors in
safePipetteMovementscollision logic were causing errors to be raised intransfercommand creator calls using a 96-channel pipette with COLUMN configuration. This PR addresses these errors bywellLocationPointtogetPipetteBoundsAtSpecifiedMoveToPositionto get correct pipette boundsgetHighestZInSlot, andTest Plan
Changelog
Review requests
Risk assessment