You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when write() is called, the data is re-read to be made lazy. We have to prevent this because it leads to undesired behavior when one wants to overwrite the data (i.e. data that was in memory should remain in-memory unless the user explicitly wants to load it lazily).
In doing this we need to warn the user that the in-memory object may be not performant (especially relevant if calling Interactive() to the output of functions like xenium()). So we should add a check that controls if the data is lazy and backed by a .zarr or .parquet storage (we already have the code for that (see the tests test_io_and_lazy_loading_points() and test_io_and_lazy_loading_raster()), if it is not backed, then when calling Interactive() we should display this warning.
The text was updated successfully, but these errors were encountered:
write()
is called, the data is re-read to be made lazy. We have to prevent this because it leads to undesired behavior when one wants to overwrite the data (i.e. data that was in memory should remain in-memory unless the user explicitly wants to load it lazily).Interactive()
to the output of functions likexenium()
). So we should add a check that controls if the data is lazy and backed by a.zarr
or.parquet
storage (we already have the code for that (see the teststest_io_and_lazy_loading_points()
andtest_io_and_lazy_loading_raster()
), if it is not backed, then when callingInteractive()
we should display this warning.The text was updated successfully, but these errors were encountered: