Added details on Datashader speedups

add speed up demonstration of datashader
scverse · Oct 25, 2024 · a08575f · a08575f
2 parents 5b2c978 + 7588c33
commit a08575f
Show file tree

Hide file tree

Showing 3 changed files with 532 additions and 91 deletions.
diff --git a/notebooks/examples/models1.ipynb b/notebooks/examples/models1.ipynb
@@ -15,13 +15,13 @@
    "source": [
     "The `spatialdata` framework has three ways to construct `SpatialData` objects:\n",
     "\n",
-    "1. You can read a `SpatialData` object that has already been saved to `.zarr` in the SpatialData Zarr format.\n",
-    "    1. From disk.\n",
-    "    2. From the cloud.\n",
-    "2. You can use the reader functions from `spatialdata-io`.\n",
-    "3. You can construct a `SpatialData` object from scratch using our Python `spatialdata` APIs.\n",
-    "    1. Using the `SpatialData` class.\n",
-    "    2. Extending it with the Incremental IO APIs.\n",
+    " * You can read a `SpatialData` object that has already been saved to `.zarr` in the SpatialData Zarr format ...\n",
+    "     * ... from disk.\n",
+    "     * ... from the cloud.\n",
+    " * You can use the reader functions from `spatialdata-io`.\n",
+    " * You can construct a `SpatialData` object from scratch using our Python `spatialdata` APIs ...\n",
+    "     * ... using the `SpatialData` class.\n",
+    "     * ... by extending it with the Incremental IO APIs.\n",
     "\n",
     "This tutorial is divided into two parts. The first part (this notebook) will discuss all of the above. The second part will discuss how to consuct the basic components of a SpatialData object (images, labels, points, shapes, tables)."
    ]

diff --git a/notebooks/examples/speed_up_illustration.ipynb b/notebooks/examples/speed_up_illustration.ipynb
diff --git a/notebooks/examples/transformations.ipynb b/notebooks/examples/transformations.ipynb
@@ -774,13 +774,13 @@
    "id": "df398f31-0d14-414a-ab50-9a801c07f63b",
    "metadata": {},
    "source": [
-    "# Caveats!\n",
+    "## Caveats!\n",
     "There are three important clarifications to make to avoid sources of confusion. The first 2 are for all users, the 3rd is more technical and may be skipped.\n",
     "\n",
-    "## Known bug: pixel-perfectedness\n",
+    "### Known bug: pixel-perfectedness\n",
     "When using APIs such as `transform()`, `rasterize()` and `transform_to_data_extent()` (all shown below), we may get a [misalignment of half-pixel magnitude](https://github.com/scverse/spatialdata/issues/165). We identified the root of the problem and we will make a fix in one of the next releases.\n",
     "\n",
-    "## Coordinate transformations vs `transform()`\n",
+    "### Coordinate transformations vs `transform()`\n",
     "\n",
     "When adding/remove coordinate transformations as we showed above, we are not modifying the actual data, but just some lightweight metadata. For instance, if you add a rotation transformation to an image, the image data will not get rotated. If you want, you can call the {func}`spatialdata.transform()` function to actually create a new image object with the rotated data.\n",
     "\n",
@@ -1320,7 +1320,7 @@
    "id": "c383374d-e3b0-4832-8e6e-0d0c5892b687",
    "metadata": {},
    "source": [
-    "# Technical topics"
+    "## Technical topics"
    ]
   },
   {