Run Manager

Learn RunManager with Videos - https://www.youtube.com/playlist?list=PLRCe_SRAk7hOvHdyCuLQ15-6JldaH8Ryu

Overview

• The Run Manager is used to compose and submit model runs

• Each model run is based on a Case definition comprising:

  • Scenarios

  • Regions

  • Settings

  • Properties

Modifying RUN files

There are new attributes to write TIMES switches or GAMS code at five different locations in the RUN file. Further, these declarations can also be made at the top or bottom of scenario DD files (last two attributes in the table below). The attributes are supported by regular INS/DINS tables, in any scenario file or in SysSettings.

Attribute	Location	Alias
RFCmd_GAMS	<GAMSOPTIONS>	RFCmd_G, RFCmd
RFCmd_OPTIMIZER	<OPTIMIZER>	RFCmd_O
RFCmd_FLAGS	<SET FLAGS>	RFCmd_F
RFCmd_DD	<INCLUDE DD FILES>	RFCmd_D
RFCmd_GLOBAL	<GLOBAL Parameters>	RFCmd_Glb
SFCmd_top	top of the scen DD file	SFCmd_T, SFCmd
SFCmd_bot	bottom of the scen DD file	SFCmd_B

There is no need to modify the RUN file template manually.

Commands will be ordered by Value column; only rows with value>0 will be considered. If multiple scenarios send commands to the RUN file, the blocks will be ordered as per the order of scenarios in the case definition.

Note

This also opens up some new possibilities. For example, you can run parametric scenarios where base prices for elastic demands are picked up from different Reference cases.

These examples are available in the Advanced Demo model.

Example 1

~TFM_INS
Attribute	Other_Indexes	Value		Comment
RFCmd_F	$SET BENCOST YES	1		Written to FLAG section of RUN file
RFCmd_F	$SET ANNCOST LEV	2
RFCmd_F	$SET WAVER YES	3
RFCmd_G	GAMS statement 1	1		Written GAMSOPT section
RFCmd_Glb	GAMS statement 2	2		Written to Global parameters section
RFCmd_Glb	GAMS statement 3	3
SFCmd_T	$OFFEPS	1		Top of the scen DD file
SFCmd_B	GAMS statement A	3		Bottom of the scen DD file
SFCmd_B	GAMS statement B	4

If you want to use single quotes <’> in your instructions, then it is necessary to use a DINS table, as shown below. DINS tables need process or commodity specification. You can use any valid process instead of IMPNRGZ; it will have no impact on the outcome.

Example 2

~TFM_DINS-AT
RFCmd_DD	Other_Indexes	pset_pn
3	set nr(all_reg);	IMPNRGZ
4	nr(all_reg)=yes$(not r(all_reg));	IMPNRGZ
5	*–	IMPNRGZ
6	*Python embedded code to remove invalid TU and TB trade processes	IMPNRGZ
7	set cb_p(r,p) all crossborder processes involved	IMPNRGZ
8	*–	IMPNRGZ
9	;	IMPNRGZ
10	cb_p(r,p)=yes$gr_genmap(r,p,’CrossBorderTrade’);	IMPNRGZ
11	*–	IMPNRGZ
12	embeddedCode Python:	IMPNRGZ
13	ncb_p = []	IMPNRGZ
14	for r,p in gams.get(‘cb_p’):	IMPNRGZ
15	*–	IMPNRGZ
16	*–	IMPNRGZ
17	*–	IMPNRGZ
18	gams.set(‘ncb_p’,ncb_p)	IMPNRGZ
19	endEmbeddedCode ncb_p	IMPNRGZ
20	ACT_BND(R,T,P,S,’UP’)$ncb_p(r,p) = EPS;	IMPNRGZ

Case definition

• Create a New Case by providing the core information for the case definition

  • Case Name - name of the case

  • Description - description of the case

  • Scenario Group - scenarios to be included in this run

  • Region Group - regions to be included in this run

  • Parametric Group - driver scenario for a suite of runs

  • Properties Group - what GAMS options/switch are to be employed

  • Periods Definition - period definition for the run

  • Ending Year - last period for the run

  • Source TIMES - where does the TIMES code reside

  • Solver - which solver is to be used

  • Solver Options - which solver options to use

  • GDX References - GDX files to be used for freezing periods, elastic demand base prices or IRE bounds/prices

Model run submission

• Select one (or more) of the cases in the Managed Save Cases section and click SOLVE

• Solve status of model case can be tracked in JobsDashboard.