Deck
The deck is the working surface of your liquid handler. Everything the device works with is "placed" on it: labware, consumables, handoff positions and peripherals.
When you call aspirate(plate["A1"]), the software needs to know where well A1 sits in 3D space.
It knows because the plate is placed in a carrier site, which belongs to a carrier, which is placed on the deck at a known position.
The deck is the root of that resource tree and defines the reference coordinate system for all liquid handler work.
Deck
└── Carrier
└── CarrierSite
└── Plate "wellplate"
├── Well A1
├── Well A2
└── ...
Coordinate system
UniteLabs unifies the way you interact with devices, and that includes their decks. Every liquid handler deck uses the same right-handed coordinate system (robotics industry default).
The deck is a 3-dimensional space with x, y and z coordinates:
- x: left → right (track direction)
- y: front → back (depth)
- z: bottom → top (height)
When you stand in front of the device, the origin is the bottom-left corner at the front. Depending on the device, the origin can be below the physical deck surface and beyond the marked tracks.
Offsets
Most of the time you don't need absolute deck positions, because the UniteLabs tooling computes them for you. However, sometimes, to for example correct a small difference in your specific labware, you will need to set offsets. When you do pass an offset to a position or a command, it means the same on every liquid handler:
- a positive x offset moves to the right,
- a positive y offset moves to the back,
- a positive z offset moves up,
even where the vendor software of a device uses a different convention.
Labware
All resources, such as labware, use the same coordinate system as the deck. Place the labware in its natural orientation, for example a plate with well A1 at the back-left. Its origin is then, like the deck's, the bottom-left corner at the front.
Locations
Every resource has two locations:
| Property | What it returns |
|---|---|
resource.location | Position relative to parent |
resource.absolute_location | Absolute position from the deck origin |
A resource's location is the position of its origin relative to the origin of its parent. For a plate in a carrier site, that is the plate's front-left-bottom corner measured from the carrier site's front-left-bottom corner. The absolute location adds up the locations along the resource tree, from the resource up to the deck.
Indexing
Indexing is based on the layout of a standard microplate as it starts in the back-left corner, which is the back left when you stand in front of the deck.
On a plate, well A1 is in the back-left corner.
You can address a well by its label, plate["A1"], or by its integer index, plate[0].
Integer indices count column by column: A1 is 0, B1 is 1, …, H1 is 7 and A2 is 8 for a 96-well plate.
On track-based liquid handlers, deck tracks are numbered from left to right, starting at 1. Position-based liquid handlers number their positions differently: Bravo numbers its 3x3 grid from left to right, row by row (the first column holds locations 1,4,7), and the Beckman Biomek has named positions (e.g. "P1"). Please refer to the respective device pages to learn more. In each carrier, the backmost carrier site has index 0.
For more about how to find and handle specific resources in code, read the labware page.
Persisting deck layout
You can save a deck by serializing it to JSON. The JSON captures everything on the deck, including your custom identifiers and states, for example tips left in a tip rack or liquid volumes in plate wells.
The JSON file can be version controlled to serve as an audit trail for which layout was used at which time and what has changed.
For the conventions on when to use the JSON form vs. a Python-script form of a deck, see Save/load a deck.
Where to go next
- Building a deck — compose a deck from carriers and labware
- Save/load a deck — persist and reload layouts
- Labware — the physical objects that live inside a deck
Last updated