simulo run

Submit a Simulo app: run its @app.entrypoint (or, without one, map the flags onto the job’s own signature; –job NAME chooses among several), writing the package to disk.

usage: simulo run [--entrypoint ENTRYPOINT] [--detach] [--viewstream] [--frozen] [--strict-assets]
                  [--from JOB_REF[:best|:latest]] [--skip-preflight] [--describe]
                  [app_file]

Arguments

Argument	Description
APP_FILE (optional)	Path to the Python file declaring the simulo.App.

Options

Option	Description
--entrypoint ENTRYPOINT	Entrypoint to run when the file has more than one.
--detach	Submit a cloud job without waiting for its logs to finish (prints attach hints instead).
--viewstream	Enable the live 3D viewport stream for this cloud job (simulo view watches it once minted; no effect on a local-disk submit, which never reaches a worker). Training runs noticeably slower while streaming (roughly 4-5x, measured on a 512-environment benchmark) even with the platform’s built-in low-overhead render settings applied.
--frozen	Fail the submit if any mounted registry asset is unpinned (has no :vN), instead of resolving it to the current latest. Opt CI and release pipelines into full version explicitness — a cloud submit only (a local-disk submit resolves no assets).
--strict-assets	Treat asset warnings as errors: a mounted asset that is deprecated, or has never validated on the job’s runtime, fails the submit instead of printing a warning (cloud submit only).
--from JOB_REF[:best|:latest]	Continue this run from a finished job’s uploaded checkpoint instead of starting fresh (the default is ALWAYS a fresh run). JOB_REF is a job id, matched by exact equality — give it in full; an unambiguous id prefix (>= 4 chars, like Git) works too, but only for the legacy UUID form some jobs from before friendly identifiers still carry. The optional suffix picks the output — ‘:best’ (the default) or ‘:latest’. Applies to every job this one simulo run submits, and requires a cloud control plane (simulo login): a local-disk submit cannot continue from a checkpoint. The new job records what it continued from (simulo jobs / simulo result show it).
--skip-preflight	Bypass the pre-submit platform check entirely (a cloud submit only; a local-disk submit never calls it) — no request is made, not just ‘ignore the result’. Use this if simulo prepare/simulo run’s preflight check is wrong about your app, or the platform is unreachable and you still want to try the submit.
--describe	Print each declared job’s pre-run-known outputs (from ResumableCheckpoint / DebugOnAnomaly callbacks) and exit — submits NOTHING: no package is written, no archive is uploaded, no job is created. General-file registration is not a pre-run declaration, so it is not included.

Note

-h/--help after an app file is forwarded to the app itself: simulo run app.py -h prints the app’s own flags — its @app.entrypoint’s signature if it has one (for example --num-envs); with no entrypoint, the sole job’s own flags, or (with more than one job) the job list and a --job NAME -h pointer — not this page’s options.