Remove optional arguments from CCPP framework/metadata #415
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR removes invalid
optional
andintent
attributes from the CCPP metadata inGFS_typedefs.meta
. Metadata for variable/derived data type definitions do not use these attributes (they do not make sense there), only CCPP schemes use(d) them.Submodule pointers for ccpp-framework and ccpp-physics are updated to remove support the
optional
attribute in the CCPP framework/metadata. The implementation ofoptional
in CCPP was always flaky and we now have a better way to deal with potentially unallocated variables (active
attribute).Issue(s) addressed
Fixes NCAR/ccpp-framework#407
Testing
For regression testing with the UFS, see ufs-community/ufs-weather-model#887.
Dependencies
NCAR/ccpp-framework#408
earth-system-radiation/rte-rrtmgp#143
NCAR/ccpp-physics#763
#415
ufs-community/ufs-weather-model#887
Associated SCM PR: MISSING