Save and write SpatialExperiment's in Python
Introduction
The dolomite-spatial package is the Python counterpart to the alabaster.spatial R package,
providing methods for saving/reading SpatialExperiment objects within the dolomite framework.
Quick start
Let's mock up a SpatialExperiment that contains reduced dimensions and alternative experiments,
from spatialexperiment import SpatialExperiment, construct_spatial_image_class
import biocframe
import numpy as np
spe = SpatialExperiment(
assays={"counts": np.random.rand(1000, 200)},
row_data=biocframe.BiocFrame(
{"foo": np.random.rand(1000), "bar": np.random.rand(1000)}
),
column_data=biocframe.BiocFrame(
{"whee": np.random.rand(200), "stuff": np.random.rand(200), "sample_id": ["sample_1", "sample_2"] * 100}
),
reduced_dims={"tsnooch": np.random.rand(200, 4)},
spatial_coords = np.array(
[
np.random.uniform(low=0.0, high=100.0, size=200),
np.random.uniform(low=0.0, high=100.0, size=200)
]
).transpose(),
img_data = biocframe.BiocFrame({
"sample_id": ["sample_1", "sample_1", "sample_2"],
"image_id": ["aurora", "dice", "desert"],
"data": [
construct_spatial_image_class("biocpy/spatialexperiment/tests/images/sample_image1.jpg"),
construct_spatial_image_class("biocpy/spatialexperiment/tests/images/sample_image2.png"),
construct_spatial_image_class("biocpy/spatialexperiment/tests/images/sample_image3.jpg"),
],
"scale_factor": [1, 1, 1],
})
)
print(spe)
Now we can save it:
from dolomite_base import save_object
import dolomite_spatial
import os
from tempfile import mkdtemp
path = os.path.join(mkdtemp(), "test")
save_object(spe, path)
And load it again, e,g., in a new session:
from dolomite_base import read_object
roundtrip = read_object(path)
print(roundtrip)
## output
class: SpatialExperiment
dimensions: (1000, 200)
assays(1): ['counts']
row_data columns(2): ['foo', 'bar']
row_names(0):
column_data columns(3): ['whee', 'stuff', 'sample_id']
column_names(0):
main_experiment_name:
reduced_dims(1): ['tsnooch']
alternative_experiments(0): []
row_pairs(0): []
column_pairs(0): []
metadata(0):
spatial_coords columns(0): []
img_data columns(4): ['sample_id', 'image_id', 'data', 'scale_factor']
Note
This project has been set up using BiocSetup and PyScaffold.
Metadata
Release files for dolomite-spatial 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dolomite_spatial-0.1.1.tar.gz | 964.5 kB | With provenance | Details for dolomite_spatial-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dolomite_spatial-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for dolomite_spatial-0.1.1-py3-none-any.whl |
Total release size: 972.2 kB
Release files / dolomite_spatial-0.1.1.tar.gz
| Download URL | dolomite_spatial-0.1.1.tar.gz |
|---|---|
| Size | 964.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
04648f40244645d15dc5f5005931183aaa63df2da39809f8147603f7242a334b
|
|
BLAKE2b-256 checksum How to use checksums |
87e4a975ade9e65d4356d88109c3cad8fe4b59d79826c85de380bcf97b06f21c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 May 14, 2025.
Transparency logRelease files / dolomite_spatial-0.1.1-py3-none-any.whl
| Download URL | dolomite_spatial-0.1.1-py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6a242eb7969c04d4b1be98bf953c9604e455b57dc8453d922c17852c5db319e1
|
|
BLAKE2b-256 checksum How to use checksums |
fd18c9678d74f6fccb6549bd6de83c9359c021b3c6711b39b6f767db2f5eb273
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 May 14, 2025.
Transparency logSecurity for dolomite-spatial 0.1.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for dolomite_spatial-0.1.1.tar.gz
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 May 14, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.