@rickwierenga thank you, those are some really useful updates.
In regards to stacking/nesting, I agree with @ben that simple offsets based on the labware used is likely the fastest way to execute the physical stacking.
But in regards to deck management, can theâŚ
lh.summary()
Rail Resource Type Coordinates (mm)
===============================================================================================
(3) âââ tip carrier TipCarrier (145.000, 063.000, 100.000)
â âââ tips_01 TipRack (162.900, 145.800, 131.450)
â âââ <empty>
â âââ <empty>
â âââ <empty>
â âââ <empty>
â
(15) âââ plate carrier PlateCarrier (415.000, 063.000, 100.000)
â âââ plate_01 Plate (433.000, 146.000, 187.150)
â âââ <empty>
â âââ <empty>
â âââ <empty>
â âââ <empty>
â
(32) âââ trash Trash (800.000, 190.600, 137.100)
âŚmethodâs output be modified to incorporate stacking/nesting?
I could see the generation of new resource types called TipStack
and PlateStack
which in turn can contain the current TipRack
and Plate
types as their children, respectively.
In the end the lh.summary()
method should then return something likeâŚ
Rail Resource Type Coordinates (mm)
===============================================================================================
(3) âââ tip carrier TipCarrier (145.000, 063.000, 100.000)
â âââ tips_01 TipRack (162.900, 145.800, 131.450)
â âââ NTR_300_clear TipStack (162.900, 145.800, 131.450)
â â âââ tips_02a TipRack (162.900, 231.800, 131.450)
â â âââ tips_02b TipRack (162.900, 231.800, 262.900)
â â âââ tips_02c TipRack (162.900, 231.800, 394.350)
â âââ <empty>
â âââ <empty>
â âââ <empty>
â
(15) âââ plate carrier PlateCarrier (415.000, 063.000, 100.000)
â âââ plate_01 Plate (433.000, 146.000, 187.150)
â âââ <empty>
â âââ <empty>
â âââ <empty>
â âââ <empty>
â
(32) âââ trash Trash (800.000, 190.600, 137.100)
The aim is to allow (1) simplified plate hotel processing, and (2) increased tip capacity/deck enabled by a streamlined management of nested labware.