Remove Tecan-Specific Attributes from resource model

[rickwierenga]

We should remove Tecan-specific fields from TecanResource, TecanPlate, and TecanTipRack to move toward a unified, model-agnostic resource system. The idea is that the base resource model should contain enough information to support all operations.

To Remove:

From TecanResource:

• off_x
• off_y

From TecanPlate and TecanTipRack, there are z-attributes. They are explained here: https://www.tecan.com/knowledge-portal/how-to-teach-the-z-values-in-freedom-evoware

• z_travel: "Height at which the tip moves between positions within a rack.". In PLR should be: "hardcode" this, make it a user-defined fixed value.
• z_start: "Height at which liquid detection is activated.". In PLR should be: container.get_absolute_position(z="cavity_bottom") + clld_search_height
• z_dispense: "Height at which liquid is dispensed.". In PLR should be: container.get_absolute_position(z="cavity_bottom") + liquid_height
• z_max: "Lowest position of the well/tube in the rack, and the lowest possible position the tip is allowed to reach.". In PLR should be: container.get_absolute_position(z="cavity_bottom")
• area

From TecanPlateCarrier:

• roma_x
• roma_y
• roma_z_travel
• roma_z_safe
• roma_z_end

From TecanTipCarrier

• no attributes, just class itself

These fields are redundant and will be phased out.

After all are done, we will get rid of Tecan* classes.

also see this old but loosely related thread: https://labautomation.io/t/pylabrobot-tecan-error-in-adding-labware-to-carrier/2987

[rickwierenga]

thanks for working on this and all the information!

sorry to be that guy, but would you mind opening new issues for every individual topic (area/off{x,y}, etc). i fear this thread would become too long and disorganized if we have all these topics here. i think this thread should just be used to track overall progress of de-tecanizing these resources.