Skip to content

Container: add nominal_volume, the rated working volume distinct from physical capacity - #1476

Open
sanaxr0001-tech wants to merge 1 commit into
PyLabRobot:mainfrom
sanaxr0001-tech:fm/plr-nominal-volume
Open

sanaxr0001-tech wants to merge 1 commit into
PyLabRobot:mainfrom
sanaxr0001-tech:fm/plr-nominal-volume

Conversation

@sanaxr0001-tech

Copy link
Copy Markdown
Contributor

Adds nominal_volume to Container following @BioCam's invitation in #1467. Mirrors Tip.nominal_volume (#1102): the rated working volume, distinct from physical brim-full capacity.

  • Optional; defaults to max_volume. Tracking remains bound by max_volume.
  • Serialized; existing payloads without the field still load.
  • Passed through Well, Tube, Trough, PetriDish and Trash.
  • Sets nominal_volume=200 for NEST 701011 (nest_96_wellplate_200uL_Fb), keeping max_volume=372.4.

Backward compatible: the new parameter is appended to all six constructor signatures, preserving every existing positional and keyword argument binding. No existing definition's max_volume changes.

Tests cover explicit/default values, serialization round trips, legacy payloads, the Well subclass, and complete existing positional calls for all six constructors.

Other resource definitions and the wider modelling clean-up mentioned in #1467 are left for follow-up work.

…from physical capacity

`nominal_volume` is optional and falls back to `max_volume`, mirroring `Tip`. Append it to
constructor signatures to preserve existing positional arguments. It is serialized, and payloads
without it still deserialize. `Well`, `Tube`, `Trough`, `PetriDish` and `Trash` pass it through.
`nest_96_wellplate_200uL_Fb` sets `nominal_volume=200` next to its brim-full `max_volume=372.4`.
@sanaxr0001-tech
sanaxr0001-tech requested a review from a team as a code owner October 8, 2026 08:31

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant