Skip to content

ctsm5.4.034: bug fix to the FATES land use driver input code#3902

Merged
adrifoster merged 5 commits intoESCOMP:masterfrom
adrifoster:landuse_driver_bugfix
Apr 22, 2026
Merged

ctsm5.4.034: bug fix to the FATES land use driver input code#3902
adrifoster merged 5 commits intoESCOMP:masterfrom
adrifoster:landuse_driver_bugfix

Conversation

@adrifoster
Copy link
Copy Markdown
Contributor

@adrifoster adrifoster commented Apr 1, 2026

Description of changes

This PR includes a cherry-picked fix from NorESMhub/CTSM #209 to address swap in the order of rangeland and pasture in the reading of the landuse drivers.

Specific notes

Contributors other than yourself, if any: @rosiealice

Are answers expected to change (and if so in what way)? Yes - for FATES land use runs

Any User Interface Changes (namelist or namelist defaults changes)? No

Does this create a need to change or add documentation? Did you do so? No

Testing performed, if any:

testing starting

@adrifoster adrifoster moved this to In progress - master in CTSM: Upcoming tags Apr 2, 2026
@adrifoster adrifoster changed the title bug fix to the land use driver inputs bug fix to the FATES land use driver inputs Apr 2, 2026
@adrifoster adrifoster changed the title bug fix to the FATES land use driver inputs bug fix to the FATES land use driver input code Apr 2, 2026
Copy link
Copy Markdown
Member

@samsrabin samsrabin left a comment

Choose a reason for hiding this comment

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

Nice

@samsrabin samsrabin added non-b4b Changes answers (incl. adding tests) test: aux_clm Pass aux_clm suite before merging test: fates Pass fates test suite before merging labels Apr 2, 2026
@samsrabin samsrabin changed the title bug fix to the FATES land use driver input code ctsm5.4.031: bug fix to the FATES land use driver input code Apr 2, 2026
@adrifoster
Copy link
Copy Markdown
Contributor Author

okay well it's hard to tell if this is working as intended because we don't have any LUH tests that don't die in the RUN phase?

@glemieux
Copy link
Copy Markdown
Contributor

glemieux commented Apr 9, 2026

okay well it's hard to tell if this is working as intended because we don't have any LUH tests that don't die in the RUN phase?

@adrifoster I talked about this with @ckoven yesterday. I could have a "quick" fix for this that would require an update to the LUH datasets and the FATES code. I'll start working on that; what do you think about holding on this until that's updated?

@samsrabin
Copy link
Copy Markdown
Member

That seems like a reasonable approach to me, especially considering the b4b-dev merge is supposed to happen today.

@rosiealice
Copy link
Copy Markdown
Contributor

Just to confirm that this code change is what we implemented in NorESM and that it's all working fine there. But agree that this might be a good reason to create the relevant working tests!

@glemieux
Copy link
Copy Markdown
Contributor

glemieux commented Apr 9, 2026

Just to confirm that this code change is what we implemented in NorESM and that it's all working fine there. But agree that this might be a good reason to create the relevant working tests!

@rosiealice @mvdebolskiy Do y'all run the tests are we see failing here: #3789 (comment)?

@mvdebolskiy
Copy link
Copy Markdown
Contributor

@glemieux no, we don't and the latest NorESM has not yet been updated to 5.4.030.

@samsrabin samsrabin changed the title ctsm5.4.031: bug fix to the FATES land use driver input code ctsm5.4.032: bug fix to the FATES land use driver input code Apr 9, 2026
@mvdebolskiy
Copy link
Copy Markdown
Contributor

@rosiealice it is fine only because we did not yet updated to sam's files.

@samsrabin samsrabin changed the title ctsm5.4.032: bug fix to the FATES land use driver input code ctsm5.4.033: bug fix to the FATES land use driver input code Apr 9, 2026
@samsrabin
Copy link
Copy Markdown
Member

This PR will come in after @glemieux fixes the FATES land use tests, which will happen in a separate master tag.

@samsrabin samsrabin changed the title ctsm5.4.033: bug fix to the FATES land use driver input code ctsm5.4.034: bug fix to the FATES land use driver input code Apr 10, 2026
@glemieux
Copy link
Copy Markdown
Contributor

The FATES-side fix appears to be working. I'll make the PR on the fates side for review and link it here.

@adrifoster
Copy link
Copy Markdown
Contributor Author

All tests have now passed or fail as expected.

@adrifoster adrifoster merged commit f426849 into ESCOMP:master Apr 22, 2026
4 checks passed
@github-project-automation github-project-automation Bot moved this from Final Testing to Ready to Integrate in FATES Pull Request Planning and Status Apr 22, 2026
@github-project-automation github-project-automation Bot moved this from In progress - master to Done (non release/external) in CTSM: Upcoming tags Apr 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

non-b4b Changes answers (incl. adding tests) PR status: needs testing test: aux_clm Pass aux_clm suite before merging test: fates Pass fates test suite before merging

Projects

Status: Done (non release/external)

Development

Successfully merging this pull request may close these issues.

6 participants