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 keyload_labware()returns it under.labware/schema.pyis the pydantic model every definition is validated against.labware/labware.v1.schema.jsonis that model published as a JSON schema. Each definition names it in its$schemakey.
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:
- Open https://github.com/ramonaoptics/labware/releases/new
- Under "Choose a tag", type the new version with a leading
v, for examplev0.1.1, and pick "Create new tag on publish". - 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.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| labware-0.1.3.tar.gz | 77.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| labware-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 252.8 kB
Release files / labware-0.1.3.tar.gz
| Download URL | labware-0.1.3.tar.gz |
|---|---|
| Size | 77.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
980184e35ffcf1f672bf9bceaaa7ed8c339adb8232f755bd65130e2a62fbabce
|
|
BLAKE2b-256 checksum How to use checksums |
0d10962dbd65754b771e094d739ecf224aebb8b609150dc05853dad434e9ff9f
|
| 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 11, 2026.
Transparency logRelease files / labware-0.1.3-py3-none-any.whl
| Download URL | labware-0.1.3-py3-none-any.whl |
|---|---|
| Size | 175.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5a5aa9491da1977a343095752a4e4d3c8b7cc2e7d79115c6870d0970454a00e3
|
|
BLAKE2b-256 checksum How to use checksums |
22ed9f491c2f1445b36cf210c4f40fb899cab878325f644b8c30fa6398f1a33d
|
| 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 11, 2026.
Transparency log