Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the call to SatellitePhenology when fates is active #5345

Merged
merged 2 commits into from
Dec 15, 2022

Conversation

glemieux
Copy link
Contributor

@glemieux glemieux commented Dec 1, 2022

Move the fates-specific satellitephenology call out of an area that is unreachable when fates is active.

Fixes NGEET/fates#953.

[Non-B4B]

@glemieux
Copy link
Contributor Author

glemieux commented Dec 2, 2022

Perlmutter E3SM land developer tests against master baseline are complete (I merged master into this branch locally, but did not push). All but 2 tests are b4b. One DIFF in the fates satphen test as expected. The test with the hcru_hcru resolution failed to run however. The testlog had an error I wasn't familiar with:

 ---------------------------------------------------
2022-12-01 15:20:17: OLD FAIL: Potentially broken merges:
3b28b97f2f3ab181b1cdabf8d618256f2360f8e6
c0381621ba5653261e70edc1463bd17b7bc87d4a
 ---------------------------------------------------

Folder location on perlmutter: /global/homes/g/glemieux/pm-scratch/e3sm-tests/pr5345.fates.pm-cpu.gnu.Cb4cb329d34-Fdef6b3e7

@bishtgautam
Copy link
Contributor

@glemieux, I could not access the /global/homes/g/glemieux/pm-scratch/e3sm-tests/pr5345.fates.pm-cpu.gnu.Cb4cb329d34-Fdef6b3e7. Btw, instead of merging master locally, you can rebase your branch off the latest master before testing.

@glemieux
Copy link
Contributor Author

glemieux commented Dec 5, 2022

Sorry about that @bishtgautam; I've opened up all the folders in my scratch directory to be readable by all now. Thanks.

@glemieux
Copy link
Contributor Author

glemieux commented Dec 7, 2022

Upon a resubmit the hrcu_hrcu test that failed to RUN is passing now.

Copy link
Contributor

@rgknox rgknox left a comment

Choose a reason for hiding this comment

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

good stuff, thanks @glemieux

bishtgautam added a commit that referenced this pull request Dec 14, 2022
…ext (PR #5345)

Move the fates-specific `satellitephenology` call out of an area that is unreachable when `fates` is active.

Fixes NGEET/fates#953.

[Non-B4B]
@bishtgautam
Copy link
Contributor

This PR is now merged to next. A minor comment regarding renaming your future branches: E3SM is following the following naming convention: <username/component-name/short-useful-name>. So, this branch could be named <glemieux/lnd/fates-satphen-mode>.

@glemieux
Copy link
Contributor Author

This PR is now merged to next. A minor comment regarding renaming your future branches: E3SM is following the following naming convention: <username/component-name/short-useful-name>. So, this branch could be named <glemieux/lnd/fates-satphen-mode>.

Thanks for the reminder @bishtgautam

@bishtgautam bishtgautam merged commit 83d265b into E3SM-Project:master Dec 15, 2022
@glemieux glemieux deleted the fates-satphen-call-fix branch January 23, 2024 23:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SP-mode not working as it should in ELM-FATES
4 participants