Skip to content

Docs/post sync refresh - #62

Closed
mdrewbeyer wants to merge 4 commits into
devfrom
docs/post-sync-refresh
Closed

mdrewbeyer wants to merge 4 commits into
devfrom
docs/post-sync-refresh

Conversation

@mdrewbeyer

Copy link
Copy Markdown
Collaborator

Summary

Technical details

Implementation notes

Additional changes

Switches added/removed/changed

Issues resolved

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

Tag points of contact here if you would like additional review of the relevant parts of the model

mdrewbeyer and others added 4 commits September 30, 2026 16:30
… audit

Keep FIXED entries for RMI fixes still unfixed upstream at 2026.08.03 and
add one for the compare_cases.py 'Flexibly Sited Demand' slide. Drop
entries resolved by the sync (z90, z134) or no longer reachable (NY/CT
offshore-wind RPS, reeds_to_rev). Shorten entries that duplicate guidance
docs, correct stale upstream-status claims, and note issues that resolve
at the 2026.09.08 sync. Add entries for issues seen in post-sync runs:
outputs.h5 missing sets, operating reserves off by default, retail-rate
pandas-3 no-ops, and PRAS single-zone crash (moved from the deleted
SUBNATIONAL_REGION_SUPPORT.md, whose other issues are all resolved).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Fix the plantchar_gas Choices and fiona wheel claims, document the
undocumented divergences (cases_test.csv cells, zizmor comments,
.markdownlint.json, upstream special_keys lines), update the case list
after #55, note that 2026.09.08 carries upstream's own Error 579 fix, and
cut history that sync-log.md already records. Close done sync-log open
items and add the temp-august cleanup and next-target notes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Replace shifted line references with file and symbol names, update case
names removed in #55, flag that two-step figures carry the Texas->p59
load error, collapse passages duplicated in known-reeds-issues.md, fix
the cap_limit and copy_files.py descriptions, and correct stale pins and
facts in UV_MAMBA_GUIDE, GAMS_ERROR_579, reeds-data-sources and the CI
runbook.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Working uv docs-build command, docs/ paths for sources files, shorter
CEPM/ orientation, updated case and run references in preprocessing
READMEs, decisions README aligned with its template, and run_cepm.ps1
comments without stale line numbers or cleanup_level reasoning.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mdrewbeyer

Copy link
Copy Markdown
Collaborator Author

Superseded by PR63

@mdrewbeyer
mdrewbeyer deleted the docs/post-sync-refresh branch October 1, 2026 23:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant