Running Locally#
Running Locally
Local execution exists only where the specific application and workflow support it — it is not a universal CryoStack mode.
ICESEE offers a Local execution mode: a selected workflow runs as a Python subprocess on the application host, without a scheduler or cloud resource. This is the fastest path for small examples and interactive development — see ICESEE’s Local Mode for scope and limits.
CryoLauncher has no Local execution mode for a standalone ISSM or Icepack run — its execution paths are Remote and Cloud.
Frozen Legacies and LIVIST are not organized around Local/Remote/ Cloud execution modes at all; see Applications & Workflows.
Do not assume a workflow that lacks a Local option is somehow incomplete — some scientific workflows (an MPI-parallel ISSM solve, for example) are not meaningfully “local” in the first place.