/how-to/index.html Purpose Provide task-oriented recipes for common dsambayesplus operational workflows. Each guide starts from a user objective, gives minimal reproducible steps, and includes expected output artefacts and quick verification checks. Audience Users who know the concepts but need execution steps. Engineers debugging run and artefact issues. Pages Guide Objective Run from YAML Execute a complete runner workflow and verify staged outputs Interpret Diagnostics Read and act on diagnostics gate results Compare Runs Compare multiple runs and select a candidate model Debug Run Failures Diagnose and resolve common runner failure modes Hugo en-gb /how-to/run-from-yaml/index.html Mon, 01 Jan 0001 00:00:00 +0000 /how-to/run-from-yaml/index.html Objective Execute a complete dsambayesplus model run from a YAML configuration file and verify the staged output artefacts. Prerequisites dsambayesplus installed locally (see Install and Setup). A YAML config file (see Config Schema for structure). Data file(s) referenced by the config are accessible. Steps 1. Set up the environment Complete the environment setup in Install and Setup (selecting the host library, creating the cache directory, and exporting XDG_CACHE_HOME) before continuing. /how-to/interpret-diagnostics/index.html Mon, 01 Jan 0001 00:00:00 +0000 /how-to/interpret-diagnostics/index.html Objective Read and act on the diagnostics report produced by a dsambayesplus runner execution, understanding which checks matter most and what remediation steps to take. This is the operational triage guide. For the methodological meaning of the gates themselves, see Stage 4: Computation and Sampler and Stage 5: Model Adequacy. Prerequisites A completed runner run execution with artefacts under 40_diagnostics/. Familiarity with Diagnostics Gates definitions. Steps 1. Open the diagnostics report cat results/<run_dir>/40_diagnostics/diagnostics_report.csv Each row is one diagnostic check. The key columns are: /how-to/compare-runs/index.html Mon, 01 Jan 0001 00:00:00 +0000 /how-to/compare-runs/index.html Objective Compare multiple dsambayesplus runner executions and select a candidate model for reporting or decision-making, using predictive scoring and diagnostic summaries. This page is a late-stage selection aid, not a full workflow. Use it only after the candidate runs are computationally trustworthy enough to compare. In the principled workflow, that means Stage 4 and Stage 5 work has already been done: the sampler is behaving acceptably, and the model is at least adequate enough to remain a candidate. For the surrounding methodology, see Stage 4: Computation and Sampler and Stage 5: Model Adequacy. /how-to/debug-run-failures/index.html Mon, 01 Jan 0001 00:00:00 +0000 /how-to/debug-run-failures/index.html Objective Diagnose and resolve the most common failure modes encountered when running dsambayesplus via the YAML/CLI runner. Prerequisites A failed runner execution (non-zero exit code or missing artefacts). Access to the terminal output or log from the failed run. Familiarity with CLI Usage and Config Schema. Triage by failure stage Stage 0: Config resolution failures Symptoms: runner exits immediately after validate or at the start of run; no run directory created or only 00_run_metadata/ is present.