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 GFS_init.F90 #2524

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

Partition GFS_init.F90 #2524

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

GFS_init.F90 is responsible for reading in the physics namelist(s) and initializing the data containers used within the physics. This could be partitioned into dynamical core agnostic/specific pieces, which could be a single module guarded with dynamical core specific pre-processor directives (PPD), or into agnostic/specific modules.

Solution

One option, using the dycore pre-processor directives, MPAS and FV3, partition GFS_init into:
ccpp/driver/GFS_init.F90 - Common initialization + dycore specific initialization guarded by PPD
ccpp/driver/GFS_FV3_init.F90 - FV3 specific initialization imported
ccpp/driver/GFS_MPAS_init.F90 - MPAS specific initialization

@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

2 participants