PD 9.0.0 manual revisions#21559
Conversation
emilyburghardt
changed the base branch from
chore_release-pd-8.10.2
to
docs-release-9.1.0
emilyburghardt
force-pushed
the
docs-pd-8.10.2
branch
from
9d97c61 to
3acd9ce
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## edge #21559 +/- ##
==========================================
+ Coverage 21.69% 22.28% +0.59%
==========================================
Files 3906 3907 +1
Lines 320209 320282 +73
Branches 57718 57709 -9
==========================================
+ Hits 69465 71377 +1912
+ Misses 247755 245910 -1845
- Partials 2989 2995 +6
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
emilyburghardt
temporarily deployed
to
pd-non-prod
GitHub Actions
Inactive
emilyburghardt
changed the base branch from
docs-release-9.1.0
to
chore_release-pd-8.10.2
emilyburghardt
changed the base branch from
chore_release-pd-8.10.2
to
docs-release-9.1.0
ecormany
added
the
DO NOT MERGE
jwwojak
left a comment
jwwojak
left a comment
There was a problem hiding this comment.
Not a PD expert by any means, but a few thoughts for review.
| </figure> | ||
|
|
||
| Even though the tip rack above is full of pipette tips, the "not enough tips" warning tells you that there aren't enough tips that the pipette can safely access. This results in a collision error to prevent the pipette from striking adjacent labware in your final protocol. | ||
| Even though the tip rack above is full of pipette tips, the "not enough tips" warning tells you that there aren't enough tips that the pipette can safely access to complete your protocol step. This results in a collision error to prevent the pipette from striking adjacent labware in your final protocol. |
There was a problem hiding this comment.
This really is fine as is, just a suggestion for consideration to reduce some words and sharpen the edge a bit:
| Even though the tip rack above is full of pipette tips, the "not enough tips" warning tells you that there aren't enough tips that the pipette can safely access to complete your protocol step. This results in a collision error to prevent the pipette from striking adjacent labware in your final protocol. | |
| Even though the tip rack above is full, the "not enough tips" warning indicates that the pipette cannot safely access them to complete the step. The software triggers a collision error to prevent the pipette from striking adjacent labware during your protocol run. |
You could also say, "The robot triggers a collions error.." or "The Flex trigges a collision error..." too.
¯_(ツ)_/¯
| Even though the tip rack above is full of pipette tips, the "not enough tips" warning tells you that there aren't enough tips that the pipette can safely access to complete your protocol step. This results in a collision error to prevent the pipette from striking adjacent labware in your final protocol. | ||
|
|
||
| To fix the collision error, move the tip racks so they are no longer adjacent, or change your tip pickup selections. | ||
| To fix the collision error in the example above, move the well plate from slot C3 so the labware items are no longer adjacent, or change your tip pickup selections. |
There was a problem hiding this comment.
Could change "fix" to "resolve" but that's also used on line 181 below, so repetition?
Consider trying an "either...or" for this sentence as a signal to the reader that there are some options coming:
To fix the collision error in the example above, either move the well plate from slot C3 so the labware items are no longer adjacent, or change your tip pickup selections.
Could do bullets here too!
To fix the collision error in this example, you can either:
- Move the well plate...
- Change your tip pickup selections
With bullets, you get some nice punchy imperative verbs (do this! do that!).
|
|
||
| Fix all errors before exporting to ensure your protocol runs successfully. You won't be able to run protocols with unresolved errors. | ||
|
|
||
| To make it easier to resolve tip pickup warnings, be sure **Manual tip tracking** is selected, then click to select tips for manual pickup. This form can show you which selection is causing the collision error, and which tip pickups could work for your step. |
There was a problem hiding this comment.
Bullets might work here as well.
To resolve tip pickup warnings more easily:
- Select Manual tip tracking
- Click to select tips for manual pickup
This form can show you which section...
ecormany
removed
the
DO NOT MERGE
ecormany
left a comment
ecormany
left a comment
There was a problem hiding this comment.
Joe's comments look good. Addressing them would be enough to merge.
Can of worms question: The "Transfer steps" page is now well over 2000 words plus screenshots. Should we consider breaking it into 4 pages (for each of its H2 sections)?
3 participants
Overview
Adds a description of an improvement for PD 9.0.0/OT-2 PD 26.6.0.
previously: a user experiences a potential collision warning and might not know what's causing it.
now: a user experiences a potential collision warning; PD describes the slot the item(s) causing the risk/warning are located in and users can open the tip selection modal to see where tip pickups might be causing a warning.
DO NOT MERGE until PD 9.0.0 release, at which time I can merge this PR and complete a docs deploy from
edge:)Test Plan and Hands on Testing
sandbox
Changelog
See above.
Review requests
Risk assessment
low.