ccpp_fortran_to_metadata.py errors out when given a file that has a constituent properties object #643
Assignees
Labels
bug
For issues describing bugs, or PRs fixing bugs
Comments
mkavulich
pushed a commit
that referenced
this issue
Mar 3, 2025
Add options for pre-registered DDT names Add an option for pre-registered DDT names Add `ccpp_constituent_prop_ptr_t` as a default (pre-registered) DDT Add test for 'unknown' DDT variables User interface changes?: Yes Added a new option, `--ddt-names`, to allow users to simply add DDT names that allow generation of a CCPP metadata template from a Fortran source. Because it is an option, it is backwards compatible. Fixes: #643 ccpp_fortran_to_metadata.py errors out when given a file that has a constituent properties object Testing: test removed: None unit tests: NA system tests: NA manual testing: Added a manual test that tests this bug fix --------- Co-authored-by: Steve Goldhaber <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When run ccpp_fortran_to_metadata.py with a Fortran module which contains the constituent properties object, the python script errors out with the following error:
const_props: 'ccpp_constituent_prop_ptr_t' is not a valid derived Fortran type, at /home/cacraig/cam_sima_dme/src/physics/ncar_ccpp/schemes/conservation_adjust/dme_adjust/physics_dme_adjust.F90:52Steps to Reproduce
Provide the tag or hash of the CCPP Framework used to reproduce the bug
Have you make any modifications to the CCPP Framework code?
Please provide detailed steps for reproducing the issue.
ccpp_constituent_prop_ptr_tin the calling listThe text was updated successfully, but these errors were encountered: