-
Notifications
You must be signed in to change notification settings - Fork 66
CCPP Framework Meeting Minutes 2026 02 19
Courtney Peverley edited this page Feb 19, 2026
·
4 revisions
Attendees: Michael Kavulich, Dom Heinzeller, Jordan Powers, RhaeSung Kim, Cheryl Craig, Jesse Nusbaumer, Courtney Peverley
GitHub issues, PRs, discussions
- Nothing new!
-
New test to demonstrate GNU failure #689
- Associated issue: Unallocated fields passed into Group Caps #690
- PR Demonstrates test failure, but doesn't fix it yet
- DRAFT FOR DOM: Feature/capgen_for_fuji #718
- No new issues, PRs
- Issue backlog/triage
- Skipped any issues that have "post-capgen unification" label...we should review those at the appropriate time
- Convert old python strings to f-strings #501
- capgen: check handling of type attribute for ddts #516
-
Change constituent properties parsed from standard name? #534
- Label this "post-capgen unification"?
-
Update CCPP tech doc: schemes can currently have optional arguments in between regular arguments - follow up with moving opt args to the end #544
- Partially resolved, Mike will follow up with tech-doc update.
-
Add "number of instances" dimension to module-level variables to support multi-instance usage #561
- New names added to dictionary, but these changes haven't come in from NEPTUNE yet right?
- Add threading and multi-instance test for capgen (#721)
- GNU failure / ddt rework
- Courtney still working, has made forward progress on organizing the dictionaries/calling lists; now working on constituent indices
Backlog triage
- Convert old python strings to f-strings (#501)
- Has been partially done, needs someone’s time
- Check handling of type attribute for ddts (#516)
- Not a high priority, but probably should check what this behavior is doing
- Change constituent properties parsed from standard name (#534)
- Probably needs discussion in the future
- Might need to be discussed at same time as other constituent issues
- Michael added the “post-capgen-unification” label
- Update CCPP tech doc: schemes can currently have optional arguments in between regular arguments - follow up with moving opt argos to the end (#544)
- Unclear if this is necessary, it technically works because we always pass “var=var” into the function calls
- Michael to check the fortran standards; will close this issue (with no action) if we’re not explicitly breaking any fortran standards
- Add “number of instances” dimension to module-level variables to support multi-instance (#561)
- In progress - Steve & Dom; standard names are in place & Dom working on adding a test
NEXT MEETING
- We'll plan to meet in 3 weeks (unless something comes up and we need to meet next week)