Merging TecanCarrier into Carrier

it should be possible to model all physical reality of resources in one universal model.

tecans have a very annoying issue i found out last week

there are a carrier-specific x and y-offsets when sliding a carrier into the rails

i imagine there is a little overhang on the left and/or right when sliding a resource into a rails. on hamiltons the left side of a carrier is exactly midway on the submarine, allowing having carriers snugly side by side. but i think on tecan there’s got to be a buffer and/or can’t have some carriers side by side without an empty rails. i haven’t confirmed since i don’t have an evo here but from the information this seems to be the case

if we want to have a general carrier resource model we have to add this to Carrier and set it to 0 for all hamilton carriers

just starting a discussion thread. hopefully someone can confirm exactly how this works on EVO or even provide a picture. for now it definitely works using the custom resource, but would be great to learn more and get rid of “TecanCarrier”

tracking issue for all Tecan resources: Remove Tecan-Specific Attributes from resource model · Issue #552 · PyLabRobot/pylabrobot · GitHub

1 Like

backlink to github issue: Remove Tecan parameter off x/y · Issue #580 · PyLabRobot/pylabrobot · GitHub