Visualize Dask computations by chunk.
Install
pip install dask-progress-matrix
Quick-start
API
Use ProgressMatrix as a context manager to track Dask computations:
import dask.array as da
from dask_progress_matrix import ProgressMatrix
with ProgressMatrix(cmap="inferno"):
da.random.random((2, 128, 256), chunks=(1, 16, 16)).compute()
CLI
Track Dask computations in any Python file using the CLI. For example, using uv:
$ uvx dask-progress-matrix compute_something.py --cmap=inferno
Features
-
Terminal or Jupyter - Progress matrixes can be displayed in both terminal environments and Jupyter notebooks.
-
Modes - When a computation is complete, the
ProgressMatrixdisplays a summary with either the completed index or the elapsed time for each chunk, depending on themodeparameter. -
Data structures - Computing any Dask-backed object will display a progress matrix, including Xarray objects.
-
Dimensionality - You can track the computation of any Dask array, regardless of dimensionality. For visualization, arrays are truncated to the last two dimensions, so e.g. an array with chunks
(3, 16, 16)will be rendered as a 16 x 16 matrix where each chunk tracks the progress of 3 different computations.
Limitations
-
Distributed schedulers - Support for distributed schedulers like
dask.distributed.Clientisn't currently implemented. -
Character width - Each computation chunk is rendered with a minimum width of 2 characters, so arrays with huge numbers of chunks may render slowly or poorly.
-
Chunk shapes - All chunks are represented by squares, regardles of their shape.
FAQ
Why use a progress matrix?
This was mostly developed out of curiosity, but it has some practical debugging and tuning applications, like identifying chunks that are slow to compute.
Why does it take a long time to start doing anything?
The progress matrix only tracks terminal tasks that correspond directly to chunks in the computed output array. If your computation has a lot of intermediate tasks, you won't see any progress until those are completed.
Metadata
Release files for dask-progress-matrix 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dask_progress_matrix-0.0.1.tar.gz | 7.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dask_progress_matrix-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.0 kB
Release files / dask_progress_matrix-0.0.1.tar.gz
| Download URL | dask_progress_matrix-0.0.1.tar.gz |
|---|---|
| Size | 7.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
de192f37c7699e6170d3f5e46fe72d9b320c5c3288e359eac661812fa940f3de
|
|
BLAKE2b-256 checksum How to use checksums |
ff1d6239b36ef816aabcb36c6d67ea9942a99ab516741943ba0c10a5cb71c503
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 11, 2025.
Transparency logRelease files / dask_progress_matrix-0.0.1-py3-none-any.whl
| Download URL | dask_progress_matrix-0.0.1-py3-none-any.whl |
|---|---|
| Size | 11.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
595f373fc0d50710a74685ce1731a1371e85d8a3b25d00926c6b74183b03ca86
|
|
BLAKE2b-256 checksum How to use checksums |
321b4a4e467dfa1ab60cd1d0c24c72ba7da7cea90761513dc82290c1f038940b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 11, 2025.
Transparency log