Applications & Workflows#
Applications & Workflows
CryoStack's principal applications share platform services but keep their own interfaces. Do not expect one application's controls to predict another's.
CryoLauncher — ISSM and Icepack#
CryoLauncher configures and runs ISSM and Icepack. Its configuration experiences are Basic (curated, solver-aware parameters), Advanced (the full working copy), and Auto-config · Beta (natural-language proposals over the same configuration state) — see the CryoLauncher User Manual and Getting Started.
CryoLauncher’s execution paths are Remote and Cloud; it has no Local execution mode for a standalone ISSM or Icepack run. ISSM’s container workflow uses MATLAB and requires a license; Icepack does not.
ICESEE — ensemble data assimilation#
ICESEE organizes execution as Local, Remote, or Cloud, with Auto-config · Beta available alongside that organization — not a Basic/Advanced split. See the ICESEE User Manual and Getting Started.
ICESEE can wrap ISSM, Icepack, or a synthetic model such as Lorenz-96 as its forecast model. Dependencies follow that choice: an ISSM-based workflow requires MATLAB, Icepack and Lorenz-96 do not — ICESEE itself does not generally require MATLAB.
Frozen Legacies — historical radar catalog#
Frozen Legacies discovers, catalogs, and interprets historical Antarctic radar observations. It is not organized around Local/Remote/Cloud execution modes — see its own Getting Started and User Manual.
LIVIST — englacial temperature products#
LIVIST explores Antarctic englacial-temperature products inferred from radar and constrained by boreholes, through its own frontend served under the CryoStack deployment registry. It does not use CryoLauncher/ICESEE execution-mode concepts — see Open LIVIST and its own User Manual.
Control Center — administrative infrastructure#
Control Center is CryoStack’s administrative/operations tooling (roles, deployment status, account administration). It is not one of the principal scientific applications above.