Skill Tracer
Skills › Scientific Agent Skills › opentrons-integration › liquid_handling.md

liquid_handling.md

434 lines · skills/opentrons-integration/references/liquid_handling.md at 5f2bc03

Open on GitHub
1# Liquid Handling Guide
2
3Choose commands from the physical behavior the assay needs, not from which call
4is shortest to write. Every command still depends on correct liquid volumes,
5labware geometry, pipette range, tips, and contamination controls.
6

Liquid Handling Guide

Choose commands from the physical behavior the assay needs, not from which call is shortest to write. Every command still depends on correct liquid volumes, labware geometry, pipette range, tips, and contamination controls.

Raw lines 1 to 6
7## Command Layers
8

Command Layers

Raw lines 7 to 8
9### Building-block commands
11Use when aspiration and dispensing need independent control:
13```python
14pipette.pick_up_tip()
15pipette.aspirate(50, source.bottom(z=1), flow_rate=25)
16protocol.delay(seconds=1)
17pipette.dispense(50, destination.bottom(z=2), flow_rate=20, push_out=5)
18pipette.blow_out(destination.top(z=-1))
19pipette.drop_tip()
20```
22Advantages:
24- Explicit position and order.
25- Independent flow rates and delays.
26- Fine control for viscous, volatile, foaming, low-volume, or bead workflows.
28Costs:
30- The author owns tip state and volume state.
31- More opportunities to aspirate with no tip, overfill the pipette, or leave
32 residual volume.

Building-block commands

Use when aspiration and dispensing need independent control:

pipette.pick_up_tip()
pipette.aspirate(50, source.bottom(z=1), flow_rate=25)
protocol.delay(seconds=1)
pipette.dispense(50, destination.bottom(z=2), flow_rate=20, push_out=5)
pipette.blow_out(destination.top(z=-1))
pipette.drop_tip()

Advantages:

  • Explicit position and order.
  • Independent flow rates and delays.
  • Fine control for viscous, volatile, foaming, low-volume, or bead workflows.

Costs:

  • The author owns tip state and volume state.
  • More opportunities to aspirate with no tip, overfill the pipette, or leave residual volume.
Raw lines 9 to 33
34### Standard complex commands
36Use for conventional source-to-destination mappings:
38```python
39pipette.transfer(
40 volume=50,
41 source=source_plate.wells()[:8],
42 dest=destination_plate.wells()[:8],
43 new_tip="always",
44 mix_after=(3, 30),
46```
48- `transfer()`: one or more source-to-destination transfers.
49- `distribute()`: one source to many destinations, normally with an excess
50 disposal volume.
51- `consolidate()`: many sources into one destination.
53Inspect the simulation run log. Complex commands expand into many building
54blocks, and their expansion changes with parameters and API level.

Standard complex commands

Use for conventional source-to-destination mappings:

pipette.transfer(
    volume=50,
    source=source_plate.wells()[:8],
    dest=destination_plate.wells()[:8],
    new_tip="always",
    mix_after=(3, 30),
)
  • transfer(): one or more source-to-destination transfers.
  • distribute(): one source to many destinations, normally with an excess disposal volume.
  • consolidate(): many sources into one destination.

Inspect the simulation run log. Complex commands expand into many building blocks, and their expansion changes with parameters and API level.

Raw lines 34 to 55
56### Liquid-class complex commands, Flex API 2.24+
58Use an Opentrons-verified class when the pipette/tip combination is supported
59and the liquid resembles the verified model:
61```python
62viscous = protocol.get_liquid_class("glycerol_50")
64pipette.transfer_with_liquid_class(
65 liquid_class=viscous,
66 volume=50,
67 source=reservoir["A1"],
68 dest=plate["A1"],
69 new_tip="always",
70 trash_location=trash,
72```
74Related methods:
76- `distribute_with_liquid_class()`
77- `consolidate_with_liquid_class()`
79Verified classes include water, 80% ethanol, and 50% glycerol. A liquid class
80controls multiple coupled properties such as flow rate, submerge and retract
81behavior, delays, air gaps, positions, and push-out. Do not casually override
82one property without testing the full result.
84Opentrons-verified liquid classes are for supported Flex pipette and tip
85combinations, not OT-2 pipettes.

Liquid-class complex commands, Flex API 2.24+

Use an Opentrons-verified class when the pipette/tip combination is supported and the liquid resembles the verified model:

viscous = protocol.get_liquid_class("glycerol_50")

pipette.transfer_with_liquid_class(
    liquid_class=viscous,
    volume=50,
    source=reservoir["A1"],
    dest=plate["A1"],
    new_tip="always",
    trash_location=trash,
)

Related methods:

  • distribute_with_liquid_class()
  • consolidate_with_liquid_class()

Verified classes include water, 80% ethanol, and 50% glycerol. A liquid class controls multiple coupled properties such as flow rate, submerge and retract behavior, delays, air gaps, positions, and push-out. Do not casually override one property without testing the full result.

Opentrons-verified liquid classes are for supported Flex pipette and tip combinations, not OT-2 pipettes.

Raw lines 56 to 86
87## Source and Destination Mapping
89Complex commands accept a single well or a sequence. Make the intended mapping
90explicit:
92- One source, one destination: one transfer.
93- One source, many destinations: repeated transfers or a distribution.
94- Many sources, one destination: repeated transfers or a consolidation.
95- Equal-length source and destination lists: pairwise transfers.
97Do not assume row-major ordering:
99```python
100# Explicit sample order is easier to audit.
101sample_wells = [plate[name] for name in ("A1", "B1", "C1", "D1")]
102```
104For multi-channel pipettes, the referenced well anchors the pipette's primary
105channel:
107- A full 8-channel pipette normally targets an entire column by referencing its
108 A-row well.
109- A full 96-channel pipette addresses an entire 96-well rack or plate.
110- A partial-column layout has a different primary channel; follow the layout
111 documentation rather than reusing full-column assumptions.

Source and Destination Mapping

Complex commands accept a single well or a sequence. Make the intended mapping explicit:

  • One source, one destination: one transfer.
  • One source, many destinations: repeated transfers or a distribution.
  • Many sources, one destination: repeated transfers or a consolidation.
  • Equal-length source and destination lists: pairwise transfers.

Do not assume row-major ordering:

# Explicit sample order is easier to audit.
sample_wells = [plate[name] for name in ("A1", "B1", "C1", "D1")]

For multi-channel pipettes, the referenced well anchors the pipette's primary channel:

  • A full 8-channel pipette normally targets an entire column by referencing its A-row well.
  • A full 96-channel pipette addresses an entire 96-well rack or plate.
  • A partial-column layout has a different primary channel; follow the layout documentation rather than reusing full-column assumptions.
Raw lines 87 to 112
113## Tip Policy
115`new_tip` is a contamination decision.
117For standard `distribute()` and `consolidate()`, `new_tip="always"` still uses
118one tip for the entire command, including refills. The isolation behavior below
119applies to `transfer()`; use explicit transfers or building blocks for
120independent samples. Liquid-class commands have their own policies.
122| Policy | Typical use | Primary risk |
123| --- | --- | --- |
124| `"always"` | Independent samples, controls, or source-destination pairs | Higher tip consumption |
125| `"once"` | Reagent distribution within one contamination domain | Returning a contaminated tip to a shared source |
126| `"never"` | Explicit surrounding `pick_up_tip()` and `drop_tip()` | Hidden or invalid tip state |
128For a shared reagent:
130- Aspirating repeatedly from the same source with one tip may be acceptable only
131 if the tip never contacts incompatible destination liquid.
132- A submerged dispense can wet the exterior or interior of the tip.
133- Touch tip, mix, or bottom-contact dispense increases contamination risk.
134- Controls and samples generally require separate tips.
136Calculate tips for every conditional path. Multi-channel operations consume
137sets, not individual command calls.

Tip Policy

new_tip is a contamination decision.

For standard distribute() and consolidate(), new_tip="always" still uses one tip for the entire command, including refills. The isolation behavior below applies to transfer(); use explicit transfers or building blocks for independent samples. Liquid-class commands have their own policies.

PolicyTypical usePrimary risk
"always"Independent samples, controls, or source-destination pairsHigher tip consumption
"once"Reagent distribution within one contamination domainReturning a contaminated tip to a shared source
"never"Explicit surrounding pick_up_tip() and drop_tip()Hidden or invalid tip state

For a shared reagent:

  • Aspirating repeatedly from the same source with one tip may be acceptable only if the tip never contacts incompatible destination liquid.
  • A submerged dispense can wet the exterior or interior of the tip.
  • Touch tip, mix, or bottom-contact dispense increases contamination risk.
  • Controls and samples generally require separate tips.

Calculate tips for every conditional path. Multi-channel operations consume sets, not individual command calls.

Raw lines 113 to 138
139## Flow Rate, Position, and Delays

Flow Rate, Position, and Delays

Raw lines 139 to 140
141### Flex 50 µL volume modes
143The nominal 1–50 µL range spans two modes. With an empty Flex 1- or 8-channel
14450 µL pipette, call `configure_for_volume()` before pickup:
146```python
147pipette.configure_for_volume(1)
148pipette.pick_up_tip()
149pipette.aspirate(1, source)
150pipette.dispense(1, destination)
151pipette.drop_tip()
152```
154Inputs 1–4.9 µL select a 1–30 µL mode; inputs 5–50 µL select a 5–50 µL mode.
155Tips may further limit capacity. Reconfigure while empty when changing modes,
156and requalify low-volume delivery for the actual liquid. Simulation validates
157the mode/range contract, not accuracy at 1 µL.
159The 10.0.0 simulator reports `min_volume=0.5` in low-volume mode, below the
160official guide's 1 µL lower limit. Keep the documented 1 µL limit unless
161Opentrons explicitly qualifies a lower range for the exact hardware and tips;
162the property alone is not evidence of accuracy below 1 µL. Mode changes also
163reset flow rates, so apply any validated custom rate after changing mode.

Flex 50 µL volume modes

The nominal 1–50 µL range spans two modes. With an empty Flex 1- or 8-channel 50 µL pipette, call configure_for_volume() before pickup:

pipette.configure_for_volume(1)
pipette.pick_up_tip()
pipette.aspirate(1, source)
pipette.dispense(1, destination)
pipette.drop_tip()

Inputs 1–4.9 µL select a 1–30 µL mode; inputs 5–50 µL select a 5–50 µL mode. Tips may further limit capacity. Reconfigure while empty when changing modes, and requalify low-volume delivery for the actual liquid. Simulation validates the mode/range contract, not accuracy at 1 µL.

The 10.0.0 simulator reports min_volume=0.5 in low-volume mode, below the official guide's 1 µL lower limit. Keep the documented 1 µL limit unless Opentrons explicitly qualifies a lower range for the exact hardware and tips; the property alone is not evidence of accuracy below 1 µL. Mode changes also reset flow rates, so apply any validated custom rate after changing mode.

Raw lines 141 to 164
165### Relative and absolute rates
167`rate=` multiplies the configured flow rate:
169```python
170pipette.aspirate(50, source, rate=0.5)
171```
173Supported modern APIs also accept absolute flow-rate arguments:
175```python
176pipette.aspirate(50, source, flow_rate=25)
177```
179Use one form per action. Absolute units are µL/s. Establish values through
180liquid-specific testing rather than copying another pipette's settings.

Relative and absolute rates

rate= multiplies the configured flow rate:

pipette.aspirate(50, source, rate=0.5)

Supported modern APIs also accept absolute flow-rate arguments:

pipette.aspirate(50, source, flow_rate=25)

Use one form per action. Absolute units are µL/s. Establish values through liquid-specific testing rather than copying another pipette's settings.

Raw lines 165 to 181
182### Positions
184```python
185source.bottom(z=1)
186source.top(z=-2)
187destination.center()
188```
190- Bottom aspiration reduces residual volume but increases collision and pellet
191 disturbance risk.
192- Top or near-top dispensing can reduce contact contamination but may splash.
193- Side offsets can reduce foaming but require known well geometry.
194- `touch_tip()` can be unsafe in large wells and reservoirs; API 2.28+ rejects
195 certain large-space uses.

Positions

source.bottom(z=1)
source.top(z=-2)
destination.center()
  • Bottom aspiration reduces residual volume but increases collision and pellet disturbance risk.
  • Top or near-top dispensing can reduce contact contamination but may splash.
  • Side offsets can reduce foaming but require known well geometry.
  • touch_tip() can be unsafe in large wells and reservoirs; API 2.28+ rejects certain large-space uses.
Raw lines 182 to 196
197### Air gaps and push out
199Air gaps can reduce dripping but occupy pipette capacity:
201```python
202pipette.aspirate(80, source)
203pipette.air_gap(10)
204pipette.dispense(90, destination)
205```
207The total liquid plus air must fit the pipette. Use `push_out` to move the
208plunger a small extra amount after dispensing:
210```python
211pipette.dispense(80, destination, push_out=5)
212```
214Use blowout for a larger purge. Avoid blowing into liquid when aerosols,
215bubbles, or cross-contamination matter.

Air gaps and push out

Air gaps can reduce dripping but occupy pipette capacity:

pipette.aspirate(80, source)
pipette.air_gap(10)
pipette.dispense(90, destination)

The total liquid plus air must fit the pipette. Use push_out to move the plunger a small extra amount after dispensing:

pipette.dispense(80, destination, push_out=5)

Use blowout for a larger purge. Avoid blowing into liquid when aerosols, bubbles, or cross-contamination matter.

Raw lines 197 to 216
217## Mixing
219Standard mixing:
221```python
222pipette.mix(
223 repetitions=5,
224 volume=40,
225 location=plate["A1"].bottom(z=1),
226 aspirate_flow_rate=20,
227 dispense_flow_rate=30,
228 final_push_out=5,
230```
232Choose a mix volume below the available liquid volume and pipette maximum.
233Account for pellets, beads, cells, foaming, and plate seals.
235API 2.27 adds dynamic mixing:
237```python
238well = plate["A1"]
239pipette.dynamic_mix(
240 aspirate_start_location=well.bottom(z=1),
241 aspirate_end_location=well.bottom(z=4),
242 dispense_start_location=well.bottom(z=4),
243 dispense_end_location=well.bottom(z=1),
244 repetitions=3,
245 volume=50,
247```
249Dynamic movement is geometry-sensitive. Simulate, inspect the path, and dry-run
250with the exact labware before using it on samples.

Mixing

Standard mixing:

pipette.mix(
    repetitions=5,
    volume=40,
    location=plate["A1"].bottom(z=1),
    aspirate_flow_rate=20,
    dispense_flow_rate=30,
    final_push_out=5,
)

Choose a mix volume below the available liquid volume and pipette maximum. Account for pellets, beads, cells, foaming, and plate seals.

API 2.27 adds dynamic mixing:

well = plate["A1"]
pipette.dynamic_mix(
    aspirate_start_location=well.bottom(z=1),
    aspirate_end_location=well.bottom(z=4),
    dispense_start_location=well.bottom(z=4),
    dispense_end_location=well.bottom(z=1),
    repetitions=3,
    volume=50,
)

Dynamic movement is geometry-sensitive. Simulate, inspect the path, and dry-run with the exact labware before using it on samples.

Raw lines 217 to 251
252## Dynamic Aspiration and Dispensing
254API 2.27 can move between two locations during one plunger action:
256```python
257pipette.aspirate(
258 volume=100,
259 location=well.bottom(z=1),
260 end_location=well.bottom(z=5),
261 movement_delay=1,
263```
265This can follow a changing meniscus or sweep through a liquid column. It does
266not automatically prove that the declared liquid volume or geometry is
267correct.

Dynamic Aspiration and Dispensing

API 2.27 can move between two locations during one plunger action:

pipette.aspirate(
    volume=100,
    location=well.bottom(z=1),
    end_location=well.bottom(z=5),
    movement_delay=1,
)

This can follow a changing meniscus or sweep through a liquid column. It does not automatically prove that the declared liquid volume or geometry is correct.

Raw lines 252 to 268
269## Liquid Definitions and Meniscus
271Declare setup volumes with labware-level methods:
273```python
274buffer = protocol.define_liquid(
275 name="Buffer",
276 description="Assay buffer",
277 display_color="#1F77B4",
279reservoir.load_liquid(
280 wells=["A1"],
281 volume=12_000,
282 liquid=buffer,
284```
286API 2.23 adds `well.meniscus()`:
288```python
289start_surface = reservoir["A1"].meniscus(z=-1, target="start")
290end_surface = reservoir["A1"].meniscus(z=-1, target="end")
291```
293The calculated surface depends on liquid volume and labware geometry. With
294dynamic aspiration or dispensing, `target="start"` and `target="end"` can
295represent the expected surface at either end of the operation.
297API 2.30 permits a start-only aspiration without an end location:
299```python
300pipette.aspirate(50, reservoir["A1"].meniscus(z=-1, target="start"))
301```
303At API 2.29 and lower, that form raises an error; use the documented end-target
304or dynamic start/end form instead. This 2.30 fix does not add OT-2 support.
306Do not rely on meniscus targeting until declared volumes, well geometry, and
307liquid-level behavior have been checked on the robot.

Liquid Definitions and Meniscus

Declare setup volumes with labware-level methods:

buffer = protocol.define_liquid(
    name="Buffer",
    description="Assay buffer",
    display_color="#1F77B4",
)
reservoir.load_liquid(
    wells=["A1"],
    volume=12_000,
    liquid=buffer,
)

API 2.23 adds well.meniscus():

start_surface = reservoir["A1"].meniscus(z=-1, target="start")
end_surface = reservoir["A1"].meniscus(z=-1, target="end")

The calculated surface depends on liquid volume and labware geometry. With dynamic aspiration or dispensing, target="start" and target="end" can represent the expected surface at either end of the operation.

API 2.30 permits a start-only aspiration without an end location:

pipette.aspirate(50, reservoir["A1"].meniscus(z=-1, target="start"))

At API 2.29 and lower, that form raises an error; use the documented end-target or dynamic start/end form instead. This 2.30 fix does not add OT-2 support.

Do not rely on meniscus targeting until declared volumes, well geometry, and liquid-level behavior have been checked on the robot.

Raw lines 269 to 308
309## Liquid Presence Detection
311Flex pressure sensors support three explicit operations:
313```python
314present = pipette.detect_liquid_presence(reservoir["A1"])
315pipette.require_liquid_presence(reservoir["A1"])
316height = pipette.measure_liquid_height(reservoir["A1"])
317```
319Or enable a check before every aspiration:
321```python
322pipette = protocol.load_instrument(
323 "flex_1channel_1000",
324 "left",
325 tip_racks=[tips],
326 liquid_presence_detection=True,
328```
330Operational constraints:
332- Use a fresh, dry, empty tip.
333- Detection can add 5–50 seconds per check depending on well depth and volume.
334- An 8-channel pipette has pressure sensors only on channels 1 and 8.
335- A 96-channel pipette has pressure sensors only on channels 1 and 96.
336- A wet tip can defeat absence detection.
337- With global detection, complex-command refills may check with a wet tip.
338 Prefer building blocks that pick up a fresh tip immediately before every
339 checked aspiration.
340- Detection is not a substitute for source-volume planning.
342Use explicit checks at critical sources when global detection would add too
343much time.

Liquid Presence Detection

Flex pressure sensors support three explicit operations:

present = pipette.detect_liquid_presence(reservoir["A1"])
pipette.require_liquid_presence(reservoir["A1"])
height = pipette.measure_liquid_height(reservoir["A1"])

Or enable a check before every aspiration:

pipette = protocol.load_instrument(
    "flex_1channel_1000",
    "left",
    tip_racks=[tips],
    liquid_presence_detection=True,
)

Operational constraints:

  • Use a fresh, dry, empty tip.
  • Detection can add 5–50 seconds per check depending on well depth and volume.
  • An 8-channel pipette has pressure sensors only on channels 1 and 8.
  • A 96-channel pipette has pressure sensors only on channels 1 and 96.
  • A wet tip can defeat absence detection.
  • With global detection, complex-command refills may check with a wet tip. Prefer building blocks that pick up a fresh tip immediately before every checked aspiration.
  • Detection is not a substitute for source-volume planning.

Use explicit checks at critical sources when global detection would add too much time.

Raw lines 309 to 344
345## Partial Tip Pickup
347Supported layouts:
349| Pipette | Layout | Minimum API |
350| --- | --- | ---: |
351| Flex 96-channel | column | 2.16 |
352| Flex 96-channel | row, single | 2.20 |
353| Flex 8-channel | single, partial column | 2.20 |
354| OT-2 multi-channel | single, partial column | 2.20 |
356```python
357from opentrons.protocol_api import ALL, COLUMN
359pipette.configure_nozzle_layout(
360 style=COLUMN,
361 start="A12",
362 tip_racks=[partial_rack],
365# Partial-column operations...
367pipette.configure_nozzle_layout(
368 style=ALL,
369 tip_racks=[full_rack],
371```
373Critical rules:
375- `configure_nozzle_layout()` resets `pipette.tip_racks`.
376- Use separate rack variables for full and partial pickup.
377- Full-rack Flex 96-channel pickup requires an adapter.
378- Partial Flex 96-channel pickup must not use the adapter.
379- Never pass a pickup or well location that leaves active nozzles hanging
380 outside the rack or labware.
381- Deck-edge reach depends on layout and starting nozzle.
382- Prefer the 96-channel pipette's column-12 nozzles for column pickup when deck
383 reach allows.
384- Simulate and perform a tip-only dry run before first physical use.
386See the official
387[Partial Tip Pickup guide](https://docs.opentrons.com/python-api/pipettes/partial-tip-pickup/)
388for layout-specific target-well rules.

Partial Tip Pickup

Supported layouts:

PipetteLayoutMinimum API
Flex 96-channelcolumn2.16
Flex 96-channelrow, single2.20
Flex 8-channelsingle, partial column2.20
OT-2 multi-channelsingle, partial column2.20
from opentrons.protocol_api import ALL, COLUMN

pipette.configure_nozzle_layout(
    style=COLUMN,
    start="A12",
    tip_racks=[partial_rack],
)

# Partial-column operations...

pipette.configure_nozzle_layout(
    style=ALL,
    tip_racks=[full_rack],
)

Critical rules:

  • configure_nozzle_layout() resets pipette.tip_racks.
  • Use separate rack variables for full and partial pickup.
  • Full-rack Flex 96-channel pickup requires an adapter.
  • Partial Flex 96-channel pickup must not use the adapter.
  • Never pass a pickup or well location that leaves active nozzles hanging outside the rack or labware.
  • Deck-edge reach depends on layout and starting nozzle.
  • Prefer the 96-channel pipette's column-12 nozzles for column pickup when deck reach allows.
  • Simulate and perform a tip-only dry run before first physical use.

See the official Partial Tip Pickup guide for layout-specific target-well rules.

Raw lines 345 to 389
390## Serial Dilution Pattern
392For a full 96-well plate and an 8-channel pipette:
3941. Preload stock in column 1.
3952. Add diluent to columns 2–12.
3963. Transfer from column 1 to 2, mix, then 2 to 3, and so on.
3974. Use a fresh tip set at each dilution step unless the validated method says
398 otherwise.
3995. Remove one transfer volume from column 12 if equal final volumes are needed.
401The bundled template uses 13 sets of eight tips (104 individual tips), draws
4028,800 µL diluent from the 12,000 µL setup volume, and collects 800 µL final
403liquid waste in initially empty reservoir A12. That reserve still requires
404validation against the source's dead volume. Waste must remain separate from
405diluent; the trash bin receives tips.
407Referencing A-row wells addresses full columns:
409```python
410pipette.transfer(
411 100,
412 source=plate.rows()[0][0:11],
413 dest=plate.rows()[0][1:12],
414 mix_after=(3, 50),
415 new_tip="always",
417```
419Verify that the tip budget covers 11 serial steps plus diluent addition and
420final-volume removal.

Serial Dilution Pattern

For a full 96-well plate and an 8-channel pipette:

  1. Preload stock in column 1.
  2. Add diluent to columns 2–12.
  3. Transfer from column 1 to 2, mix, then 2 to 3, and so on.
  4. Use a fresh tip set at each dilution step unless the validated method says otherwise.
  5. Remove one transfer volume from column 12 if equal final volumes are needed.

The bundled template uses 13 sets of eight tips (104 individual tips), draws 8,800 µL diluent from the 12,000 µL setup volume, and collects 800 µL final liquid waste in initially empty reservoir A12. That reserve still requires validation against the source's dead volume. Waste must remain separate from diluent; the trash bin receives tips.

Referencing A-row wells addresses full columns:

pipette.transfer(
    100,
    source=plate.rows()[0][0:11],
    dest=plate.rows()[0][1:12],
    mix_after=(3, 50),
    new_tip="always",
)

Verify that the tip budget covers 11 serial steps plus diluent addition and final-volume removal.

Raw lines 390 to 421
422## Final Liquid-Handling Review
424- Every volume is within pipette and tip range.
425- Air plus liquid never exceeds capacity.
426- Sources include dead volume and disposal volume.
427- Destinations remain below capacity at every intermediate step.
428- Mix volume is physically available.
429- Positions do not contact the well bottom or pellet.
430- Tip policy matches contamination boundaries.
431- Multi-channel well references match the active nozzle layout.
432- Liquid sensing uses fresh, dry tips.
433- Simulation expansion matches the intended command order.
434- Liquid-specific behavior has been checked in a dry run.

Final Liquid-Handling Review

  • Every volume is within pipette and tip range.
  • Air plus liquid never exceeds capacity.
  • Sources include dead volume and disposal volume.
  • Destinations remain below capacity at every intermediate step.
  • Mix volume is physically available.
  • Positions do not contact the well bottom or pellet.
  • Tip policy matches contamination boundaries.
  • Multi-channel well references match the active nozzle layout.
  • Liquid sensing uses fresh, dry tips.
  • Simulation expansion matches the intended command order.
  • Liquid-specific behavior has been checked in a dry run.
Raw lines 422 to 434