docs(api): update descriptions of partial tip pickup behavior for 7.3 #15003
+11
−28
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
CaseyBatten
reviewed
Apr 24, 2024
CaseyBatten
approved these changes
Apr 29, 2024
| @@ -106,6 +106,10 @@ When switching between full and partial pickup, you may want to organize your ti | |||
| partial_tip_racks = [tips_1, tips_2] | |||
| full_tip_racks = [tips_3, tips_4] | |||
|
|
|||
| .. Tip:: | |||
|
|
|||
| It's also good practice to keep separate lists of tip racks when using multiple partial tip pickup configurations (i.e., using both column 1 and column 12 in the same protocol). This improves positional accuracy when picking up tips. Additionally, use Labware Position Check in the Opentrons App to ensure that the partial configuration is well-aligned to the rack. | |||
There was a problem hiding this comment.
This looks good and communicates what we want. Regarding the last sentence, I think we need to confirm what exactly LPC looks like for partial configuration (I personally have never encountered it) and communicate that if possible.
There was a problem hiding this comment.
Just spoke with Sanniti, looks like LPC for partial tips is just standard LPC. You'd account for the tip overlap offset during said LPC, then presumably only use the partial configuration you LPC'd for on that piece of labware. So I think this documentation is acceptable on that front, we don't want to over-explain and end up causing confusion once this problem is addressed in full.
ecormany
changed the title
ecormany
added a commit
that referenced
this pull request
May 2, 2024
…#15003) Update partial tip pickup docs to reflect the latest behavior, as added in #15009 and to be released in robot software 7.3. Addresses RTC-440. [Sandbox](http://sandbox.docs.opentrons.com/docs-partial-pickup-channel-1/v2/) - Removed "Column 12" and "Column 1" headers from Partial Tip Pickup page. Removed tip-tracking code for Column 1 as no longer needed.. - Reworded note in `configure_nozzle_layout` API reference entry. Already spoke with @CaseyBatten to get an idea of what needed to be included here and what will go in separate documentation. - <s>Should we actually put this straight into `edge` and deploy ASAP, or can it wait a month and roll out with 2.18 docs (current plan)?</s> PAPI 2.18 deploy will be timed with robot stack 7.3 release, which this aligns with. none
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
Update partial tip pickup docs to reflect the latest behavior, as added in #15009 and to be released in robot software 7.3.
Addresses RTC-440.
Test Plan
Sandbox
Changelog
configure_nozzle_layoutAPI reference entry.Review requests
Already spoke with @CaseyBatten to get an idea of what needed to be included here and what will go in separate documentation.
Should we actually put this straight intoPAPI 2.18 deploy will be timed with robot stack 7.3 release, which this aligns with.edgeand deploy ASAP, or can it wait a month and roll out with 2.18 docs (current plan)?Risk assessment
none