Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Partition CCPP_data.F90 #2525

Open
dustinswales opened this issue Dec 3, 2024 · 0 comments
Open

Partition CCPP_data.F90 #2525

dustinswales opened this issue Dec 3, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request feature-MPAS Label to identify tasks associated with the MPAS dynamical core implementation

Comments

@dustinswales
Copy link
Collaborator

dustinswales commented Dec 3, 2024

Description

CCPP_data.F90 contains the declarations of the data-containers. To accommodate additional dynamical cores, there is a need (opportunity!) to refactor of these typedefs (#2522), and consequentially the CCPP_data module will need to reflect those changes. This module is small, and any changes made to accomplish #2522 will need to be made simultaneously in CCPP_data.F90.

Solution

This module could be abstracted to contain either FV3 or MPAS typedefs, where the UWM supplies a pre-processor directive to control the dynamic core choice. Another option is for each dynamical-core could have its own CCPP_data.F90 module, analogous to what is proposed to the ccpp_prebuild_config.py (#2518)

@dustinswales dustinswales self-assigned this Dec 3, 2024
@dustinswales dustinswales added enhancement New feature or request feature-MPAS Label to identify tasks associated with the MPAS dynamical core implementation labels Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request feature-MPAS Label to identify tasks associated with the MPAS dynamical core implementation
Projects
Development

No branches or pull requests

1 participant