Using GTAP aggregation (AggreGAMS) with MIRAGE-e #

How to #

Setting up the aggregation directory #

• Download AggregGAMS from Git repository or from CEPII’s network.
• Copy the GTAP database in the folder data/%Ver%_%Year% where %Ver% is the GTAP version number (e.g. 91 for GTAP 9.1) and Year is the corresponding year. The required files are: gsddat.har, gsdemiss.har, gsdpar.har, gsdset.har, gsdvole.har.

Building the aggregation #

• Build your aggregation on Excel, using the file corresponding to your version, e.g. Aggregation%Ver%_Simple.xlsm. The Label for your aggregation will be what follows the version number. In the previous example: _Simple.
  • If you are using MIRAGE-e 2 with GHG features, check that your sector aggregation respects the constraints below
  • If you plan to implement the Paris agreement, check that your regional aggregation respects the constraints below
  • Also check that every transport sector is listed as in Perfect competition

Aggregate #

• Check the main file Aggregation.gms:
• The version should be correct:

$setglobal Ver 92

In the case you are using MIRAGE-e 2, the correct version is 90a

• The year should be correct

$setglobal Year 2011 

• The Label corresponds to the Excel file you edited beforhands:

$setglobal Label "_Simple" 

• Launch the aggregation in GAMS with a chosen name for the g00 file, e.g. s=data
• Copy and paste the files data.g00 and GTAP_version_info.txt to MIRAGE root directory
• When running MIRAGE’s Calib.gms file, don’t forget to check the start file name, e.g. r=data.

Constraints on aggregation specific to MIRAGE-e 2.0 #

To have the full features of MIRAGE-e 2, additionnal constraints are added. The purpose of these constrait is :

• GTAP sectors need to be aggregated only between the same type of sectors (see below) to be subject to the correct GHG-inclusive production function
• GTAP agricultural sectors are better if aggregated separately for animal and vegetal agriculture, due to different trajectories in sector productivity in the baseline
• In case the Paris agreement needs to be implemented, GTAP regions need to be aggregated only between regions with the same type of commitment (see below)

Sector aggregation compatible with MIRAGE-e 2 #

The table below summarizes the constraints on sectors :

Region aggregation compatible with the Paris agreement #

There are three different types of commitments in the Paris agreement:

• Aboslute : the target reduction is labeled in percetage change from a reference emissions in the past
• Intensity : the target reduction is labeled as a percentage reduction in GHG-intensity of GDP from a reference intensity in the past
• BAU : the target reduction is labeled as a percentage reduction in emissions in a future date, compared to the BAU scenario

In order to implement the Paris agreement, the regional aggregation has to match the types of commitments. The aggregation of commitment is done separately in the R code NDCs_r.