Post capgen v1 unification: recreate CCPP variable tracker and add debugging feature
@climbfuji is already working on this.
Since Jul 17, 2026.
- Dominant language
- Python
- Stars
- 25
- Forks
- 67
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 2
Description
Description
The CCPP variable tracker for ccpp-prebuild hasn't been ported to ccpp-capgen v1 yet.
Also, the previously used GFS_debug CCPP scheme in prebuild, which was hardcoded to the GFS DDTs and cumbersome to maintain, was retired.
Solution
We should recreate the CCPP variable tracker for ccpp-capgen-v1 and also think about a framework-side solution that provides similar or better debugging capabilities than the old GFS_debug scheme. @climbfuji experimented with this when tracking bit-for-bit differences for one of the CAM-SIMA regression tests.
Alternatives (optional)
Retire CCPP variable tracker - did anyone really use it?
Don't provide debugging capabilities, use add-hoc debugging print statements if needed. This will hurt us.
Related to (optional)
n/a
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.