From 3f37a9eaa6b57408dd1eabd63d0754e0c9244d03 Mon Sep 17 00:00:00 2001 From: Edward Cormany Date: Thu, 2 May 2024 16:14:30 -0400 Subject: [PATCH] update drop tip behavior for 2.18 --- .../opentrons/protocol_api/instrument_context.py | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/api/src/opentrons/protocol_api/instrument_context.py b/api/src/opentrons/protocol_api/instrument_context.py index 5c8dc21e959..a429cfb8a91 100644 --- a/api/src/opentrons/protocol_api/instrument_context.py +++ b/api/src/opentrons/protocol_api/instrument_context.py @@ -1021,11 +1021,6 @@ def drop_tip( If no location is passed (e.g. ``pipette.drop_tip()``), the pipette will drop the attached tip into its :py:attr:`trash_container`. - Starting with API version 2.15, if the trash container is the default fixed - trash, the API will instruct the pipette to drop tips in different locations - within the trash container. Varying the tip drop location helps prevent tips - from piling up in a single location. - The location in which to drop the tip can be manually specified with the ``location`` argument. The ``location`` argument can be specified in several ways: @@ -1044,6 +1039,15 @@ def drop_tip( the ``WasteChute`` object. For example, ``pipette.drop_tip(location=waste_chute)``. + Starting with API version 2.15, if ``location`` is a trash container or not + specified, the API will instruct the pipette to drop tips in different locations + within the trash container. Varying the tip drop location helps prevent tips + from piling up in a single location. + + Starting with API version 2.18, the API will only vary the tip drop location if + ``location`` is not specified. A trash container ``location`` behaves the same + as that trash container's ``.top()``, which is a fixed position. + :param location: Where to drop the tip.