feat(shared-data,-protocol-designer): add foundation for plate reader support in PD

[ncdiehl11]

Overview

This PR introduces plate reader to PD, still hidden behind a feature flag. Namely, it adds the ability to add plate reader to the initial deck state and fixes logic for ModuleLabel rendering for all modules. Of note, in this dev work, I discovered a bug in the plate reader's shared-data definition, in which the top-level x and y dimensions were flipped, so those values are swapped here as well.

Closes AUTH-1077

Test Plan and Hands on Testing

• create or import a Flex protocol (example)
• select slot B1 to edit hardware/labware
• verify correct modules populate, and hovering each module option produces the correctly positioned ModuleLabel on the deck
• repeat with center and right column slots, verifying that plate reader option displays properly on the right column slot
• with modules added, navigate to protocol timeline and click various module steps
• verify that ModuleLabel is correctly positioned

Screen.Recording.2024-12-18.at.8.00.30.PM.mov

Changelog

• add logic for handling plate reader addition to deck and adding compatible labware
• add logic for correct positioning of ModuleLabel for all modules in any slot position. An implication here is passing a slot prop to determine slot-specific corner offset from slot from a module's definition
• improve time complexity of DeckSetup util getModuleModelsBySlot
• fix plate reader x and y dimensions (spoke with plate reader devs to ensure this was correct)
• fix tests

Review requests

see test plan

Risk assessment

low. behind feature flag and major changes only affect UI for module labels

[jerader]

wow nice catch! there is plate reader support in the app in 8.2. it'd probably be good to post that you found this bug and swapped the values in the protocol execution slack channel so sw folks who worked on plate reader support in app/api are aware

[ncdiehl11]

Thanks! I did run this by exec/plat and they concur that it was in fact a bug. They're aware of the value swap in this PR

[jerader]

this plate isn't showing up, it might be included in the PD_DO_NOT_LIST or something

[ncdiehl11]

As far as I know, we don't permit explicit loading of the lid, because we don't treat it like a normal labware. Rather than use move labware commands, the api expects open/close lid commands, which will move the implicitly loaded lid "labware" object.

[jerader]

looks amazing, great work! A few questions and comments:

1. we aren't supporting MoaM for this launch?
2. there's that one plate that isn't showing up: opentrons_flex_lid_absorbance_plate_reader_module - is that expected?
3. great work finding that bug in the def!
4. the module tags look a lot better now. feel free to make a follow up ticket and put it in the backlog for us to further fix them in the future. but i think what you have now is sufficient

[ncdiehl11]

looks amazing, great work! A few questions and comments:

1. we aren't supporting MoaM for this launch?
2. there's that one plate that isn't showing up: opentrons_flex_lid_absorbance_plate_reader_module - is that expected?
3. great work finding that bug in the def!
4. the module tags look a lot better now. feel free to make a follow up ticket and put it in the backlog for us to further fix them in the future. but i think what you have now is sufficient

@jerader thanks for the review:

1. We totally are and I forgot to remove that check. I will do that now
2. I just spoke with exec— that lid def is never used by the public API. It is only used internally to know the dimensions of picking up the lid for the gripper. In fact, we actually should disallow loading labware initially onto the plate reader, since it will have to be removed before initializing/reading.
3. thanks!
4. thanks, I will leave for now

[jerader]

2. there's that one plate that isn't showing up: opentrons_flex_lid_absorbance_plate_reader_module - is that expected?

2. I just spoke with exec— that lid def is never used by the public API. It is only used internally to know the dimensions of picking up the lid for the gripper. In fact, we actually should disallow loading labware initially onto the plate reader, since it will have to be removed before initializing/reading.

@ncdiehl11 , cool, lets remove it from the array then? because right now it is included in the list of recommended labware