Skip to content
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

some updates from NGFS runs #1385

Merged
merged 1 commit into from
Oct 13, 2023
Merged

Conversation

orichters
Copy link
Contributor

@orichters orichters commented Aug 24, 2023

Purpose of this PR

some bug fixes and improvements copied from this branch.

  • With new NPi realization, 45/NDC module should now be run from 2025 onwards only.
  • Remove recalculation of 2020 values
  • add option to run netZero scenarios with 46/NDC module
  • start calculate 46 markups earlier to improve convergence

Type of change

  • Bug fix

Checklist:

  • My code follows the coding etiquette
  • I performed a self-review of my own code
  • I explained my changes within the PR, particularly in hard-to-understand areas
  • I checked that the in-code documentation is up-to-date
  • All automated model tests pass (FAIL 0 in the output of make test)
  • The changelog CHANGELOG.md has been updated correctly

@orichters orichters self-assigned this Aug 24, 2023
@orichters orichters marked this pull request as ready for review September 20, 2023 15:52
@@ -45,20 +45,20 @@ p45_factorRescaleCO2TaxLtd(p45_NDCyearSet(t,regi)) =
min(max(0.1**p45_adjustExponent, p45_factorRescaleCO2Tax(t,regi)), max(2-iteration.val/15,1.01-iteration.val/10000));
*** use max(0.1, ...) to make sure that negative emission values cause no problem, use +0.0001 such that net zero targets cause no problem

pm_taxCO2eq(t,regi)$(t.val gt 2016 AND t.val ge cm_startyear AND t.val le p45_lastNDCyear(regi)) = max(1* sm_DptCO2_2_TDpGtC,pm_taxCO2eq(t,regi) * p45_factorRescaleCO2TaxLtd(t,regi) );
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will this create problems if we have runs with cm_startyear = 2025 in two years?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, because then t = 2025, 2030, 2035 etc. We have to adjust that though once the NPi realization fixes the carbon prices for t = 2025, I think.

@orichters orichters merged commit 8a8eccb into remindmodel:develop Oct 13, 2023
1 check passed
@orichters orichters deleted the NGFSupdates2 branch December 6, 2023 14:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants