Skip to content

add iteration tracking parameters#2414

Merged
robertpietzcker merged 5 commits into
remindmodel:developfrom
robertpietzcker:2026-07_addTradeTracking
Jul 16, 2026
Merged

add iteration tracking parameters#2414
robertpietzcker merged 5 commits into
remindmodel:developfrom
robertpietzcker:2026-07_addTradeTracking

Conversation

@robertpietzcker

@robertpietzcker robertpietzcker commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Purpose of this PR

Add more parameters that track REMIND values over iterations (this time for edgeTransport and the CES tree / energy service demand). Also added _iter to a number of output parameters that were built to track variables over iterations.

Type of change

Parts concerned

  • ☑️ GAMS Code
  • ◻️ R-scripts
  • ◻️ Documentation (GAMS incode documentation, comments, tutorials)
  • ◻️ Input data / CES parameters
  • ◻️ Tests, CI/CD (continuous integration/deployment)
  • ◻️ Configuration (switches in main.gms, default.cfg, and scenario_config*.csv files)
  • ◻️ Other (please give a description)

Impact

  • ◻️ Bug fix
  • ☑️ Refactoring
  • ◻️ New feature
  • ◻️ Change of parameter values or input data (including CES parameters)
  • ◻️ Minor change (default scenarios show only small differences)
  • ◻️ Fundamental change of results of default scenarios

Checklist

Do not delete any line. Leave unfinished elements unchecked so others know how far along you are.
In the end all checkboxes must be ticked before you can merge
.

  • I executed the automated model tests (make test) after my final commit and all tests pass (FAIL 0)
  • I adjusted the reporting in remind2 if and where it was needed
  • I adjusted the madrat packages (mrremind and other packages involved) for input data generation if and where it was needed
  • My code follows the coding etiquette
  • I explained my changes within the PR, particularly in hard-to-understand areas
  • I checked that the in-code documentation is up-to-date
  • I adjusted forbiddenColumnNames in readCheckScenarioConfig.R in case the PR leads to deprecated switches
  • I updated the CHANGELOG.md correctly (added, changed, fixed, removed, input data/calibration)

Further information (optional)

  • Runs with these changes are here:
  • Comparison of results (what changes by this PR?): nothing - the PR simply adds some output parameters

@dklein-pik dklein-pik left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Needs changes. I'll come back in a minute.

@dklein-pik dklein-pik left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@robertpietzcker

Copy link
Copy Markdown
Contributor Author

Could you please update the names of

Thanks for catching this!

I had asked Leon if he uses these parameters in further scripts, but I hadn't thought of simply doing a "find in files" for the names.

Apologies!

@dklein-pik dklein-pik left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks!

@dklein-pik

Copy link
Copy Markdown
Contributor

Could you please update the names of

Thanks for catching this!

I had asked Leon if he uses these parameters in further scripts, but I hadn't thought of simply doing a "find in files" for the names.

Apologies!

In cases where you wonder if something is used somewhere else, I recommend reposearch o_vm_fuExtr_pebiolc on the cluster. That does not cover "private" scripts of course.

@robertpietzcker robertpietzcker merged commit a4a4614 into remindmodel:develop Jul 16, 2026
2 checks passed
@robertpietzcker robertpietzcker deleted the 2026-07_addTradeTracking branch July 16, 2026 16:17
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