Transformations and Scenarios
These methods change the structure or scenario state of a database.
Database.aggregate(...) now also supports workbook-free Region
aggregation through region_aggregation presets or explicit mappings.
Database.ras(...) rebalances the Z block of an IOT scenario to target
row and column margins with the biproportional RAS algorithm.
Database Transformations#
- mario.Database.aggregate
- mario.Database.add_extensions
- mario.Database.keep_extensions
- mario.Database.add_sectors
- mario.Database.ras
- mario.Database.to_iot
- mario.Database.to_region_subset
- mario.Database.to_single_region
- mario.Database.to_chenery_moses
- mario.Database.pool_trade
- mario.Database.change_assumption
Supply and Trade Mixes#
Scenario-level redistribution of one regional bundle preserving the selected
column totals: technology/market shares with update_supply_mix and
regional sourcing with update_trade_mix. See
Update electricity mixes for the end-to-end workflow
(EMBER supply mix, ENTSO-E trade mix, pool_trade and the data-provider
API keys). update_supply_mix_iot and update_mix_iot are kept as
IOT-only backward-compatible aliases of update_supply_mix.
Scenario Operations#
For workbook-free manual shocks and programmatic scenario edits, see Apply shocks and compare scenarios.