Choose the format of your database. Each guide explains its blocks, names, axes and calculation assumptions together.
One sector set on both sides of the transaction matrix. Sectors represent industries or products, depending on the source.
Flows
Explore IOT structure and nomenclature
Activities and commodities have separate axes. Supply records what activities produce; use records their inputs.
Flows
Explore SUT structure and nomenclature
Objects in MARIO#
Database
The mario.Database object holding your table, metadata and scenarios.
Table
The accounting structure: IOT or SUT. Inspect it with db.table_type.
Scenario
A state of that table, such as the baseline or a modified scenario.
Matrix
A named block or result, such as db.Z or db.U.
Each scenario stores its own matrices. MARIO can calculate missing quantities when requested; Scenarios explains how the states are managed.
Flows, coefficients and units#
For paired names such as Z / z or E / e, capitals indicate
absolute flows and lowercase indicates coefficients per unit of output.
A table can contain both. Final-demand blocks remain flows.
The format describes the arrangement of the table. Monetary or physical units come from the database: a hybrid table can use different units for different products. Check units before summing quantities or comparing coefficients.
These guides use MARIO’s default names. See custom labels to change them, or the matrix reference for the full catalogue.