-
Notifications
You must be signed in to change notification settings - Fork 175
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
docs(api): Refactor liquid control section #13396
docs(api): Refactor liquid control section #13396
Conversation
Added a comment to make this different from the branch, docs-refactor-building-blocks-commands to create a draft PR.
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## docs-refactor-building-block-commands #13396 +/- ##
========================================================================
Coverage ? 71.68%
========================================================================
Files ? 2427
Lines ? 67568
Branches ? 7779
========================================================================
Hits ? 48433
Misses ? 17306
Partials ? 1829
Flags with carried forward coverage won't be shown. Click here to find out more. |
Need to make simple change to switch to a different branch.
Plus a few others throughout before lunch.
Moving on to next sections.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lots of little stuff but in general this section covers what it needs to!
api/docs/v2/new_atomic_commands.rst
Outdated
**************** | ||
============== | ||
|
||
After attaching a tip, your robot is ready to aspirate, dispense, and perform other liquid handling tasks. The API provides the following methods that help you manipulate liquids in your protocols. These include: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some thoughts on this list…
- Either
the following methods
orThese include
depending on whether this list is exhaustive — it at least appears to be w.r.t. what this page covers. - For the list itself, we probably shouldn't repeat
InstrumentContext.
every time, for readability. - I'm torn on whether each item should link directly to the reference, or whether it should link down this page. Each subsection begins with a
:py:meth:
link to the reference, for anyone who's looking for reference entries rather than prose explanations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was uncomfortable with the bullet list too. Let's try something different, a bit more general without links to methods or page sections. I will summarize what the page covers and let the section headers and table of contents do the work of links in a bullet list.
Utility commands next.
Co-authored-by: Ed Cormany <[email protected]>
- add shortcut to "Move To" section in robot_position - Revisions to liquid handling sections after Aspirate/Dispense - Blow out - Touch tip - Mix - Air gap Done for now, ready for another review.
In text linking to another doc, changing "well" to "pipette." Th
Minor sentence changes. Will call this done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a straightforward section, and it's definitely cleaner than before. A few more touchups and it'll be good to go!
.. _new-aspirate: | ||
pipette.pick_up_tip() | ||
pipette.aspirate(200, plate['A1']) | ||
protocol.delay(seconds=5) # pause for 5 seconds |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here and everywhere, two spaces before the #
that begins an inline comment. Because Black.
|
||
pipette.blow_out(protocol.fixed_trash['A1']) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
api/docs/v2/new_atomic_commands.rst
Outdated
radius=0.75, | ||
v_offset=-2) | ||
|
||
When ``radius=1``, the robot moves the centerline of the pipette’s plunger axis to the exact edge of the well. Sometimes this means a pipette tip may hit the well wall or edge first and bends inwards. Setting the radius to < 1 helps avoid hitting the well wall prematurely. If you need to use it, test the radius argument first before starting a protocol production run. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe a chance for some levity here, along the lines of:
"The purpose of touch_tip
is to touch the edges of the well, not to crash into them. Using a smaller radius and lower speed produces gentler motion. Droplets of different types of liquid behave differently, so test out these parameters in a single well before performing a full protocol run."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ooof, that's what passes for humor? Borscht Belt here we come! Time for some Pocono Palaver. Tip your waitstaff, enjoy the veal, I'm here all week. badum tsssss.
I'd like to keep some of Seth's explanation in here. How about trying to combine some of these:
Revised
The touch_tip
feature allows the pipette to touch the edges of a well gently instead of crashing into them. When radius=1
the robot moves the centerline of the pipette’s plunger axis to the edge of the well. This means a pipette tip may sometimes hit the well wall too early, causing the tip to bend inwards. A smaller radius helps avoid a premature wall collision and a lower speed produces gentler motion. Different liquid droplets behave differently, so test out these parameters in a single well before performing a full protocol run.
.. code-block:: python | ||
This example aspirates 200 µL of air 5 mm above the current well:: | ||
|
||
pipette.air_gap(volume=200) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
200 is a biiiiiiig air gap. Maybe use 20, like the existing example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The section is based on, and linked to, those sample protocol files on another page. I selected 200 b/c the linked examples use a 1000 uL pipette. Drawing 20 ul of air from a 1000 ul pipette doesn't seem like a good example (or even accurately possible). That's why this uses such a large amount of air.
From the section intro:
The examples used here assume that you've loaded the pipettes and labware from the basic
:ref:protocol template <protocol-template>.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Check for lets
--> let's
throughout.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets as in 3rd person singular is ok, right? As in giving you the ability, capability, or permission to do whatever it is. This method "allows you to do the thing"
This method lets you . . .
not
This method let's you . . .
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, not one for find and replace! Regular expressions can't save you here 🤪
Batch commit. Another check and more changes to come. Co-authored-by: Ed Cormany <[email protected]>
Co-authored-by: Ed Cormany <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New changes look good, this is ready to merge into the feature branch.
f48e112
into
docs-refactor-building-block-commands
* Adding comments to make different from edge At top of the doc, these comments should be deleted when we're done. Had to add something to make the branch code different from edge. Can't easily open a PR if the branch and edge are the same. Simple comments easier than forcing an empty commit. * Revised summary and new intro sections Revised the intro paragraph that summarizes the page contents. Also, added the intro sections on how the page code is structured, what labware/instruments are used, and include base protocol code for Flex and OT-2 in tabs. * Remove repeated content labware and protocol This was the content used in the Examples section. Removing it because it's long and repetitious. Instead, each section will include a short sentence linking to the protocol file template/example. * docs(api): refactor-tip-handling (#13383) * New pickup tip text and code samples Includes a revised section header and intro. Focus is on pick_up_tip method. * tips revisions: iterate, drop, return, and used 3 sections. The original "iterate through tips" becomes a section on loops and tip pickup. Then, the doc picks up from the original with drop tips, return tips. Final section cleans up info about using "used" tips. More after lunch revisions to come. * Minor text adjustment * Used tips text, small edits * Tips section finish up and a first review Will run through again on Monday. Checked code snippets with base code sample/protocol. They work. Formatting via Black formatter style. * Minor text and space adjustments * Monday morning review and minor adjustments * Tips intro, simplify last sentence * Adding protocol template text and link * Apply suggestions from code review Returning to the tip handling section. Committing previous review comments. Co-authored-by: Ed Cormany <[email protected]> * Saving stashed changes after batch commit to keep text synched up * Fixed conflicts, restored H2 section header * Basic tip pick up and using a loop for pickup * Automating tip pickup intro Something weird going on. Trying again. * Working with used tips * Small changes in tip manipulation section. * API raise error, not throw an error --------- Co-authored-by: Ed Cormany <[email protected]> * docs(api): Refactor liquid control section (#13396) * New branch for Liquid Control section Added a comment to make this different from the branch, docs-refactor-building-blocks-commands to create a draft PR. * Adjust section header, make H2 Need to make simple change to switch to a different branch. * Touch tip, blow out, dispense revisions Plus a few others throughout before lunch. * Touch tip revisions * Revisions to Mix section * Air gap section revisions * Add text and link to protocol template code * End of day review edits * Remove horizontal line between sections * Aspirate section revisions * Finish aspirate revisions, start dispense * Start dispense, end of day push * Final review of aspirate, start dispense * Dispense and aspirate revisions done for now Moving on to next sections. * Blow out revisions * Starting touch tip revisions, add option sections * touch_tip and blow_out text, short small changes * Mix revisions * Mix revisions * Air gap revisions, finish Liquid Handling section Utility commands next. * Remove intro bullet list, fix Aspirate headers * Apply suggestions from code review Co-authored-by: Ed Cormany <[email protected]> * API versions capitalization and case * Mix and air_gap changes, make similar, use text * add shortcut, revise remaining liquid sections - add shortcut to "Move To" section in robot_position - Revisions to liquid handling sections after Aspirate/Dispense - Blow out - Touch tip - Mix - Air gap Done for now, ready for another review. * Suggested word change-that's it for Friday In text linking to another doc, changing "well" to "pipette." Th * Small edits to air gap and touch tip Minor sentence changes. Will call this done. * Apply suggestions from code review Batch commit. Another check and more changes to come. Co-authored-by: Ed Cormany <[email protected]> * Update api/docs/v2/new_atomic_commands.rst Co-authored-by: Ed Cormany <[email protected]> * Let's get rid of some lets * Touch tip update * Let's look for more lets --------- Co-authored-by: Ed Cormany <[email protected]> * docs(api): Refactor utility commands section (#13406) * Creating stub PR for Utility section For Building Block Commands doc. * Fix section headers * Start section summary * Section intro starting draft save * Section intro - add full method links * Section comments removed. * Delay method revisions * Utility commands intro, delay/resume, pause meths * Homing, lights, and comments * Door safety switch section * Homing and safety switch adjustments * Utility last check * Utility intro changes * Delay/resume, pause, rail light checks * Intro and comment features * Minor edits to comment and homing * Making reviewer changes * Utility delete image, fix homing * restore header lost in merge conflict * Fix merge conflicts with main PR * 1st push reorganized sections same content * Revise parent page "og" short description * Content summaries for page links * Small edit to summary intro * Apply suggestions from code review Co-authored-by: Ed Cormany <[email protected]> * Final updates --------- Co-authored-by: Ed Cormany <[email protected]>
Overview
This PR is for managing changes made to the "Liquid Control" section of the doc, Building Block Commands.
Following the plan laid out in this Figma file. This PR is for the second small branch section in Merge Strategy 1 of the Figma file.
The original manipulating tips section has 6 parts:
Test Plan
Changelog
Review requests
The usual suspects.
Risk assessment
Low, docs changes only.