/how-to/index.html Task-oriented guides for preparing evidence, running analyses, and reviewing outputs. Pages Prepare a Tracker Run an Analysis Review Outputs Run Sensitivity Hugo en-gb /how-to/prepare-tracker/index.html Mon, 01 Jan 0001 00:00:00 +0000 /how-to/prepare-tracker/index.html The modelling workflow starts from a long-format tracker. Use one row per extracted effect estimate. Required columns client,evidence_type,metric,value,unit,period,source_type,source_status,source_file_or_link,owner_or_contact,analysis_ready,notes Optional uncertainty columns study_id,estimand_note,standard_error,ci_lower,ci_upper,ci_level,ci_type,p_value,p_value_sidedness,uncertainty_scenario Supported pooled evidence Evidence Default treatment geo_test Pool comparable effects on log_relative scale. bls Pool comparable effects on percentage_point scale. mmm, pa2, ROI, CPA, CPO, iROAS Treat as triangulation unless harmonised upstream. Validate the tracker marketbayesmeta-check-tracker path/to/tracker.csv marketbayesmeta-check-tracker path/to/tracker.csv --audit --include-partial Resolve or explicitly accept: /how-to/run-analysis/index.html Mon, 01 Jan 0001 00:00:00 +0000 /how-to/run-analysis/index.html Use a YAML config when an analysis should be repeatable and reviewable. marketbayesmeta-check-config examples/config.yaml marketbayesmeta-run examples/config.yaml For local repository use: python runme.py examples/config.yaml Conservative default gates Config runs stop on directional and not_recommended readiness by default, and failed sampler diagnostics are blocking by default. diagnostics: allow_directional: false allow_not_recommended: false allow_duplicates: false fail_on_diagnostic_failure: true minimum_studies_ready: 4 minimum_studies_directional: 3 Override these only for explicit exploratory work. Record the reason in project.notes or the downstream analysis review. /how-to/review-outputs/index.html Mon, 01 Jan 0001 00:00:00 +0000 /how-to/review-outputs/index.html Config runs write a compact artefact set intended for analyst review. First files to open File Review question analysis_report.md What is the run status, readiness, and headline result? run_status.json Is reportable true? Why did the run complete, warn, block, or fail? readiness.csv How many comparable rows were eligible, and are they enough? diagnostics.csv Did sampler diagnostics pass configured thresholds? prior_diagnostics.csv Do priors imply warnings or implausible prior-predictive ranges? effect_preparation.csv Which rows were included, transformed, excluded, or scenario-based? ppc.csv Are individual studies out of line with in-sample posterior predictive checks? Status meanings run_status.json may report: /how-to/run-sensitivity/index.html Mon, 01 Jan 0001 00:00:00 +0000 /how-to/run-sensitivity/index.html Small-sample Bayesian meta-analysis can be prior-sensitive and uncertainty-sensitive. For serious reporting, sensitivity is part of the result. Enable prior sensitivity sensitivity: prior: true When prior_specs are omitted, the package uses a scale-aware grid: log_relative: regularising, default, weak percentage_point: regularising, default, weak Review prior_sensitivity.csv for pooled mean, probability positive, interval width, diagnostics, and deltas versus the default prior.