Skip to content

Move inputs documentation from sources.csv to inputs/*/README.md - #157

Merged
kennedy-mindermann merged 32 commits into
mainfrom
km/source-documentation
Aug 28, 2026
Merged

kennedy-mindermann merged 32 commits into
mainfrom
km/source-documentation

Conversation

@kennedy-mindermann

@kennedy-mindermann kennedy-mindermann commented Jul 23, 2026 •

Copy link
Copy Markdown
Contributor

Summary

This PR adds more inputs/*/README.md files and automatically compiles them into a single Inputs Documentation page. I removed all of the input files in sources.csv and added any information found there to the applicable README.md.

Since the documentation on the inputs is still pretty light, I also created this issue to cover filling in the documentation a bit more with this new structure: #156.

Technical details

The sources.csv file no longer contains any input files. It now only contains references to hourlize, postprocessing, and test files.

Implementation notes

Additional changes

Switches added/removed/changed

Issues resolved

Addresses the documentation reorganization mentioned in #43

Known incompatibilities

Relevant sources or documentation

Validation, testing, and comparison report(s)

I did a GDX diff between main and this branch for a USA default scenario and it showed no differences.

image

results-8_24_2026_sd_USA_defaults,8_24_2026_main_USA_defaults.pptx

Checklist for author

Details to double-check

  • Charge code provided to reviewers
  • Included comparison reports for appropriate test cases
  • Documentation updated if necessary
  • If input data added/modified:
    • Dollar year recorded and converted to 2004$ for GAMS
    • Timeseries are in Central Time
    • Units are specified
    • Preprocessing steps have been documented and committed to ReEDS_Input_Processing
    • New large data files handled with .h5 instead of .csv
    • If spatially resolved inputs are modified, the following visualizations for each file are included in the PR description (time-averaged if the inputs are time-resolved):
      • Map of absolute values before
      • Map of absolute values after
      • Map of differences: (after - before) or (after / before)
    • If entries are added/removed/changed in the EIA-NEMS unit database:
      • Changes have been committed to ReEDS_Input_Processing
      • hourlize/resource.py was rerun to regenerate the existing/prescribed VRE capacity data
  • Code formatting standardized
  • Reusable functions used where possible instead of copy/pasted code

General information to guide review

  • Zero impact on results of default case
  • No large data file(s) added/modified
  • No substantive impact on runtime for full-US reference case
  • No substantive impact on folder size for full-US reference case
  • No change to process flow (runreeds.py, reeds/core/solve/solve.py)
  • No change to code organization
  • No change to package requirements (environment.yml or Project.toml)

Did you use LLM tools (chatbot or copilot) in the preparation of this PR? If so, describe how

Yes, I used copilot to help me write the generate_inputs_markdown.py script.

Comment thread inputs/zones/README.md
@@ -1,4 +1,4 @@
# Model zone definitions
## Model Zone Definitions

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.

I use the markdownlint extension and it complains if the first line in the file is not a top-level heading (single #). Is it ok to stick with that format?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I think so, I had originally left them as single # but that prevents us from compiling into a single markdown file for the documentation unless we do some additional processing

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.

Oh I see, thanks. I can just turn off that rule if it complicates things (I'm not sure how widely that linter is used anyway).

@kennedy-mindermann
kennedy-mindermann marked this pull request as ready for review August 21, 2026 15:24
@pesap pesap mentioned this pull request Aug 21, 2026
7 tasks done

@wesleyjcole wesleyjcole 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.

developer_B]=best_practicies.md needs updated.

Would you update the PR description to note the revised scope of source.csv (non-inputs files only)? Or do you think it's worth removing all sources.csv entries in this PR?

Comment thread docs/scripts/generate_inputs_markdown.py Outdated
Comment thread docs/scripts/generate_inputs_markdown.py Outdated
Comment on lines +80 to +81
readmes = _collect_input_readmes(inputs_root)
_write_inputs_md(output_path, readmes)

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.

What do you think about bringing the function code down to here instead of keeping it above in the functions? That seems slightly more intuitive to me, but maybe there is a value to keeping it as a function?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I see value in keeping the main function smaller, and having this as a separate function makes it a little more digestible imo. Happy to reconsider if you feel strongly, but I'd lean toward leaving it separate.

Comment thread inputs/canada_imports/README.md Outdated
Comment thread inputs/capacity_exogenous/README.md Outdated
Comment thread inputs/sets/README.md Outdated
Comment thread reeds/input_processing/copy_files.py Outdated
return runfiles, non_region_files, region_files


def get_source_deflator_map(reeds_path):

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.

I think this function can now be removed.

Comment thread docs/sources_documentation.md Outdated

@patrickbrown4 patrickbrown4 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 a lot for starting this Kennedy. A few notes from a quick scan.

Comment thread docs/sources.csv

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.

I think this whole file could be removed now; it looks like most of the remaining entries are out of date anyway.

Comment thread inputs/canada_imports/README.md Outdated
Comment thread inputs/canada_imports/README.md Outdated
Comment thread inputs/consume/README.md Outdated
Comment thread inputs/canada_imports/README.md Outdated
Comment thread inputs/canada_imports/README.md Outdated

### Global Warming Potentials
A range of values for global warming potentials (GWP) of CH<sub>4</sub> and N<sub>2</sub>O are taken from the most recent IPCC assessment reports (AR4 to AR6). Summary of the ranges of GWPs for these pollutants can be found in Table 7.15, page 1017 of the IPCC AR6 report (https://www.ipcc.ch/report/ar6/wg1/downloads/report/IPCC_AR6_WGI_FullReport.pdf).
A range of values for global warming potentials (GWP) of CH<sub>4</sub> and N<sub>2</sub>O are taken from the most recent IPCC assessment reports (AR4 to AR6). Summary of the ranges of GWPs for these pollutants can be found in Table 7.15, page 1017 of the IPCC AR6 report ([https://www.ipcc.ch/report/ar6/wg1/downloads/report/IPCC_AR6_WGI_FullReport.pdf](https://www.ipcc.ch/report/ar6/wg1/downloads/report/IPCC_AR6_WGI_FullReport.pdf)).

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.

(nitpick) bare URLs can be given as a single <https://www.ipcc.ch/report/ar6/wg1/downloads/report/IPCC_AR6_WGI_FullReport.pdf> (with triangle brackets) instead of the two-part link

Comment on lines +115 to +135
- `ofs-wind_ATB_2023_*.csv`:
- `ofs-wind_ATB_2023_advanced.csv`: 2023 advanced ofs-wind capital, fixed O&M, var O&M costs and rsc_mult (SC cost reduction mult) by class and year
- `ofs-wind_ATB_2023_conservative.csv`: 2023 conservative ofs-wind capital, fixed O&M, var O&M costs and rsc_mult (SC cost reduction mult) by class and year
- `ofs-wind_ATB_2023_moderate.csv`: 2023 moderate ofs-wind capital, fixed O&M, var O&M costs and rsc_mult (SC cost reduction mult) by class and year
- `ofs-wind_ATB_2023_moderate_noFloating.csv`: 2023 moderate_noFloating ofs-wind capital (5x floating capital cost), fixed O&M, var O&M costs and rsc_mult (SC cost reduction mult) by class and year

- `ofs-wind_ATB_2024_*.csv`:
- `ofs-wind_ATB_2024_advanced.csv`:
- `ofs-wind_ATB_2024_conservative.csv`: 2024 conservative ofs-wind capital, fixed O&M, var O&M costs and rsc_mult (SC cost reduction mult) by class and year
- `ofs-wind_ATB_2024_moderate.csv`: 2024 moderate ofs-wind capital, fixed O&M, var O&M costs and rsc_mult (SC cost reduction mult) by class and year
- `ofs-wind_ATB_2024_moderate_noFloating.csv`: 2024 moderate_noFloating ofs-wind capital (5x floating capital cost), fixed O&M, var O&M costs and rsc_mult (SC cost reduction mult) by class and year

- `ons-wind_ATB_2023_*.csv`:
- `ons-wind_ATB_2023_advanced.csv`: Advanced cost and performance inputs from the 2023 Annual Technology Baseline for land-based wind
- `ons-wind_ATB_2023_conservative.csv`: Conservative cost and performance inputs from the 2023 Annual Technology Baseline for land-based wind
- `ons-wind_ATB_2023_moderate.csv`: Moderate cost and performance inputs from the 2023 Annual Technology Baseline for land-based wind

- `ons-wind_ATB_2024_*.csv`:
- `ons-wind_ATB_2024_advanced.csv`: Advanced cost and performance inputs from the 2024 Annual Technology Baseline for land-based wind
- `ons-wind_ATB_2024_conservative.csv`: Conservative cost and performance inputs from the 2024 Annual Technology Baseline for land-based wind
- `ons-wind_ATB_2024_moderate.csv`: Moderate cost and performance inputs from the 2024 Annual Technology Baseline for land-based wind

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.

I think a lot of things like these can be collapsed for readability, but it can happen in a followup

Comment thread inputs/sets/README.md Outdated
kennedy-mindermann and others added 7 commits August 27, 2026 10:29
Co-authored-by: Patrick Brown <25125211+patrickbrown4@users.noreply.github.com>
Co-authored-by: Patrick Brown <25125211+patrickbrown4@users.noreply.github.com>
Co-authored-by: Patrick Brown <25125211+patrickbrown4@users.noreply.github.com>
Co-authored-by: Patrick Brown <25125211+patrickbrown4@users.noreply.github.com>
Co-authored-by: Patrick Brown <25125211+patrickbrown4@users.noreply.github.com>
Co-authored-by: Patrick Brown <25125211+patrickbrown4@users.noreply.github.com>
@kennedy-mindermann
kennedy-mindermann merged commit 855ba2f into main Aug 28, 2026
10 checks passed
@kennedy-mindermann
kennedy-mindermann deleted the km/source-documentation branch August 28, 2026 15:47
@wesleyjcole wesleyjcole mentioned this pull request Aug 31, 2026
9 tasks done
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants