Skip to content

Latest commit

 

History

History
281 lines (217 loc) · 10 KB

6_AdvancedChangeInputs.md

File metadata and controls

281 lines (217 loc) · 10 KB
Raw

Changing inputs in the MAgPIE model

Miodrag Stevanovic (stevanovic@pik-potsdam.de), updated by Florian Humpenöder (humpenoeder@pik-potsdam.de) 10 December, 2020

1 Introduction

The input data for MAgPIE is prepared by a set of pre-processing routines that take the data from original sources (e.g. FAO, LPJmL…), execute additional calculations and convert it to the required MAgPIE parameter format. These pre-processing routines are not accessible as open source at the moment. A user is instead provided with a ready-made inputs that are necessary for the model execution.

The input files are setup in the config file config/default.cfg, usually at the beginning of the settings. Currently, the input data is set as:

cfg$input <- c("isimip_rcp-IPSL_CM5A_LR-rcp2p6-co2_rev48_c200_690d3718e151be1b450b394c1064b1c5.tgz",
         "rev4.52_h12_magpie.tgz",
         "rev4.52_h12_validation.tgz",
         "calibration_H12_c200_26Feb20.tgz",
         "additional_data_rev3.86.tgz")

Once specified in the configuration as the input data, the data is automatically downloaded (if needed) when the model run is started.

The prepared input data are compressed tar archive files “.tgz”, which can be opened with software such as 7-Zip, or in terminal by tar and untar commands. The data archive files contain the following types of data:

  • Cellular input data (e.g. land area, crop yields, water requirements, carbon density)
    • isimip_rcp-IPSL_CM5A_LR-rcp2p6-co2_rev48_c200_690d3718e151be1b450b394c1064b1c5.tgz
  • Regional input and validation data (e.g. food demand)
    • rev4.52_h12_magpie.tgz
    • rev4.52_h12_validation.tgz
    • calibration_H12_c200_26Feb20.tgz
  • Global and other input data (e.g. conversion factors, national policies)
    • additional_data_rev3.86.tgz

1.1 Learning objectives

There is a specific procedure on how to handle the changing of the input data. It will be demonstrated by the example of changing the USA NDC policy on afforestation target at 2030 with the following learning objectives:

  1. Create local input data repository.
  2. Package the patch file.
  3. Update the configuration to automatically apply designed changes.

2 Demonstration of change in input data for national land-based NDC policies

Once the input data is downloaded to the local MAgPIE repository in forms of different input files in designated input folders (in the core, scripts, modules and module realizations), a user can update or change these input data files. This can be done directly by manipulating the files, but this approach carries a risk that such changes are not documented and that in certain cases the made changes can be overwritten by the repeated download of the data from the declared repositories. In order to avoid this risk, it is recommended to create a local folder that serves as a repository for the patch files that will apply changes to the data by overwriting the original data.

2.1 Create folder for local input data repository

The folder for local input data repository can be created anywhere and it’s path must be provided to the settings in config/default.cfg file.

Let us assume that the patch folder (patch_inputdata) is created in the main MAgPIE repository. One can do it in R:

dir.create("./patch_inputdata")

or in the command line:

mkdir patch_inputdata

Once the directory is created, provide its location to the configuration file. It’s important to keep the list structure of the repository information:

cfg$repositories <- append(list("https://rse.pik-potsdam.de/data/magpie/public"=NULL,
                                "./patch_inputdata"=NULL),
                           getOption("magpie_repos"))

2.2 Create a patched file policy_definition.csv and package it with gms::tardir()

Create a sub-directory in the ./patch_inputdata which is going to be used for packaging of the patched files.

dir.create("./patch_inputdata/patch_ndc_usa_190909")

Copy the original file the policy_definition.csv in the patch folder. In R:

file.copy(from="./scripts/npi_ndc/policies/policy_definitions.csv",
          to="./patch_inputdata/patch_ndc_usa_190909/.")

or in the command line:

cp scripts/npi_ndc/policies/policy_definitions.csv patch_inputdata/patch_ndc_usa_190909/.

Edit the content, in this case update the USA afforestation NDC policy (affore) with a more ambitious target of 15 MHa of afforested area starting in 2020 and reaching the target at 2030:

USA,affore,ndc,1,2020,2030,15

After saving the file, package it with the tardir function in R environment and delete the file patch folder:

gms::tardir(dir="patch_inputdata/patch_ndc_usa_190909",
               tarfile="patch_inputdata/patch_ndc_usa_190909.tgz")

unlink("patch_inputdata/patch_ndc_usa_190909", recursive=TRUE)

2.3 Add the .tgz packed patch file in the configuration file

Finally, the configuration file should be informed about the change in the input data and the existing patch file that replaces the existing input data. For this, edit the config/default.cfg file from:

cfg$input <- c("isimip_rcp-IPSL_CM5A_LR-rcp2p6-co2_rev48_c200_690d3718e151be1b450b394c1064b1c5.tgz",
         "rev4.52_h12_magpie.tgz",
         "rev4.52_h12_validation.tgz",
         "calibration_H12_c200_26Feb20.tgz",
         "additional_data_rev3.86.tgz")

to:

cfg$input <- c("isimip_rcp-IPSL_CM5A_LR-rcp2p6-co2_rev48_c200_690d3718e151be1b450b394c1064b1c5.tgz",
         "rev4.52_h12_magpie.tgz",
         "rev4.52_h12_validation.tgz",
         "calibration_H12_c200_26Feb20.tgz",
         "additional_data_rev3.86.tgz",
         "patch_ndc_usa_190909.tgz")

It is very important to add the patch file at the end of the listings in the cfg$input listings, because every next .tgz archive will overwrite the files previously imported by the files that are contained in it.

At the next start of the model by Rscript, the new patch will place the file with change inputs according to the changes in the settings.

3 Alternative way of adding a local repository

As an alternative to the steps carried out in 2.1 we can add a local repository to getOption("magpie_repos"). For this, we have to add an entry in the .Rprofile file. Typically .Rprofile is located in the users’ home directory (~/.Rprofile).

options(magpie_repos=list("~/input_data/"=NULL))

The local repository can be located anywhere on your filesystem. You could then add patch_ndc_usa_190909.tgz in this folder.

Changes in default.cfg.

cfg$repositories <- append(getOption("magpie_repos"),
                           list("https://rse.pik-potsdam.de/data/magpie/public"=NULL))

With this setup, the download script (Rscript start.R -> 3 Download data) will first look into your local repo and check if the input files (cfg$input) exist. If you download the input files once from https://rse.pik-potsdam.de/data/magpie/public to your local repo, this saves you from downloading all input files again in case you make a change to cfg$input.

4 Excercise:

Write your own starting script that will test the scenario with changed NDC policy for the USA described above. None of the changes should actually occur in the default.cfg, but instead the starting script should introduce them to the loaded cfg object.

Add a MAgPIE start script here: scripts/start/projects/name_of_your_script.R

With this content:

# |  (C) 2008-2020 Potsdam Institute for Climate Impact Research (PIK)
# |  authors, and contributors see CITATION.cff file. This file is part
# |  of MAgPIE and licensed under AGPL-3.0-or-later. Under Section 7 of
# |  AGPL-3.0, you are granted additional permissions described in the
# |  MAgPIE License Exception, version 1.0 (see LICENSE file).
# |  Contact: magpie@pik-potsdam.de

# ----------------------------------------------------------
# description: Test USA NDC
# ----------------------------------------------------------


######################################
#### Script to start a MAgPIE run ####
######################################

library(lucode2)
library(magclass)
library(gms)

# Load start_run(cfg) function which is needed to start MAgPIE runs
source("scripts/start_functions.R")

#start MAgPIE runs
source("config/default.cfg")

#cfg$force_download <- FALSE

cfg$results_folder <- "output/:title:"

cfg$output <- c("rds_report")


cfg$title <- "SSP2_NDC_default"
cfg <- gms::setScenario(cfg,c("SSP2","NDC"))
cfg$input <- c("isimip_rcp-IPSL_CM5A_LR-rcp2p6-co2_rev48_c200_690d3718e151be1b450b394c1064b1c5.tgz",
               "rev4.52_h12_magpie.tgz",
               "rev4.52_h12_validation.tgz",
               "calibration_H12_c200_26Feb20.tgz",
               "additional_data_rev3.86.tgz")
start_run(cfg,codeCheck=FALSE)

cfg$title <- "SSP2_NDC_USA"
cfg <- gms::setScenario(cfg,c("SSP2","NDC"))
cfg$input <- c("isimip_rcp-IPSL_CM5A_LR-rcp2p6-co2_rev48_c200_690d3718e151be1b450b394c1064b1c5.tgz",
               "rev4.52_h12_magpie.tgz",
               "rev4.52_h12_validation.tgz",
               "calibration_H12_c200_26Feb20.tgz",
               "additional_data_rev3.86.tgz",
               "patch_ndc_usa_190909.tgz")
start_run(cfg,codeCheck=FALSE)