Local Execution

Generate and inspect a dataset on one host with the default local executor:

rfgen init narrowband-baseline ./my-config
cd ./my-config
rfgen validate --config-dir .
rfgen generate --config-dir .
rfgen inspect ./rfgen-output

generate runs synchronously in the invoking process. It returns after writing the requested records or reporting an error. inspect reports on the stored dataset without changing it; ./rfgen-output is the maintained baseline’s local output. Use the configured storage path if you change it. For the read-only inspection boundary, see Inspect and audit a dataset.

When to use it

Use local execution for debugging, CI, and small single-host datasets. A materialized template uses it unless you select another executor. It keeps the editable configuration, validation, generated store, and inspection workflow on one host. Configuration model and lifecycle explains executor selection.

The local Golden Paths are the production-qualified generation journeys. Their scope and supported templates are documented in Golden Paths. For a runnable workflow, follow Generate a local dataset.

Output and provenance

The selected storage configuration controls where records are written; the maintained baseline uses the local storage workflow. Records retain scene and generator provenance. Keep the resolved YAML with the experiment record: it is the durable description of the request.

Storage backends and their access boundaries are specified in Storage and the storage schema. Exact executor and command options belong to the generation API and CLI reference.