Skip to content
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

Merged
merged 9 commits into from
Mar 8, 2024

Conversation

ecormany
Copy link
Contributor

@ecormany ecormany commented Mar 4, 2024

Overview

Follow up to further explain behavior introduced in #14560.

Addresses RTC-400.

Test Plan

  • sandbox
  • 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 locations
  • 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.

@ecormany ecormany requested a review from a team as a code owner March 4, 2024 19:18
@ecormany ecormany requested review from jwwojak, jbleon95 and a team and removed request for a team March 4, 2024 19:18
Copy link

codecov bot commented Mar 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.50%. Comparing base (d6d9416) to head (6590f44).

Additional details and impacted files

Impacted file tree graph

@@                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           
Flag Coverage Δ
g-code-testing 92.43% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
...i/src/opentrons/protocol_api/instrument_context.py 89.09% <ø> (ø)

api/docs/v2/robot_position.rst Outdated Show resolved Hide resolved
api/src/opentrons/protocol_api/disposal_locations.py Outdated Show resolved Hide resolved
@ecormany ecormany force-pushed the docs-trash-offsets branch from 365f7da to 45e54bd Compare March 7, 2024 15:34
@ecormany ecormany changed the base branch from edge to docs_release-2.18 March 7, 2024 17:22
@ecormany ecormany requested review from jwwojak and jbleon95 March 7, 2024 17:22
@ecormany
Copy link
Contributor Author

ecormany commented Mar 7, 2024

OK, after a near-miss rebasing this onto docs_release.2-18, this is ready for another review. Not much prose has changed (except some added in the API reference). Version added/changed notices have changed and moved around quite a bit — make sure I've tagged everything properly, especially related features added prior to 2.18.

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.
Copy link
Contributor

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 ..."

Copy link
Contributor

@jwwojak jwwojak left a 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
Copy link
Contributor

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

Copy link
Contributor Author

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!

@jbleon95 jbleon95 self-requested a review March 7, 2024 21:58
@ecormany ecormany requested a review from jwwojak March 7, 2024 22:36
Copy link
Contributor

@jwwojak jwwojak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great revision.

:shipit:

ecormany added a commit that referenced this pull request Mar 8, 2024
…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.
@ecormany ecormany merged commit 2630fb9 into docs_release-2.18 Mar 8, 2024
22 checks passed
ecormany added a commit that referenced this pull request Mar 8, 2024
# 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.
ecormany added a commit that referenced this pull request Mar 29, 2024
# 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.
ecormany added a commit that referenced this pull request Apr 19, 2024
# 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.
ecormany added a commit that referenced this pull request May 2, 2024
# 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.
Carlos-fernandez pushed a commit that referenced this pull request May 20, 2024
…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.
@ecormany ecormany deleted the docs-trash-offsets branch October 16, 2024 20:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants