-
Notifications
You must be signed in to change notification settings - Fork 64
CCPP Framework Meeting Minutes 2021 10 28
Dom Heinzeller edited this page Oct 27, 2021
·
6 revisions
- Transition to capgen.py
- Dropping support for optional arguments
- Dictionary of standard names
- Estimates of dedicated time needed to complete unification tasks added to GitHub issues
- Could use help to write unit tests that will pass once new capgen features are implemented (e.g., blocked data, unit conversion)
- Refactor capgen PR: https://github.com/NCAR/ccpp-framework/pull/410#event-5524461306
- Use flags to determine which branch to take in the code and whether to access certain variables (can be optional), instead of testing for presence
- Together with the
active
attribute and the extended usage ofpresent
in the Fortran 2008 standard, we do not need theoptional
attribute in the CCPP metadata - Fortran variables can still have the
optional
attribute (in the Fortran source code), presence of variable in CCPP metadata decides if the variable gets passed or not (i.e. at compile-time) - Remove optional attribute from CCPP framework (ccpp_prebuild) and ccpp-physics metadata
- Bug fix PRs that should be merged: "janic" --> "janjic" (https://github.com/ESCOMP/CCPPStandardNames/pull/23)
- Inconsistent standard names for vertical dimensions for radiation (issue https://github.com/ESCOMP/CCPPStandardNames/issues/24)
- We were encouraged to submit a full proposal for the CCPP surface composites work for the JTTI internal funding opportunity
- We got negative feedback for our LOI for the NOFO WPO JTTI proposal, which included the following features:
- finalize unification of CCPP framework between NOAA and NCAR
- surface composites (redundant with internal call)
- single precision physics
- NRL has created a single precision physics version based on CCPP v5, currently battling a few NaNs, PR will be created soon
- DTC will update the PR (which will be for v5) to the head of main
- From last week: We need a process to update the CCPP requirements (e.g. optional arguments, single precision, ...)
- Does this committee have the authority?
- Who should be involved to provide input, feedback, ...
- CCPP physics governance group must be included (scheme point of contacts / codeowners)
- In kind contributors should also have the right to comment on requirements, not only the funding agencies