-
Notifications
You must be signed in to change notification settings - Fork 64
CCPP Framework Meeting Minutes 2025 02 13
Courtney Peverley edited this page Feb 13, 2025
·
4 revisions
Attendees: Michael Kavulich, Michael Waxmonsky, Jordan Powers, Brian Dobbins, Cheryl Craig, RhasSung Kim, Courtney Peverley, Dom Heinzeller, Soren Rasmussen
CCPP Framework (issues, PRs, discussions)
-
Enable multiple schemes to use the same local name for different variables #621
- Any updates?
-
- Approved, but still unresolved comments.
-
Sub-cycling not working properly Issue#632, Suite-part list is wrong Issue#634
-
Capgen in SCM: Fix to allow for scheme subcycling. #633
- Ready for review!
-
Capgen in SCM: Fix to allow for scheme subcycling. #633
-
Allow for differing module/file names Issue#636
-
Capgen in SCM: Differing source and module name #637
- Approved, but needs updates. Did anyone else want to review?
-
Capgen in SCM: Differing source and module name #637
-
- Continued updates and discussion
Standard names (issues, PRs, discussions)
-
- Merged.
-
- Still need some discussion
Brian Dobbins has started testing the Intel compiler limit problem, and will be attending the beginning of the meeting, so it might be good to discuss this issue first if possible.
Updated branch rules:
- For
main
, Added "Dismiss stale pull request approvals when new commits are pushed" and increased number of required reviews to 3 (to match number of regtests) - For
develop
, Added "Require linear history" (which prevents merge commits to that branch specifically). This allows me to re-enable merge commits as an option, but creates a potentially confusing message on PRs where merge commit is the default.
Offer suggestions/comments on development workflow rules:
- Latest updates were applied: https://github.com/NCAR/ccpp-framework/wiki/Development-Workflow
- New comments and suggestions here: https://docs.google.com/document/d/1iMh_iKsUrB_mOMF6lGkFggG85JV62NFkTjKJboqWvV8/edit?tab=t.0
CCPP Framework
- #633 and #637 are ready for review!
- Michael W to open issue for bug in comparing fortran vs metadata local names for host variables
Standard Names
- Michael K to rename to ESMStandardNames TODAY!
Discussion
-
255 arguments issue with intel
- It’s not a hard limit on arguments, but a hard limit on “specification expressions”
- E.g. array bounds
- Documentation here
- Brian D wants more info on what’s causing the problem for Dustin, maybe an example
- Soren: Dustin’s example wouldn’t work even after messing with flags a bit
- ccpp_SCM_GFS_v17_p8_ugwpv1
- Are we explicitly passing array bounds? If so, that’s likely the problem
- Dom - need to subset chunks of array for things like radiation
- Need to know if capgen is subsetting at the group level or scheme level
- Courtney to look into how capgen handles this/get the example from Dustin/Soren
- Brian’s analysis of physics meta data
- It’s not a hard limit on arguments, but a hard limit on “specification expressions”
- Next week’s meeting will be in-person in the Mesa Lab for those in the area