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

[kennedy-mindermann]

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

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)

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.

[patrickbrown4]

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?

[kennedy-mindermann]

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

[patrickbrown4]

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).