WIOD parser walkthrough#
This notebook is the practical guide for parsing WIOD 2016 workbooks in MARIO.
What this notebook covers#
where to download each WIOD workbook family;
when to pass a direct file path and when to pass a directory;
how
year=andcountry=disambiguate candidate files;how
MRIO, nationalIOT, and nationalSUTworkflows differ;how
add_extensions=importsSocio_Economic_Accounts.xlsx;why the international
SUTparser exposesrow_mode=and why that part should still be treated with caution.
Relevant source pages#
Official WIOD 2016 release page: GGDC WIOD 2016 release
MRIO IOT, current prices: Dataverse 199104
MRIO IOT, previous-year prices: Dataverse 199102
MRIO international SUT: Dataverse 199100
National IOT bundle: Dataverse 199099
National SUT bundle: Dataverse 199096
Socio-economic accounts: Dataverse 199095
Main entry point#
For normal user workflows, the public entry point is:
mario.parse_wiod(...)
The same function supports:
multiregional
IOTworkbooks;multiregional
IOT_PYPworkbooks;multiregional international
SUTworkbooks;national
IOTworkbooks;national
SUTworkbooks;optional socio-economic extensions through
add_extensions=.
Key arguments#
The key public arguments are:
path: one workbook or one directory containing multiple WIOD workbooks;table: choose"IOT"or"SUT";year: used to disambiguate directories and mandatory for national workbooks with multi-year content;country: useful when one directory contains multiple national workbooks;add_extensions: optional path toSocio_Economic_Accounts.xlsx;row_mode: only relevant for the internationalSUTworkbook.
Direct file path vs directory path#
Use a direct workbook path when you already know the exact file to parse. This is the simplest case and often means you do not need year= or country=.
Use a directory path when you keep several WIOD files together. In that case MARIO scans the directory and then uses table=, year=, and optionally country= to pick the correct file.
Example local layouts and caveats#
Typical extracted layout:
WIOD/
├── WIOTS_in_EXCEL/
│ └── WIOT2014_Nov16_ROW.xlsb
├── WIOTS_PYP_in_EXCEL/
│ └── WIOT2014_PYP_Nov16_ROW.xlsb
├── NIOTS/
│ └── ITA_NIOT_nov16.xlsx
├── SUT_national/
│ └── ITA_SUT_nov16.xlsx
├── SUT_international/
│ └── intsut14_nov16.xlsb
└── Socio_Economic_Accounts.xlsx
National IOT and SUT workbooks contain multiple years in one file, so year= is mandatory for those inputs. For the international SUT, row_mode="external_account" is the recommended mode because ROW is not published as a complete endogenous economy.
[1]:
import mario
Optional download step#
MARIO provides dedicated WIOD download helpers instead of one generic downloader for every asset.
[ ]:
mario.download_wiod2016(
path="/path/to/wiod",
table="IOT",
)
mario.download_wiod2016_iot_pyp("/path/to/wiod_pyp")
mario.download_wiod2016_national_iot("/path/to/wiod_national_iot")
mario.download_wiod2016_national_sut("/path/to/wiod_national_sut")
mario.download_wiod2016_socioeconomic_accounts("/path/to/wiod_extensions")
Parse one explicit MRIO IOT workbook#
Use this when you want to point MARIO to one specific WIOD multiregional IOT file.
[ ]:
db = mario.parse_wiod(
path="/path/to/WIOT2014_Nov16_ROW.xlsb",
table="IOT",
)
INFO Parser: reading WIOD workbook WIOT2006_Nov16_ROW.xlsb sheet 2006.
INFO Parser: WIOD IOT payload ready with shapes Z=(2464, 2464), Y=(2464, 220), V=(6, 2464).
INFO Metadata: initialized.
[3]:
db
[3]:
name = WIOT2006_Nov16_ROW
table = IOT
scenarios = ['baseline']
Factor of production = 6
Satellite account = 1
Consumption category = 5
Region = 44
Sector = 56
Parse one explicit MRIO IOT workbook in previous-year prices#
The _PYP variant is selected from the filename directly. No extra parser flag is needed.
[ ]:
db = mario.parse_wiod(
path="/path/to/WIOT2014_PYP_Nov16_ROW.xlsb",
table="IOT",
)
Parse one international SUT workbook#
This is the source where the treatment of ROW matters.
[ ]:
db = mario.parse_wiod(
path="/path/to/intsut14_nov16.xlsb",
table="SUT",
row_mode="external_account",
)
Parse one national IOT workbook#
National WIOD IOT workbooks contain multiple years in one workbook, so year= is required.
[ ]:
db = mario.parse_wiod(
path="/path/to/ITA_NIOT_nov16.xlsx",
table="IOT",
year=2014,
)
Parse one national SUT workbook#
National WIOD SUT workbooks also require year=.
[ ]:
db = mario.parse_wiod(
path="/path/to/ITA_SUT_nov16.xlsx",
table="SUT",
year=2014,
)
Parse from a directory containing multiple WIOD files#
This is the important case when you keep several WIOD files together. Use year= to select the release and country= when the directory contains multiple national workbooks.
[ ]:
db = mario.parse_wiod(
path="/path/to/wiod_directory",
table="SUT",
country="ITA",
year=2014,
)
Add socio-economic extensions#
When add_extensions= is provided, MARIO imports Socio_Economic_Accounts.xlsx as satellite extensions.
for
IOT, they populateE;for
SUT, they populateEaand keepEczero-filled.
[ ]:
db = mario.parse_wiod(
path="/path/to/WIOT2014_Nov16_ROW.xlsb",
table="IOT",
add_extensions="/path/to/Socio_Economic_Accounts.xlsx",
)
Warnings to expect#
Typical parser warnings or important notes are:
unreadable
.xlsbfiles stored as cloud placeholders instead of real local files;ambiguous directory selections when
year=orcountry=is missing;notes in
db.meta_historywhen the internationalSUTparser reclassifiesROWunderrow_mode="external_account".