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
Copy file name to clipboardExpand all lines: docs/index.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,8 +16,14 @@ Please see our publication {cite}`marconatoSpatialDataOpenUniversal2024` for cit
16
16
17
17
:::{note}
18
18
With dask < 2025.2.0, users can get an error as described in [#1077](https://github.com/scverse/spatialdata/issues/1064). While we tried implementing fixes in SpatialData, it can be that
19
-
users perform operations on the `Points` data themselves and get this error. In order to prevent it, please add the following on the line before the error occurs:
20
-
`dask.config.set({"optimization.tune.active": False})`. This setting can be set to True after the line where the error occurs.
19
+
users perform operations on the `Points` data themselves and get this error. In order to prevent it, users can use a context manager we created.
20
+
21
+
```python
22
+
with disable_dask_tune_optimization() if data.npartitions >1else contextlib.nullcontext():
23
+
<your operation on points dask dataframe>
24
+
```
25
+
26
+
This will disable dask graph optimization if the dataframe has more than 1 partition and otherwise keep it enabled.
0 commit comments