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

CCPP-physics Issue #127 Fix #517

Merged
merged 1 commit into from
Jan 11, 2024
Merged

Conversation

grantfirl
Copy link
Collaborator

@grantfirl grantfirl commented Dec 13, 2023

This PR is a bugfix for ufs-community/ccpp-physics#127

#503 was merged to fix the case when no scheme within a group has an init phase. A bug was introduced described in the ccpp-physics issue above. This fix ensures that the ccpp_t_instance variable is only passed once in the caps.

User interface changes?: No

Fixes:

ufs-community/ccpp-physics#127

Testing:
test removed:
unit tests:
system tests: tested with UFS RTs
RegressionTests_hera.log
Note that the CMEPS tests are still passing in particular.
manual testing: Tested with the SCM using the SDF supplied in ufs-community/ccpp-physics#127 with compilation and running. Also examined the produced caps to make sure the double cdata argument has been removed.

Copy link
Collaborator

@gold2718 gold2718 left a comment

Choose a reason for hiding this comment

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

Hope this fixes the issue without causing other issues 🤞

@grantfirl
Copy link
Collaborator Author

Hope this fixes the issue without causing other issues 🤞

Indeed. In retrospect, I got lucky (or unlucky?) in #503 that the local name for the ccpp_t type variable was consistent across the tiers of caps (suite and group caps). Otherwise, it wouldn't have worked to fix the original issue. I don't know what I was thinking adding the local name to the list of variables needed by the group caps when the framework should always be identifying variables by their standard name. Rookie mistake by me, for sure.

@climbfuji
Copy link
Collaborator

Hope this fixes the issue without causing other issues 🤞

Indeed. In retrospect, I got lucky (or unlucky?) in #503 that the local name for the ccpp_t type variable was consistent across the tiers of caps (suite and group caps). Otherwise, it wouldn't have worked to fix the original issue. I don't know what I was thinking adding the local name to the list of variables needed by the group caps when the framework should always be identifying variables by their standard name. Rookie mistake by me, for sure.

I reviewed and approved, so my bad too!

@mkavulich mkavulich merged commit 87c2b32 into NCAR:main Jan 11, 2024
1 check passed
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.

4 participants