Montage GCP/local: portable reference profile

This profile preserves the complete original Montage 050d computation: 58 activities, 138 file handoffs, twelve FITS observations, three 1800×1800 mosaics and four PNG previews. All activities execute through local Docker.

The measured reference execution is shared with the Montage 050 local showcase because the executable DAG, input data, image filesystem and runtime configuration are identical. This is explicitly a shared reference capture, not a second independent experiment and not evidence of a GCP execution. The public capture preserves its original execution identifiers.

The original cloud/local configuration is retained as a separate historical version for users who configure GCP resources. Its four on-demand worker placements and predicted values are not measured by the local reference run.

Inputs, outputs and execution

The pinned image includes the twelve original FITS observations and Montage executables. Use the source image's upstream dataset terms before redistributing the input observations. Configure local Docker using the companion environment, scope and topology definitions, import the public local-profile URI, create a plan and execute. On Apple Silicon the image requires amd64 emulation.

./prepare.sh && ./run.sh && ./validate.sh executes and validates the same local profile with Go and Docker. This is a full scientific workload, not a short timing simulation. The generated FITS and PNG files are validated before publication.

Public Hub version and measured execution

Open this workflow and its results · Documentation

Import into AkôFlow Desktop

Create workflow → Import from Hub → paste this immutable URI:

akoflow://hub/publications/bae34aba-fbc6-423f-8921-6e4dc5ea5d4a/versions/2

The URI imports the workflow definition. Build or pull the public image and register the companion environment.yaml, scope.yaml, and topology.yaml from this source bundle before planning a local execution. No hosted account, GPU or cloud capacity is required for this CPU profile.

Image: ghcr.io/uffescience/akoflow-examples/montage-050-local@sha256:26b060b83b990557ea86ab40503cc8f17ab6016b5973e7e6f9201100a96440c9.

Actual homeserver results

Run montage-050-local-local-79df14ee2e-run-20261115t052715.750879194 completed 58/58 activities in 3196.8059842586517 seconds. These are measured Docker-backed computations, not simulated timing. The captured manual plan uses placeholder predicted timings; those predictions are not benchmark measurements. Use the observed execution metrics for performance analysis. Cost is the configured local compute cost and excludes electricity and hardware.

Download the native experiment capture. The Hub Results tab includes the same plan, attempts, metrics and logs.

Inputs and outputs

Input fixtures and their generation code are in this bundle's data/ and scripts/ directories; inspect them together with the workflow definition and bundle configuration for profile assumptions. Fixtures are generated by the included code unless a bundle identifies an upstream dataset. No repository-wide LICENSE file is currently present: inspect the bundle and upstream terms before redistributing source or data; publication here does not grant additional rights. Outputs expected from this workflow:

• 1-mosaic.fits
• 2-mosaic.fits
• 3-mosaic.fits
• 1-mosaic.png
• 2-mosaic.png
• 3-mosaic.png
• mosaic-color.png

Download the actual validated output files.

Images from this validated execution

Illustrated walkthrough

The following reference screenshots come from the documentation walkthrough. The current measured run is recorded separately above.

workflow

The captured run used local alias ghcr.io/uffescience/akoflow-examples/montage-050-local:local-5781d026f51ba438. Its complete filesystem layers, runtime configuration, OS and architecture were compared with the public digest above and match; the recorded capture preserves the original image reference.