Skip to content

CCPP Framework Meeting Minutes 2023 03 13

dustinswales edited this page Mar 13, 2023 · 2 revisions

Agenda


Attendees: Michael Kavulich,, Matthew Dawson, Dustin Swales, Jesse Nusbaumer, Jordan Powers, Ligia Bernardet, Dom Heinzeller, Grant Firl

GitHub issues/PRs

CCPP Framework

Standard names

New items for discussion

  • Item from Jesse
    • It looks like at least in the capgen version the CCPP error message variable ("errmsg") is coded to be exactly 512 characters long. Given that host models and physics schemes are likely to use the CCPP error message variable, does it make sense to make a new character "kind" parameter that sets the max error message length, that could then be "used" by host models and physics schemes to ensure there are no character length conflicts anywhere?

Updates from last time

Previous notes

Other business

Notes

Mike’s PR has been merged. Question from HAFS developer. Performance of auto-generated code? (This will be addressed by Dom later in the meeting.) Jesse, Are there timing tools in the framework? Ligia, not part of the physics, relies on the host. Dustin, not that I know of.
Mike opened new PR for framework unit-testing. Move to CI eventually. PR on standard-name change for geopotential height. No problems to report, moving along.

New Item from Jesse error-message in capgen to 500 characters. From Dom, just two changes https://github.com/NCAR/ccpp-framework/blob/main/src/ccpp_types.F90 https://github.com/NCAR/ccpp-framework/blob/main/src/ccpp_types.meta

Discussion from John Michalakes From Ligia, not resolved. How to go forward? Draft PR to open discussion. Dom and Dustin will look into this. Meet next week, 20th.

Timeline for next CCPP release (Ligia) Sometime during our next period of performance. SCM has some new features, and a UFS release is scheduled for this summer, so why not do a ccpp release too?

Code hacking #464. Question about how to “hack” the code auto generation. Dom answered with a solution.

Clone this wiki locally