Debugging capabilities for capgen v1
@climbfuji is already working on this.
Since Sep 10, 2026.
- Dominant language
- Python
- Stars
- 25
- Forks
- 67
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 2
Description
Description
ccpp-prebuild had a rudimentary way for debugging variables (GFS_debug.{F90,meta} scheme in CCPP physics). It relied on the GFS datatypes required manual updating every time these were modified.
The GFS debug schemes printed variable size/shapes, minval, maxval, and either sum or 32-bit Adler checksum. The latter was especially useful for tracking down the origin of b4b differences (growing noise).
This was never ported over to capgen v0.
We need something better than the old solution for capgen v1.
Solution
TBD - once implemented update the CCPP technical documentation.
Alternatives (optional)
Do nothing. Ask an LLM to create customized debugging code every time it's needed. Not great.
Related to (optional)
capgen unification - feature/capgen-v1
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.