Overview

A complete model run is initiated by RunAll.bat (standard) or RunAll_Debug.bat (debug mode). Both scripts call RunModel.bat, which executes the full calibration pipeline before running scenarios. A complete run can take many hours.

To make a full model run, double-click either RunAll.bat or RunAll_Debug.bat.

🛈

Debug mode (RunAll_Debug.bat/RunModel Debug) saves additional intermediate checkpoints and produces Excel DTA output files at each stage, making it easier to inspect results at each step. Fast mode skips some of these saves.


Fast Mode vs. Debug Mode

RunModel.bat accepts a single argument that controls how many checkpoints are saved and whether Excel DTA files are produced:


Mode

Launched via

Behavior

Fast

RunAll.bat

Saves only the checkpoints marked Both in the checkpoint table below. No Excel DTA output at intermediate stages. Faster overall run time.

Debug

RunAll_Debug.bat

Saves all checkpoints (Both and Debug-only). Produces Excel DTA files at each calibration stage. Slower, but provides full audit trail.


Checkpoint Reference

The table below lists all available checkpoints in the order they appear in RunModel.bat, which mode produces them, what stage they represent, and what follows.

Checkpoint

Available In

Database State When Saved

What Runs After This Point

Process

Both

All process input data loaded into database

RunModel (beginning) — economic drivers, maps, calibration

Process2

Debug

After maps, economic drivers, and initial VB scripts

OG switches, GHG/CAC setup, economic calibration

Process3

Debug

After OG calibration, GHG/CAC coefficients applied

Price calibration (SCalibRun / SCalibPricesRun)

CalibPrice

Debug

After price calibration

Biofuels, hydrogen, MEconomy calibration

CalibMEconomy

Debug

After MEconomy calibration (MCalibRun)

Demand totals, CCS, carbon taxes, residential calibration

CalibRes

Debug

After residential sector calibration

Commercial sector calibration

CalibCom

Debug

After commercial sector calibration

Industrial sector calibration

CalibInd

Both

After industrial sector calibration

Transportation sector calibration

CalibTrans

Debug

After transportation sector calibration

Load curves, post-supply run

Calib

Both

After load curve and post-supply calibration

Plant/unit characteristics, electric unit build-out

Calib2

Both

After first full scenario run (1986–2024)

Electric generation calibration (EGCalibRun), price endogenization

Calib3

Both

After second full scenario run (1986–2050) with elec price calib

GHG/CAC macro, refining, supply/demand balancing

Calib4

Both

After third full scenario run (1986–2050) with full GHG/CAC

Final adjustments, SetAsPolicyCase, StartBase creation

StartBase

Both

Calibrated baseline database ready for scenario runs

Base, OGRef, Ref25, and scenario runs


Deciding When RunAll is Needed

The table below shows quick rules-of-thumb for whether you need a RunAll or RunModel:

Rules-of-Thumb for Whether to Execute RunAll vs RunModel:

If you do this...

You should run...

If you have not yet executed the model:

Execute RunAll.bat or RunAll_Debug.bat

If you change model databases, such as modifying or adding/deleting variables or sets:

If you make changes to mappings or aggregations of economic data:

If you add a new default economic forecast (TOMInitial.db):

If you make changes to .dat input data files:

After having made a full model run with RunAll, and if you then you modify any files in \Calibration or \Input\Scripts folders:

Execute RunModel.bat

If you make a change in a file in \Calibration or \Input\Scripts folders, you may be able to save time by starting your run at one of the checkpoints created in RunModel.bat. See Restarting Model from Midpoint for instructions.