-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Managed pastures tau #372
Managed pastures tau #372
Conversation
CHANGELOG.md
Outdated
|
||
### added | ||
- **tc** added new set 'tautype' spliting tau between croplands and managed pastures; New input file f13_pastr_tau_hist.csv |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is not very clear to me (only by seeing the changelog) the role of the .csv file (also for the parameters and .cs3 in land). You could instead add a brief description of it? Something like: new input file which contains historical tc for pasture.
config/default.cfg
Outdated
@@ -49,7 +49,8 @@ cfg$input <- c(regional = "rev4.67_h12_magpie.tgz", | |||
#below it will get merged into cfg$repositories | |||
|
|||
cfg$repositories <- append(list("https://rse.pik-potsdam.de/data/magpie/public"=NULL), | |||
getOption("magpie_repos")) | |||
getOption("magpie_repos")) | |||
# list("C:/magpie_inputdata/output"=NULL)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commented line is maybe coming from a merge?
pc13_tcguess(h) Guess for annual tc rates in the next time step (1) | ||
i13_tc_factor(t) Regression factor (USD05PPP per ha) | ||
i13_tc_exponent(t) Regression exponent (1) | ||
pc13_land(i, tautype) Crop land area per region (mio ha) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Description change, Now it includes pasture as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great to see this development moving!
Just for clarification. With this PR you add data sets and dimensions for managed pasture. But these additions are not yet used, right?
For instance, pasture is not yet split and pasture yields are not yet changed. Is that correct?
If I'm not mistaken vm_tau(i,"pastr") is currently a free variable.
Hi Florian! Yes, I am splitting the whole implementation into chunks. This is the first chunk of code, so vm_tau(i, "past") is still not engaged in any other module. It will be once all the other parts are put together! So, for this PR no significant changes in model behaviors are expected. |
@@ -16,7 +16,7 @@ | |||
+ vm_cost_inv(i2) | |||
+ sum((cell(i2,j2),land), vm_cost_landcon(j2,land)) | |||
+ sum((cell(i2,j2),k), vm_cost_transp(j2,k)) | |||
+ vm_tech_cost(i2) | |||
+ sum(tautype, vm_tech_cost(i2,tautype)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't do that. You will introduce various compatibility issues by changing the declaration of an interface. You can instead sum up the costs within the tc module and leave the vm_tech_cost
interface untouched
v13_cost_tc(i) Technical change costs per region (mio. USD05PPP) | ||
vm_tau(h,tautype) Agricultural land use intensity tau (1) | ||
vm_tech_cost(i,tautype) Annuitized costs of TC (mio. USD05PPP per yr) | ||
v13_cost_tc(i,tautype) Technical change costs per region (mio. USD05PPP) | ||
; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
your implementation is completely different to what is there so far. Hence, you need to create a new realization and do your changes in this new realization.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and try to reduce your changes in the interfaces! Changing interfaces will introduce a lot of work, e.g. a lot of changes in the magpie4
package and so on
@@ -9,6 +9,7 @@ | |||
parameters | |||
pm_land_start(j,land) Land initialization area (mio. ha) | |||
pcm_land(j,land) Land area in previous time step (mio. ha) | |||
pcm_grass(j,grassland) Grassland areas in previous time step (mio. ha) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think that you need that additional interface...in the tc module you could use pcm_land("past")
instead even so it has a slightly different meaning
🐦 Purpose of this PR 🐦
🔧 Checklist for PR creator 🔧
📉 Performance loss/gain from current default behavior 📈
Added changes to
CHANGELOG.md
Compilation check (model starts without compilation errors - use
gams main.gms action=c
in 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
goxygen
is okay (usegoxygen::goxygen()
for testing).Changes to
magpie4
R 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%
NA
🚨 Checklist for RSE reviewer 🚨
CHANGELOG
is updated correctly🚨 Checklist for MAgPIE reviewer 🚨
CHANGELOG
is updated correctly