fix(api): check for nozzle map configuration when executing complex commands #15723
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
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.
Overview
Addresses RQA-2867
Previously any multi channel pipettes would not allow you to pass wells for transfers that were not in Row A. This allows partial configurations to be passed any well to target directly during transfers/consolidate/distribute/mix, similar to a single channel transfer.
Test Plan
Ensure OT-2 and Flex can utilize complex commands in protocols with expected movement results.
Changelog
Review requests
Risk assessment
Because this allows users to pass any well, if they incorrectly count the wells they must index by it can lead to movement that does not behave in a desired fashion. However, conflict check will prevent executing layouts that would create a collision, so the safety risk is low.