-
Notifications
You must be signed in to change notification settings - Fork 178
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): section on Position Relative to Trash Containers #14593
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## docs_release-2.18 #14593 +/- ##
==================================================
Coverage 67.50% 67.50%
==================================================
Files 2514 2514
Lines 72376 72376
Branches 9317 9317
==================================================
Hits 48857 48857
Misses 21314 21314
Partials 2205 2205
Flags with carried forward coverage won't be shown. Click here to find out more.
|
365f7da
to
45e54bd
Compare
OK, after a near-miss rebasing this onto |
api/docs/v2/robot_position.rst
Outdated
Position Relative to Trash Containers | ||
===================================== | ||
|
||
In API version 2.15 and earlier, trash containers are :py:class:`.Labware` objects that have a single well. Use the above techniques for labware to adjust position relative to trash containers in protocols specifying these API versions. |
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.
Word choice: "techniques" stands out as unusual to me. The content referred to are methods.
Might it make sense to write something like, "Use the labware methods above to adjust position relative to trash containers ..."
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.
Added review comments for consideration. Defer to others re: go/no go approvals.
|
||
If only a ``location`` is passed (e.g., | ||
``pipette.dispense(location=plate['A1'])``), all of the | ||
liquid aspirated into the pipette will be dispensed (the | ||
amount is accessible through :py:attr:`current_volume`). | ||
|
||
.. versionchanged:: 2.18 |
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 and the other methods in instrument context can accept TrashBin and WasteChute starting in version 2.16
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 knew I had confused something. Thanks for checking!
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.
Great revision.
…er methods (#14610) # Overview It's time for Python API version 2.18! Trash container `top()` methods are the first features included in this version-in-progress. # Test Plan - [sandbox](http://sandbox.docs.opentrons.com/papi-2.18-in-edge-time/v2/new_protocol_api.html#opentrons.protocol_api.TrashBin) - automated tests # Changelog - bump max supported version - decorate trash container top methods - hide those methods from API reference, for now. they will be _shown_ in #14593 and the 2.18 docs feature branch. # Review requests sensible? correct? well-timed? # Risk assessment v low. this version bump was coming sooner or later and shouldn't affect anything up through 2.17.
# Overview Follow up to further explain behavior introduced in #14560. Addresses RTC-400. # Test Plan - [sandbox](http://sandbox.docs.opentrons.com/docs-trash-offsets/v2/robot_position.html#position-relative-to-trash-containers) - simulated snippets in 2.16 / `edge` # Changelog - new § on Labware and Deck Positions page - updated description and example for `move_to()` to cover new acceptable `location`s - version added statements for `TrashBin`, `WasteChute`, and their methods in API Reference # Review requests - double check code snippets. not only simulate, but do what i say they do? - confirm version added for the methods. it feels like we may need to gate this to 2.17, because otherwise there will be a big functionality gap between robot system 7.1 (which can't do any of this) and 7.2 (which can). the classes are unambiguously _New in version 2.16._ # Risk assessment low…but see API version gate caveat above.
# Overview Follow up to further explain behavior introduced in #14560. Addresses RTC-400. # Test Plan - [sandbox](http://sandbox.docs.opentrons.com/docs-trash-offsets/v2/robot_position.html#position-relative-to-trash-containers) - simulated snippets in 2.16 / `edge` # Changelog - new § on Labware and Deck Positions page - updated description and example for `move_to()` to cover new acceptable `location`s - version added statements for `TrashBin`, `WasteChute`, and their methods in API Reference # Review requests - double check code snippets. not only simulate, but do what i say they do? - confirm version added for the methods. it feels like we may need to gate this to 2.17, because otherwise there will be a big functionality gap between robot system 7.1 (which can't do any of this) and 7.2 (which can). the classes are unambiguously _New in version 2.16._ # Risk assessment low…but see API version gate caveat above.
# Overview Follow up to further explain behavior introduced in #14560. Addresses RTC-400. # Test Plan - [sandbox](http://sandbox.docs.opentrons.com/docs-trash-offsets/v2/robot_position.html#position-relative-to-trash-containers) - simulated snippets in 2.16 / `edge` # Changelog - new § on Labware and Deck Positions page - updated description and example for `move_to()` to cover new acceptable `location`s - version added statements for `TrashBin`, `WasteChute`, and their methods in API Reference # Review requests - double check code snippets. not only simulate, but do what i say they do? - confirm version added for the methods. it feels like we may need to gate this to 2.17, because otherwise there will be a big functionality gap between robot system 7.1 (which can't do any of this) and 7.2 (which can). the classes are unambiguously _New in version 2.16._ # Risk assessment low…but see API version gate caveat above.
# Overview Follow up to further explain behavior introduced in #14560. Addresses RTC-400. # Test Plan - [sandbox](http://sandbox.docs.opentrons.com/docs-trash-offsets/v2/robot_position.html#position-relative-to-trash-containers) - simulated snippets in 2.16 / `edge` # Changelog - new § on Labware and Deck Positions page - updated description and example for `move_to()` to cover new acceptable `location`s - version added statements for `TrashBin`, `WasteChute`, and their methods in API Reference # Review requests - double check code snippets. not only simulate, but do what i say they do? - confirm version added for the methods. it feels like we may need to gate this to 2.17, because otherwise there will be a big functionality gap between robot system 7.1 (which can't do any of this) and 7.2 (which can). the classes are unambiguously _New in version 2.16._ # Risk assessment low…but see API version gate caveat above.
…er methods (#14610) # Overview It's time for Python API version 2.18! Trash container `top()` methods are the first features included in this version-in-progress. # Test Plan - [sandbox](http://sandbox.docs.opentrons.com/papi-2.18-in-edge-time/v2/new_protocol_api.html#opentrons.protocol_api.TrashBin) - automated tests # Changelog - bump max supported version - decorate trash container top methods - hide those methods from API reference, for now. they will be _shown_ in #14593 and the 2.18 docs feature branch. # Review requests sensible? correct? well-timed? # Risk assessment v low. this version bump was coming sooner or later and shouldn't affect anything up through 2.17.
Overview
Follow up to further explain behavior introduced in #14560.
Addresses RTC-400.
Test Plan
edge
Changelog
move_to()
to cover new acceptablelocation
sTrashBin
,WasteChute
, and their methods in API ReferenceReview requests
Risk assessment
low…but see API version gate caveat above.