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

Port surface radiative flux override capability #5

Merged
merged 2 commits into from
Nov 2, 2023

Conversation

spencerkclark
Copy link
Member

@spencerkclark spencerkclark commented Oct 12, 2023

This PR ports the ability to override the surface radiative fluxes seen by the land surface model from the wrapper. This was split across two PRs originally in the case of FV3GFS:

This depends on the fortran changes made in:

which have now been merged, and incorporated into this repo via #11.

Copy link

@frodre frodre left a comment

Choose a reason for hiding this comment

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

LGTM. Only thing I noticed is that the Fortran adjustments present in ai2cm/fv3gfs-fortran#158 are not linked to this PR for shield, so I assume the allocation changes are unnecessary or already exist over there?

@spencerkclark
Copy link
Member Author

Thanks @frodre, yup, that's correct, the fortran changes already exist. Those changes, which were made in upstream SHiELD repos, were merged yesterday, and #11 updated the submodules to include them in this repo. Sorry I should have made that clear in the PR description! Will edit it now.

@spencerkclark spencerkclark merged commit 18bcafe into main Nov 2, 2023
1 check passed
@spencerkclark spencerkclark deleted the override-radiative-fluxes branch November 2, 2023 21:10
spencerkclark added a commit that referenced this pull request Nov 3, 2023
This PR adds a dependabot configuration to track updates to the GFDL submodules contained in this repo. I have tried to configure it to check for updates to all the repos once a week, and if any are updated, open a PR updating them all as a group. The motivation behind this is that these repos are all interdependent, and so it is not uncommon for a change in one repo to require a change in another (and these updates are often made around the same time, e.g. the fortran changes required for #5).

Unfortunately I'm not sure there is a great way of testing this, so we may have to try it out and tweak things as we go.

Resolves #8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants