Remote execution path for zonal_anomaly + fix remote remap serialization#72
Merged
Conversation
Closes the last local-only compute operation so HPC routing is uniform across the tool surface (#66). - remote_calculate_zonal_anomaly: self-contained worker function - calculate_zonal_anomaly: use_remote/endpoint with local fallback - frontdoor: thread use_remote/endpoint for the zonal_anomaly op - fix: inline dataset/grid opening in remote remap functions — the shared _remote_open_* module helpers did not survive AllCodeStrategies serialization, which had left the remote remap paths non-functional - docs: tools.md now states all compute + remapping ops accept use_remote - tests: remote dispatch + clear-error fallback for zonal_anomaly Verified live on Chrysalis: remote zonal_anomaly and remote remap_variable return results bit-identical to local.
This was referenced Jul 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a remote (HPC) execution path for
zonal_anomaly— the last computeoperation that was still local-only — so HPC routing is uniform across the whole
tool surface. Addresses the design item in #66.
Also fixes a latent serialization bug in the remote remapping functions
introduced in #71.
What changed
remote_calculate_zonal_anomaly— new self-contained worker functionreturning compact summary statistics (not the full per-face field).
calculate_zonal_anomaly— now acceptsuse_remote/endpointwith thestandard local-fallback semantics; raises a clear error for remote-only paths
when the endpoint is unavailable.
run_analysis— threadsuse_remote/endpointfor thezonal_anomalyoperation.
remote_remap_variable,remote_regrid_dataset,remote_remap_to_rectilinear) called module-level_remote_open_*helpers that do not surviveAllCodeStrategiesserialization, so those remote paths raised
NameErroron the worker. Theopen logic is now inlined (or defined as inner functions) in each remote
function, and the dead module helpers removed.
including
zonal_anomaly— acceptuse_remote.Testing
uv run pre-commit run— all hooks pass (ruff, isort, format, mypy).uv run pytest tests/ --ignore=tests/test_remote_agent.py— 336 passed(2 new: remote dispatch + clear-error fallback for zonal_anomaly).
zonal_anomalyremote result is bit-identical to the local result(
execution_venue: hpc:chrysalis, provenance recordsremote_uxarray_version).remap_variableremote now works end-to-end (previously broken by theserialization bug), result matches local.
Notes
The serialization fix also makes the remote remap paths from #71 functional for
the first time — they had never been exercised live because the endpoint was
offline when #71 merged.