Skip to content

This page describes Revolution release 3.1.0.

Search these docs, or ask Revo a question — answers link the pages they came from.

Labware pick lists


A labware pick list is the list of plates a Transfer takes from, one plate each time the step runs. Use one when a run should work on particular plates, chosen by barcode, rather than whatever is next in a store.

In the Transfer step:

  1. Set Source Type to Labware Pick List.
  2. Put the pick list in Source Location (see below).
  3. Set Destination Type and Destination Location as usual. A pick list is only ever a source, so Destination Type does not offer it.

Each time the step runs it takes the next plate on the list, in the order listed. Run the step once per plate, for example in a loop that runs as many times as the list has barcodes.

Source Location takes one of three things.

A JSON list of the barcodes, in the order to take them:

["plt-005", "plt-002", "plt-004"]

Use this when the plates are known when the schedule is written.

A single ${parameter}, for example ${dynamicPickList}, whose value is a JSON list of barcodes when the transfer runs. Declare the parameter on the schedule as a String (see Schedule parameters), then set it when the run starts or from a Python step earlier in the schedule:

import json
import revo
barcodes = ["plt-003", "plt-001"] # for example, read from a LIMS or a file
revo.parameters["dynamicPickList"] = json.dumps(barcodes)

Use json.dumps, so the value is valid JSON. See Schedule parameters in Python.

Left empty, the transfer takes from the run’s own order list, as an order-based run always has. In any other run an empty Source fails the transfer and nothing moves, so the schedule editor marks an empty Source as an error.

The schedule editor checks a written list as you type, and the run checks a list held in a parameter when the transfer runs. A list must:

  • be strict JSON: a list in square brackets, barcodes in double quotes, no trailing comma;
  • have at least one barcode;
  • have no blank barcode, and no barcode with a control character or ${ in it;
  • name each barcode only once.

A list written in the step is used as written: a ${...} inside it is not replaced.

The transfer fails, and no plate on the list moves, when:

  • the list cannot be read, for example a parameter that holds plt-001 rather than ["plt-001"]. The run never falls back to its own order list instead;
  • a barcode is not known to Revolution, or the plate’s location is not known;
  • a barcode is on the list twice;
  • a plate on the list is already on a pick list that another run is still using. Two runs never take the same plate.

The same rule runs the other way: an order run does not start while a plate on its order is on a JSON pick list another run is still using.

The first time a run’s transfer uses a list, Revolution makes that run’s working copy of it. Later transfers in the same run that name the same list carry on down that copy rather than starting again, including transfers in child schedules the run starts. The copy is removed when the run ends, however it ends, so the plates are free for another run.