Skip to content

build(fates): Add dynamic HLM_ROOT configuration for standalone FATES builds - #1605

Draft
johnpaulalex wants to merge 2 commits into
NGEET:mainfrom
johnpaulalex:build/standalone-support
Draft

johnpaulalex wants to merge 2 commits into
NGEET:mainfrom
johnpaulalex:build/standalone-support

Conversation

@johnpaulalex

@johnpaulalex johnpaulalex commented Aug 12, 2026 •

Copy link
Copy Markdown
Contributor

Description:

This change enhances CMake configuration and Python test suite path resolution to support building and testing FATES in standalone repository setups. HLM_ROOT path determination in CMakeLists.txt and CIME path resolution in testing/framework/utils/path.py now support an optional HLM_ROOT environment variable, falling back gracefully to the standard nested directory layout.

This allows both development scenarios:

  1. Editing a standalone FATES repository with the CTSM repository elsewhere: Set the HLM_ROOT environment variable to point to the host model / CTSM installation directory.
  2. Editing a FATES repository inside a CTSM repository: Do not set HLM_ROOT (the default fallback path logic automatically locates the host model / CIME directory relative to the FATES root).

Specific notes

Collaborators:

Parent PR (if stacked on a parent branch):

  • None

Linked issues addressed, if any:

  • None

Expectation of Answer Changes:

  • Bit-for-Bit (B4B) with baseline master
  • Roundoff-level differences only
  • Expected Answer Changes (ECA)

Description of generative AI usage (as necessary)

Google Antigravity was used to write the code and tests, followed by human-guided verification.

Checklist

Contributor

  • The in-code documentation has been updated with descriptive comments
  • The documentation has been assessed to determine if updates are necessary
  • Describe use of generative AI (if necessary)

Integrator

  • FATES PASS/FAIL regression tests were run
  • Evaluation of test results for answer changes was performed and results provided
  • FATES-CLM6 Code Freeze: satellite phenology regression tests are b4b

Test Results:

CTSM (or) E3SM (specify which) test hash-tag: N/A
CTSM (or) E3SM (specify which) baseline hash-tag: N/A
FATES baseline hash-tag: 093b4f46

Test Output:
[x] Executed pFUnit / CIME regression tests

@glemieux

Copy link
Copy Markdown
Contributor

@johnpaulalex was this test on derecho wrt to the b4b designation?

@johnpaulalex

Copy link
Copy Markdown
Contributor Author

Hey @glemieux , I didn't run any tests, but I marked b4b because it's just choosing the right paths to do the compilation. Is that misleading?

@glemieux

Copy link
Copy Markdown
Contributor

Hey @glemieux , I didn't run any tests, but I marked b4b because it's just choosing the right paths to do the compilation. Is that misleading?

@johnpaulalex it's not misleading because its under the "expectation ..." heading. I just wanted to double check since I thought I remembered you getting access to derecho.

@rgknox rgknox added the uncategorized Has not experienced any intake or triage from integrators. label Sep 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

uncategorized Has not experienced any intake or triage from integrators.

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

3 participants