<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>How-To Guides — DSAMbayes Documentation</title>
    <link>//localhost:1313/how-to/index.html</link>
    <description>Purpose Provide task-oriented recipes for common DSAMbayes operational workflows. Each guide starts from a user objective, gives minimal reproducible steps, and includes expected output artefacts and quick verification checks.&#xA;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</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <atom:link href="//localhost:1313/how-to/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Run from YAML</title>
      <link>//localhost:1313/how-to/run-from-yaml/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>//localhost:1313/how-to/run-from-yaml/index.html</guid>
      <description>Objective Execute a complete DSAMbayes model run from a YAML configuration file and verify the staged output artefacts.&#xA;Prerequisites DSAMbayes 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 mkdir -p .Rlib .cache export R_LIBS_USER=&#34;$PWD/.Rlib&#34; export XDG_CACHE_HOME=&#34;$PWD/.cache&#34; 2. Validate the configuration (dry run) Rscript scripts/dsambayes.R validate --config config/my_config.yaml Expected outcome:</description>
    </item>
    <item>
      <title>Interpret Diagnostics</title>
      <link>//localhost:1313/how-to/interpret-diagnostics/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>//localhost:1313/how-to/interpret-diagnostics/index.html</guid>
      <description>Objective Read and act on the diagnostics report produced by a DSAMbayes runner execution, understanding which checks matter most and what remediation steps to take.&#xA;Prerequisites A completed runner run execution with artefacts under 40_diagnostics/. Familiarity with Diagnostics Gates definitions. Steps 1. Open the diagnostics report cat results/&lt;run_dir&gt;/40_diagnostics/diagnostics_report.csv Each row is one diagnostic check. The key columns are:</description>
    </item>
    <item>
      <title>Compare Runs</title>
      <link>//localhost:1313/how-to/compare-runs/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>//localhost:1313/how-to/compare-runs/index.html</guid>
      <description>Objective Compare multiple DSAMbayes runner executions and select a candidate model for reporting or decision-making, using predictive scoring and diagnostic summaries.&#xA;Prerequisites Two or more completed runner run executions (MCMC fit method). Artefacts under 50_model_selection/ for each run (LOO summary, ELPD outputs). Familiarity with Diagnostics Gates and Model Selection Plots. Steps 1. Collect run directories Identify the run directories to compare:</description>
    </item>
    <item>
      <title>Debug Run Failures</title>
      <link>//localhost:1313/how-to/debug-run-failures/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>//localhost:1313/how-to/debug-run-failures/index.html</guid>
      <description>Objective Diagnose and resolve the most common failure modes encountered when running DSAMbayes via the YAML/CLI runner.&#xA;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.</description>
    </item>
  </channel>
</rss>