minimum wage scneario #454
Conversation
| p36_calibration_hourly_costs(iso) Additive calibration term for hourly labor costs (USDMER05 per hour) | ||
| p36_cost_share(t,i) Capital share of factor costs (1) | ||
| p36_share_calibration(i) Additive calibration term for capital shares (1) | ||
| p36_nonmagpie_labor_costs(t,i) Labor costs from subsidies and VoP not covered by MAgPIE (mio. USDMER05) |
There was a problem hiding this comment.
What is VoP? Can you add an explanation?
There was a problem hiding this comment.
VoP means Value of Production (the part not covered by MAgPIE comes from wool, beeswax, honey, silk-worms)
| p36_hourly_costs_increase(iso) Difference between minimum hourly labor costs and actual hourly labor costs in 2050 (USDMER05 per hour) | ||
| p36_hourly_costs_iso(t,iso) Hourly labor costs in agriculture on iso level after including minimum wage (USDMER05 per hour) | ||
| pm_hourly_costs_baseline(t,i) Hourly labor costs in agriculture on regional level (USDMER05 per hour) | ||
| pm_hourly_costs(t,i) Hourly labor costs in agriculture on regional level after including minimum wage (USDMER05 per hour) |
There was a problem hiding this comment.
These two new interfaces are very similar and also have the same unit.
Therefore, you could merge these into one interface with a set for distinction between baseline and minimum wage scenario.
@tscheypidi What do you suggest?
There was a problem hiding this comment.
I agree, that should be merged into one parameter
There was a problem hiding this comment.
done (also for p36_hourly_costs_iso)
| @@ -859,6 +859,16 @@ cfg$gms$s35_hvarea <- 0 # def = 0 | |||
| # * optimization | |||
| cfg$gms$employment <- "exo_may22" # default = "exo_may22" | |||
|
|
|||
| # * global minimum wage that needs to reached in all countries by 2050 | |||
| cfg$gms$s36_minimum_wage <- 0 # default = 0 (no minimum wage) | |||
There was a problem hiding this comment.
is that a binary 1/0 switch or does it have a unit?
There was a problem hiding this comment.
it's a USD/h value, I added the unit in the description
| p36_hourly_costs_increase(iso) Difference between minimum hourly labor costs and actual hourly labor costs in 2050 (USDMER05 per hour) | ||
| p36_hourly_costs_iso(t,iso) Hourly labor costs in agriculture on iso level after including minimum wage (USDMER05 per hour) | ||
| pm_hourly_costs_baseline(t,i) Hourly labor costs in agriculture on regional level (USDMER05 per hour) | ||
| pm_hourly_costs(t,i) Hourly labor costs in agriculture on regional level after including minimum wage (USDMER05 per hour) |
There was a problem hiding this comment.
I agree, that should be merged into one parameter
| p36_hourly_costs_iso(t,iso) Hourly labor costs in agriculture on iso level after including minimum wage (USDMER05 per hour) | ||
| pm_hourly_costs_baseline(t,i) Hourly labor costs in agriculture on regional level (USDMER05 per hour) | ||
| pm_hourly_costs(t,i) Hourly labor costs in agriculture on regional level after including minimum wage (USDMER05 per hour) | ||
| pm_labor_cost_scaling(t,i) Multiplicative factor describing increase in hourly labor costs to match minimum wage (1) |
There was a problem hiding this comment.
why is that interface needed? I would have thought that if you provide the hourly costs to the modules they should be able to compute the respective labor costs? Isn't it possible that the modules compute the required working hours and then base their calculations on pm_hourly_costs (diving the given labor costs by hourly costs should give the hours one should start with)
There was a problem hiding this comment.
the switch s36_scale_productivity_with_wage can now take any positive value which defines how strongly labor productivity should be affected by higher wages (instead of being a binary switch). The new interface is pm_productivity_gain_from_wages which replaces the interface pm_labor_cost_scaling
| *' average hours worked per employed person per year. Total labor costs include | ||
| *' labor costs from crop production (see [38_factor_costs]) and livestock production | ||
| *' (see [70_livestock]), and some labor costs for crop and livestock production | ||
| *' which are not covered by MAgPIE. |
There was a problem hiding this comment.
Github is complaining here and in some other spots about missing newlines. Perhaps you can check why this is happening (might be coming from the text editor you use)
There was a problem hiding this comment.
I don't see any complains in the updated files, either I'm not looking for the right thing, or I already fixed them unknowingly with the other changes...
deleip
dismissed
bodirsky’s stale review
all requested changes have been addressed
🐦 Purpose of this PR 🐦
This PR introduces the option to include a global minimum wage set by
s36_minimum_wage, which can either lead to total labor costs being scaled accordingly (s36_scale_labor_costs <- 1), or it is assumed that productivity increases such that total labor costs stay the same (s36_scale_labor_costs <- 0).The 38_factor_costs realization "mixed_reg_feb17" was removed as it is not used anymore. In the realization
sticky_laborthe calibration of the share parameter was fixed, and the option to fix the capital need (i.e. not allowing for substitution between labor and capital) until a given years38_fix_capital_needwas introduced.🔧 Checklist for PR creator 🔧
📉 Performance loss/gain from current default behavior 📈
Added changes to
CHANGELOG.mdCompilation check (model starts without compilation errors - use
gams main.gms action=cin model folder for testing).No hard coded numbers and cluster/country/region names.
The new code doesn't contain declared but unused parameters or variables.
Where relevant, In-code comments added including documentation comments.
Made sure that documentation created with
goxygenis okay (usegoxygen::goxygen()for testing).Changes to
magpie4R library for post processing of model output (ideally backward compatible).Self-review of my own code.
For high risk runs: validation of major model indicators - Land-use, emissions, food prices, Tau. %Delete this line in case it is not a high risk run%
old default vs. new default
results of wage scenario (blue: no minimum wage, red: minimum wage without productivity gain and no labor/capital substitution, green: minimum wage without productivity gain but with labor/capital substitution, purple: minimum wage with higher labor productivity fully compensation higher labor costs, orange: minimum wage which leads to some productivity gains but not fully compensating the higher costs)
change in default sticky_labor behavior (due to updated calibration of the share parameter)
NA
🚨 Checklist for RSE reviewer 🚨
CHANGELOGis updated correctly🚨 Checklist for MAgPIE reviewer 🚨
CHANGELOGis updated correctly