Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug] Stress period climate adjustment factors are not ingested/applied to data

Open
#116 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

This issue has not been assessed yet.

Description

bug TODO
Summary

When running ReEDS with climate impacts to hydropower or cooling water turned ON (i.e. GSw_ClimateHydro == 1 and/or GSwClimateWater == 1), climate adjustment factors for hydropower capacity factors and unappropriated freshwater seasonal distribution factors are not being read and applied for the stress periods.

Details:

The files not being read in and applied are the versions of climate_hydadjsea.csv and climate_UnappWaterSeaAnnDistr.csv found in the stress period folders of a ReEDS run (inputs_case/stress{model_year}i{iteration}). These files contain the stress-period values of the respective data they represent, and thus, should be read in alongside the representative period versions of the file, similar to cf_hyd and other similar parameters in 2_temporal_params.gms

https://github.com/ReEDS-Model/ReEDS/blob/62e69486acf4d32321667309b0dfb6432c884f8a/reeds/core/solve/2_temporal_params.gms#L462-L494

In the above example, without stress period data in the climate_hydro_seasonal parameter, Lines 490-491 calculates the non-dispatchable stress period data in cf_hyd as 0 for all years after the GSw_ClimateStartYear designation (see screenshot of inputs.gdx below):

Image
Solution (ToDo):
  • Adjust 2_temporal_params.gms to read in both versions of the climate_{hydadjsea|UnappWaterSeaAnnDistr}.csv from the inputs/{temporal_inputs|stress}/ folders.
    • Change climate_hydro_seasonal and watsa_climate from a GAMS table to parameter (required for multi-source parameter definition)
    • Fix reeds/input_processing/hourly_writetimeseries.py to output climate_hydadjsea.csv and climate_UnappWaterSeaAnnDistr.csv in long format with * appended to front of first column name
Dominant language
Python
Stars
38
Forks
18
Avg merge
3d 15h
Merged PRs (30d)
12

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ReEDS-Model/ReEDS

All issues in ReEDS-Model/ReEDS

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.