Launcher Settings

This page is generated from config/run.json.md. Do not edit it directly; change the repository source and let automation publish the Wiki.

Launcher settings

config/run.json contains stable build and execution defaults for src/launcher/workflow.py. It does not select a workflow, LUND source, sample profile, physical input, or output path; those choices remain visible on the command line.

The file is strict JSON. Unknown keys fail, so explanations live here rather than in invented comment fields.

Settings

Key	Checked-in value	CLI override
build	true	--build true|false
run	true	--run true|false
build_dir	build/release	--build-dir DIRECTORY
build_type	Release	--build-type Debug|Release|RelWithDebInfo|MinSizeRel
jobs	4	--jobs N with a positive integer

The launcher starts with built-in defaults, replaces them with values from the selected JSON file, then applies command-line overrides. For example, --jobs 2 replaces the checked-in value of 4.

Use another file by passing it to run.csh with --run-settings:

source run.csh \
    --run-settings /path/to/run-settings.json \
    --workflow create-lund \
    --source uniform \
    --build true \
    --run false

The launcher does not look for run.local.json automatically. Name an alternative file with --run-settings. Store an untracked settings file outside the ifarm checkout, because cleanup can delete it before the launcher reads it.

Launcher and child options

--workflow create-lund|submit is always required. For create-lund, launcher-owned --source uniform|physical selects the LUND application. Submission bypasses this build launcher; its resolver accepts the same --source spelling only as truth metadata for input without a LUND creation log. Other unrecognized creation options are forwarded unchanged to the selected LUND executable.

Use -- when forwarding help or any argument that should be unambiguously treated as a child option:

source run.csh \
    --workflow create-lund \
    --source uniform \
    --build false \
    -- \
    --help

Submission bypasses workflow.py and does not read this JSON. Its settings come from the LUND creation log, an optional submission config, CLI overrides, and submission defaults.

Even a command forwarding --help to a LUND application first cleans and updates the ifarm checkout. Only bare launcher help and limited early submission checks can return before cleanup; see the checkout model. During local development, run the compiled application's --help directly.

Invalid Booleans, build types, paths, or worker counts fail before CMake or a child application runs. A failed build prevents LUND creation.