[patrickbrown4]

Summary

Kestrel has updated from Red Hat Enterprise Linux 8 (RHEL8) to RHEL9; details are available at https://natlabrockies.github.io/HPC/RHEL9_upgrade/. This PR makes a few necessary changes for the new OS.

Necessary steps for internal lab users on kestrel

1. From now on, ssh into the kl3.hpc.nlr.gov node instead of kestrel.hpc.nlr.gov, kl1.hpc.nlr.gov, or kl2.hpc.nlr.gov (docs)
2. Remove the old reeds conda environment: conda env remove --name reeds (say yes to all prompts)
   1. This step is important; it doesn't work if you just update geopandas without rebuilding the whole environment from scratch
3. Rebuild the environment using the environment.yml file from this branch: conda env create -f environment.yml

Incompatibilities

Existing Julia instances with the old Manifest.toml still work, but new instantiations will fail. The Project.toml will be updated as part of #257. Until then, hold onto your Manifest.tomls.

Technical details

Implementation notes

• The NREL_CLUSTER environment variable has been changed to NLR_CLUSTER. We used it in many places, so I moved all that functionality to reeds.slurm.get_cluster() to make it easier to update in the future.
  • I also removed the need for a REEDS_USE_SLURM environment variable as it doesn't seem necessary
  • Also removed the old references to eagle

Relevant sources or documentation

https://natlabrockies.github.io/HPC/RHEL9_upgrade/

Validation, testing, and comparison report(s)

Here's a comparison for the USA_defaults case; changes are within the noise: results-v20261017_mainK0_USA_defaults,v20261020_rhel9K6_USA_defaults.pptx

Checklist for author

Details to double-check

• Charge code provided to reviewers
• Included comparison reports for appropriate test cases
• Code formatting standardized
• Reusable functions used where possible instead of copy/pasted code

General information to guide review

• Near-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

No

[cavraam]

The PR looks great, thank you for the prompt response here @patrickbrown4!

Approved, provided that pending runs complete; very minor comments/questions attached.

I wonder if the runs will reveal additional minor edits related to reporting (I don't think we have hpc-related scripts for reporting though...)

[cavraam]

curious why we might need this...

[patrickbrown4]

Until we address #4 we have to add the parent of the reeds module folder to the path so it can be imported locally. We didn't use the reeds module in this script before, but now we need it for reeds.slurm.check_slurm() below.

[cavraam]

Great to have this defined in only one spot and call if needed