search

scverse / spatialdata

An open and interoperable data framework for spatial omics data
https://spatialdata.scverse.org/
BSD 3-Clause "New" or "Revised" License
236 stars 45 forks source link

Syncing in-memory changes to disk and backing #126

Closed LucaMarconato closed 9 months ago

LucaMarconato commented 1 year ago

When we modify in-memory an object that is not backed, we need to write it to disk in order to update the changes. For backed objects we have to check if changes are written to disk immediately (as it happens with h5py), or not.

Backed Discussion In-memory changes are written immediately?
Images/Labels yes NA TODO check
Points yes NA TODO check
Polygons no https://github.com/scverse/spatialdata/issues/122 NA
Shapes no https://github.com/scverse/spatialdata/issues/122 NA
Tables no https://github.com/scverse/anndata/issues/219 NA

We need to make this behavior clear to the user in the docs.

LucaMarconato commented 9 months ago

The change is not applied to disk as it is only reflected in the computational graph of Dask.