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
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