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

Initialize crowndamage for Satellite Phenology mode #939

Merged
merged 1 commit into from
Nov 15, 2022

Conversation

glemieux
Copy link
Contributor

Description:

This PR addresses #937, which was discovered while investigating a separate issue using elm-fates on perlmutter. Note that the gnu compiler is the default compiler for perlmutter (intel is not available).

Collaborators:

@JessicaNeedham

Expectation of Answer Changes:

No changes expected

Checklist:

  • My change requires a change to the documentation.
  • I have updated the in-code documentation .AND. (the technical note .OR. the wiki) accordingly.
  • I have read the CONTRIBUTING document.
  • FATES PASS/FAIL regression tests were run
  • If answers were expected to change, evaluation was performed and provided

Test Results:

CTSM (or) E3SM (specify which) test hash-tag:

CTSM (or) E3SM (specify which) baseline hash-tag:

FATES baseline hash-tag:

Test Output:

@glemieux
Copy link
Contributor Author

All expected tests came back b4b on Cheyenne against fates-sci.1.60.0_api.24.1.0-ctsm5.1.dev112. I generated a new baseline from these tests as fates-sci.1.60.1_api.24.1.0-ctsm5.1.dev112.

Folder location: /glade/u/home/glemieux/scratch/ctsm-tests/tests_pr939

@glemieux
Copy link
Contributor Author

I also confirmed this works on perlmutter using the gnu compiler with satellite phenology mode:
/pscratch/sd/g/glemieux/e3sm-tests/pr939-satphen.fates.pm-cpu.gnu.C3c7d4fd8ef-F0445ecce

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.

2 participants