You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of the current version of the protocol API, it is no longer possible to set pipette tip presence without monkeypatching. This is a regression from previous API implementations.
Such a feature is important for starting from a point where a tip rack is not full. This is critical for reducing plastic waste or wasteful man hours manually reracking pipette tips.
Currently, this works when using old version of the api (with a deprecation warning), however, its foreseeable that newer hardware would be incompatible with old versions of the API. Im not sure if its possible to manually set tips on a Flex, for example, since my work is on the OT2.
Implementation details
For tipbox-type labware, provide a setter for the has_tip property
Design
No response
Acceptance criteria
No response
The text was updated successfully, but these errors were encountered:
croots
added
the
feature-request
A request for a new feature or a change that isn't a bug. May require further triage or scoping.
label
Jan 22, 2025
Overview
As of the current version of the protocol API, it is no longer possible to set pipette tip presence without monkeypatching. This is a regression from previous API implementations.
Such a feature is important for starting from a point where a tip rack is not full. This is critical for reducing plastic waste or wasteful man hours manually reracking pipette tips.
Currently, this works when using old version of the api (with a deprecation warning), however, its foreseeable that newer hardware would be incompatible with old versions of the API. Im not sure if its possible to manually set tips on a Flex, for example, since my work is on the OT2.
Implementation details
For tipbox-type labware, provide a setter for the
has_tip
propertyDesign
No response
Acceptance criteria
No response
The text was updated successfully, but these errors were encountered: