UniteLabs
Reference

Labware

Every physical thing the deck holds: plates, tips, tubes, troughs, carriers, and adapters.

Labware is everything the deck holds: plates, tips and tip racks, tubes and tube racks, troughs, carriers, and adapters. The instruments that move it live under Devices.

Every one of them is a Python object with real dimensions, so an aspirate() call knows where well A1 is in 3D space and a gripper move knows the dimensions of the plate it is picking up. Definitions come from unitelabs.labware, and a definition plugs into the deck and liquid handler API with no special handling.

Start with Standard Labware — your plate, carrier, or tip type may already exist. Define your own only when it does not.

What you can define

TypeBase classUse for
PlatesPlateMicroplates of any well count or geometry
TipsHamiltonTipCustom tip types for Hamilton channels
Tip RacksTipRackRacks holding custom tips
TubesTubeStandalone tubes (Eppendorf, Falcon, etc.)
Tube RacksTubeRackRacks holding tubes
TroughsTroughReagent reservoirs
CarriersHamiltonCarrierPlate, tip, or trough carriers for the deck
AdaptersAdapterPosition-modifying adapters (magnetic, temperature)

Definitions

Standard Labware
Browse and import the pre-built labware types that ship with the library.
Plates
Standard and non-standard microplates of any well count or geometry.
Tips and Tip Racks
Custom tip types for Hamilton channels, and the racks that hold them.
Tubes and Tube Racks
Standalone tubes — Eppendorf, Falcon — and the racks they sit in.
Troughs
Reagent reservoirs, from single-compartment troughs to segmented ones.
Carriers and Adapters
Deck carriers for plates, tips and troughs, plus position-modifying adapters.

Deck

Labware definitions say what exists. A deck layout says where it is. Building and saving one is a how-to, so it lives in Liquid Handling and Robots.

Building a Deck
Arrange carriers and labware into the coordinate frame an instrument can address.
Save and Load a Deck
Persist a layout to JSON and reload it across runs, machines, and CI.
  • Labware and Deck concepts: the model behind the Python objects.
  • Pipetting: commanding an instrument once the deck is built.

Last updated