The framework should be able to compare array dimensions in the auto-generated caps between the actual size of the arrays and the size inferred from the dimensions in the metadata.
Solution
These comparisons will be slowing down the code and therefore should only be activated when an appropriate --debug flag (or similar) is provided on the command line. Arrays that are not "active" (i.e. whose active attribute evaluates to .false.) must be skipped.
This solution will be implemented first in ccpp_prebuild.py (see https://github.com/NCAR/ccpp-framework/issues/405) and later in capgen.py. Note that it can but doesn't have to be in place at the time of transitioning from ccpp_prebuild.py to capgen.py. It will require the var_action class to be implemented in capgen.py.
Description
The framework should be able to compare array dimensions in the auto-generated caps between the actual size of the arrays and the size inferred from the dimensions in the metadata.
Solution
These comparisons will be slowing down the code and therefore should only be activated when an appropriate
--debug
flag (or similar) is provided on the command line. Arrays that are not "active" (i.e. whoseactive
attribute evaluates to.false.
) must be skipped.This solution will be implemented first in
ccpp_prebuild.py
(see https://github.com/NCAR/ccpp-framework/issues/405) and later incapgen.py
. Note that it can but doesn't have to be in place at the time of transitioning fromccpp_prebuild.py
tocapgen.py
. It will require thevar_action
class to be implemented incapgen.py
.