Skip to content

Commit 8f98b6f

Browse files
shoyerXarray-Beam authors
authored andcommitted
Update xarray version in docs build
PiperOrigin-RevId: 813456305
1 parent 0d2f958 commit 8f98b6f

3 files changed

Lines changed: 8 additions & 4 deletions

File tree

docs/high-level.ipynb

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -166,11 +166,15 @@
166166
},
167167
"cell_type": "markdown",
168168
"source": [
169-
"Weather/climate datasets are typically generated and stored in pancake chunks, but pencil chunks are more useful for most analytics queries, which requires large histories of weather at a single location. Intermediate \"compromise\" chunks can sometimes be a good idea, although if performance and flexibility are critical it may be worth storing multiple copies of your data in different formats. Using Zarr v3's sharding feature to group smaller chunks into shards can also help mitigate the challenges of picking an optimal chunk size.\n",
169+
"Weather/climate datasets are typically generated and stored in \"pancake\" chunks, but \"pencil\" chunks are more suitable for most analytics queries, which requires large histories of weather at small numbers of locations.\n",
170170
"\n",
171171
"Using the right chunks is *absolutely essentially* for efficient operations with Xarray-Beam and Zarr. For example, reading data from a single location across all times (a \"pencil\" query) is extremely inefficient for a dataset stored in \"pancake\" chunks -- it would require loading the entire dataset from disk!\n",
172172
"\n",
173-
"Rechunking is a fundamentally an expensive operation (it requires multiple complete reads/writes of a dataset from disk), but in Xarray-Beam it's straightforward, via {py:meth}`~xarray_beam.Dataset.rechunk`."
173+
"Rechunking is a fundamentally an expensive operation (it requires multiple complete reads/writes of a dataset from disk), but in Xarray-Beam it's straightforward, via {py:meth}`~xarray_beam.Dataset.rechunk`.\n",
174+
"\n",
175+
"```{tip}\n",
176+
"Intermediate \"compromise\" chunks can sometimes be a good idea, although if performance and flexibility are critical it may be worth storing multiple copies of your data in different formats. Using Zarr v3's sharding feature in {py:meth}`~xarray_beam.Dataset.to_zarr` to group smaller chunks into shards can also help mitigate the challenges of picking an optimal chunk size.\n",
177+
"```"
174178
]
175179
},
176180
{

docs/requirements.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,5 +14,5 @@ immutabledict==4.2.1
1414
numpy==2.2.6
1515
pandas==2.3.2
1616
pooch==1.8.2
17-
xarray==2025.9.0
17+
xarray==2025.9.1
1818
zarr==3.1.3

xarray_beam/__init__.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,4 +52,4 @@
5252
DatasetToZarr,
5353
)
5454

55-
__version__ = '0.10.0' # automatically synchronized to pyproject.toml
55+
__version__ = '0.10.1' # automatically synchronized to pyproject.toml

0 commit comments

Comments
 (0)