GEOPY-3035: Striping of data with no values running MVI with disk storage

[domfournier]

GEOPY-3035 - Striping of data with no values running MVI with disk storage

[Copilot]

Pull request overview

This PR updates the Dask-based potential-fields sensitivity (J) assembly to better support disk-backed storage workflows (per GEOPY-3035), shifting away from manual Zarr writes toward Dask Array concatenation and to_zarr.

Changes:

• Simplifies block_compute to return stacked NumPy blocks (removing the prior on-disk write helper).
• Adds distributed-client handling during linear_operator assembly.
• Writes disk-backed sensitivities via dask.array.to_zarr(...) instead of direct Zarr selection writes.

Suppressed comments (2)

simpeg/dask/potential_fields/base.py:82

• For disk-backed sensitivities, rows needs to be a list of Dask arrays (built via from_delayed) so it can be concatenated and written with .to_zarr(). Keeping the Future-based client.submit path for disk mode makes rows incompatible with dask.array.concatenate.

        if client and worker:

simpeg/dask/potential_fields/base.py:109

• When store_sensitivities == "disk", rows should be Dask arrays (from from_delayed), not distributed Futures, so this client.gather(rows) branch should be disabled in disk mode to keep the later .to_zarr() path consistent.

    if client and worker:

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[gmcga]

Seems to be working correctly!