Skip to content

Simulation Playbook

Run this playbook to configure and execute a GCBM simulation from the GCBM Assistant Simulation page.

Document Control

Field Value
Author Geraldson Muluh
Owner GCBM Assistant maintainers
Audience Model operators and analysts
Last reviewed 2026-03-27
Review cadence Monthly

Prerequisites

  • GCBM Assistant is installed and launches successfully.
  • Python requirement for source installs is >=3.10.
  • You have a valid project workspace with:
  • layers/raw/inventory/*.shp (or equivalent inventory shapefile path)
  • optional disturbance shapefiles
  • input database files in input_database/
  • yield table CSV

Inputs Required

  • Project directory root
  • Inventory shapefile
  • Disturbance shapefile(s), if applicable
  • CBM defaults database (AIDB)
  • Yield table
  • Column mappings:
  • age
  • classifiers
  • temperature source (column or TIF)

Procedure

Step 1: Select Project Directory

  1. Open Simulation.
  2. Set project directory.
  3. Confirm auto-discovered files are populated.

Simulation project selection

Step 2: Review Input Discovery

  1. Verify inventory and disturbance paths.
  2. Verify AIDB and yield table paths.
  3. Correct any missing path manually.

Simulation input discovery

Step 3: Map Required Columns

  1. Select age column.
  2. Select required classifier columns.
  3. Choose temperature input type and field/path.

Simulation column mapping

Step 4: Validate and Run

  1. Click Validate Configuration.
  2. Resolve any validation error before running.
  3. Click Run Simulation and monitor logs.

Simulation validate and run

Expected Outputs

After a successful run, your project should contain:

  • gcbm_project/output/ (model output database and run artifacts)
  • gcbm_project/ runtime configuration snapshots
  • simulation logs for traceability

Validation Checks

  • Validation reports no missing required files or mappings.
  • Run completes without unhandled exception in log panel.
  • Output database exists in the project output directory.

Failure Modes and Recovery

Failure mode Typical cause Recovery
Validation fails on missing files Wrong project folder or naming mismatch Re-select project root and manually set missing paths
Run fails after start Invalid classifier mapping or bad input data Re-check mappings and inspect first error line in logs
No output DB generated Run interrupted or configuration invalid Re-run after fixing validation/log errors

Run Specifics and Auditability Checklist

Record these items for each run:

  • GCBM Assistant version
  • Simulation name and date-time
  • Project path and key input file paths
  • Start year, end year, resolution, classifier selections
  • Validation status and run completion status
  • Output DB path and log path