Skip to main content

labware

Microplate and dish definitions for software: outer footprint, well geometry, skirt, material, and the vendor drawing each dimension came from.

Browse them in 3D: https://docs.ramonaoptics.com/tools/labware_viewer.html

Install

pip install labware

or

conda install -c conda-forge labware

Example

from labware import load_labware

plates = load_labware()
plate = plates["SBS_96_well_plate"]

print(plate.name)  # SBS 96 well
print(plate.well_dimensions.rows, plate.well_dimensions.columns)  # 8 12
print(plate.well_dimensions.pitch)  # 0.009, in meters

Layout

  • labware/definitions/ holds one JSON file per part. The file name, without .json, is the key load_labware() returns it under.
  • labware/schema.py is the pydantic model every definition is validated against.
  • labware/labware.v1.schema.json is that model published as a JSON schema. Each definition names it in its $schema key.

Releasing

Uploads to PyPI are automatic, and the version comes from the git tag, so there is no version number to edit in the source.

A merge to main that changes the package is released on its own: the pypi workflow runs the tests, creates the tag and a GitHub release, and publishes.

  • If anything in labware/ other than a JSON file changed, such as the schema model or the loader, the minor version goes up.
  • Otherwise, if a JSON file in labware/ was added, changed or deleted, which is what a new or corrected plate definition is, the patch version goes up.
  • A merge that only touches files outside labware/, such as this README, the tests or the CI, is not released.

A major version is always made by hand.

To release by hand, create the tag from the GitHub web interface:

  1. Open https://github.com/ramonaoptics/labware/releases/new
  2. Under "Choose a tag", type the new version with a leading v, for example v0.1.1, and pick "Create new tag on publish".
  3. Leave the target as main, click "Generate release notes", then "Publish release".

The pypi workflow then builds the sdist and wheel and publishes them, and labware.__version__ in the installed package reports that same version.

Metadata

Release files for labware 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for labware 0.2.0
File Size Uploaded
labware-0.2.0.tar.gz 86.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for labware 0.2.0
File Interpreter ABI Platform
labware-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 275.6 kB

Release files / labware-0.2.0.tar.gz

Download URL labware-0.2.0.tar.gz
Size 86.4 kB
Tags Source
SHA-256 checksum
How to use checksums
d852679f96b2f03276d9b19793049d2cd08426cd2783edadb57c9db4776cfd0d
BLAKE2b-256 checksum
How to use checksums
ca7161139337de058f5005e8e0b40988056290506de1b14d6ea5e2ee2ea2d4bd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.

Transparency log

Release files / labware-0.2.0-py3-none-any.whl

Download URL labware-0.2.0-py3-none-any.whl
Size 189.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e795997389cf595141d55d5f96af4ea2de4411cbb83608978285a052417e84b2
BLAKE2b-256 checksum
How to use checksums
8633830baa72dbe2fed641c278cccc1966021df643a9f85b821ac681509e7b2d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.

Transparency log

Release history Release notifications | RSS feed

0.2.1

2 release files

This release

0.2.0 This release

2 release files

0.1.7

2 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page