Search these docs, or ask Revo a question — answers link the pages they came from.
Labware names
Steps refer to labware by a Labware Name: the name of one specific item in a
run, such as SamplePlate. The labware type (for example a 96-well plate) is a
separate setting. Labware Name fields accept a
parameter reference, so the same schedule
can work on different labware from run to run.
Plates of the same type used for different jobs
Section titled “Plates of the same type used for different jobs”Give each plate its own labware name, even if they are the same type. For
example, AssayPlate and ReagentPlate can both be 96-well plates. Steps that
should only happen to one of them refer to that name. If the plates only differ
in a value, such as a reagent or volume, put the value in a parameter and start a
separate thread for each plate.
Labware Completed and Set Labware to Available
Section titled “Labware Completed and Set Labware to Available”These two steps do different jobs.
| Step | What it does |
|---|---|
| Labware Completed | Tells the scheduler this labware has finished its part of the schedule and releases anything it still claims. Its labware name is then free to use for another item in the same run, which matters in loops. The labware itself does not move. |
| Set Labware to Available | For labware that is in a store. Marks its store position as available, so later runs can take that labware. It fails if the labware is not in a store. |
Passing labware to and from a child schedule
Section titled “Passing labware to and from a child schedule”Run Schedule Thread hands labware to the child through Passed Labware, with the name each item takes in the child. The child works on the same item, not a copy. While the child has it, the parent’s name for it is released, so the parent uses that name again only once the item comes back.
- To use the labware in the parent again, list it under Returned Labware on the Join Schedule Thread step, with the name it takes back in the parent. Labware that is not returned stays with the finished child.
- With the Do Not Fork execution mode, Run Schedule Thread waits for the child and hands every passed item back under its original name, with no Join needed.
The child can receive passed labware under any labware name it uses, except names it creates itself with its own define-labware step. Run Schedule starts a separate run and passes parameter values only.