premium_module
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| premium_module [2020/03/13 11:44] – [Basic concept] matsz | premium_module [2020/03/13 11:45] – [Basic concept] matsz | ||
|---|---|---|---|
| Line 57: | Line 57: | ||
| **Figure 14: Example of technical implementation of a premium scheme** | **Figure 14: Example of technical implementation of a premium scheme** | ||
| - | {{: | + | {{: |
| The sets of payments, exemplified by DPGRCU in the figure, and the activity groups, exemplified by PGGRCU and PGPROT are defined in the file policy\policy_sets.gms. Since this is a “static” GAMS file used in any simulation, it contains the gross list of all policies that currently can be simulated, including legacy ones. In order to work efficiently with the acronyms which define the application types, these are converted to numerical attributes as shown below (// | The sets of payments, exemplified by DPGRCU in the figure, and the activity groups, exemplified by PGGRCU and PGPROT are defined in the file policy\policy_sets.gms. Since this is a “static” GAMS file used in any simulation, it contains the gross list of all policies that currently can be simulated, including legacy ones. In order to work efficiently with the acronyms which define the application types, these are converted to numerical attributes as shown below (// | ||
premium_module.txt · Last modified: 2022/11/07 10:23 by 127.0.0.1