Results & Visualization#
Results & Visualization
For CryoStack's two workflow-execution applications — CryoLauncher and ICESEE — a completed run's results can be retrieved, inspected, and visualized, though the underlying representation differs between them; see below for what each actually does. Frozen Legacies and LIVIST are their own applications with their own interaction models, not a run/results lifecycle — see Applications & Workflows.
CryoLauncher: the structured result package#
A completed CryoLauncher run (ISSM or Icepack) is exported to a transport-neutral, versioned result package (metadata, mesh geometry, field arrays, and any figures). A reader for each model’s package loads it without needing that model’s own runtime — you do not need MATLAB installed locally to inspect an ISSM result, for example.
Retrieve — Remote results are fetched over SSH/Connector; Cloud results are synchronized from S3. Both land in the same local run cache shape, for either backend or model.
Preview — inspect what solutions and fields a run actually produced.
Render — plot a field or time series on demand from the neutral package.
Download — package results and figures for offline use.
See Results, Visualization, and Downloads for the full walkthrough.
ICESEE: its own results workflow#
ICESEE currently has its own, separate results path — not the structured result package above. A completed run’s output files and any generated figures are presented directly from ICESEE’s own experiment/run-record tooling: retrieve them from the run’s Remote or Cloud location, then inspect the file listing and any generated images through ICESEE’s own Run Log and Results Preview. See Results and reports for the full walkthrough.