Skip to content

New shared module for functions used in both DynCore and AdvCore - #413

Open
lizziel wants to merge 3 commits into
GEOS-ESM:release/MAPL-v3from
geoschem:ewlundgr/refactor_DynCore_functions_used_in_AdvCore
Open

New shared module for functions used in both DynCore and AdvCore#413
lizziel wants to merge 3 commits into
GEOS-ESM:release/MAPL-v3from
geoschem:ewlundgr/refactor_DynCore_functions_used_in_AdvCore

Conversation

@lizziel

@lizziel lizziel commented Jul 21, 2026

Copy link
Copy Markdown

This update moves the functions defined in DynCore but used in both DynCore and AdvCore to a new file. This allows skipping the build of DynCore and some of its dependencies in GCHP, which only uses AdvCore. I also added access declarations to jw and sw fortran files, and generally cleaned up the formatting in those files.

@lizziel
lizziel requested review from a team as code owners July 21, 2026 14:40
This enables not building DynCore in models that only use AdvCore

Signed-off-by: Lizzie Lundgren <elundgren@seas.harvard.edu>
@lizziel
lizziel force-pushed the ewlundgr/refactor_DynCore_functions_used_in_AdvCore branch from 20df9e5 to 1e11d2f Compare July 21, 2026 14:43
@pchakraborty pchakraborty added 0 diff The changes in this pull request have verified to be zero-diff with the target branch. MAPL3 MAPL 3 Related Skip Changelog labels Jul 21, 2026

@pchakraborty pchakraborty left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, but we will need the CI to run first. I have triggered the CI tests, and will check back later to see if they passed.

@pchakraborty pchakraborty left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Our general convention is to make everything private by default and explicitly mark the routines as public

Comment thread fv_shared.F90
New additions to the file will not be private unless
explicitly declared as public

Signed-off-by: Lizzie Lundgren <elundgren@seas.harvard.edu>
@lizziel

lizziel commented Jul 21, 2026

Copy link
Copy Markdown
Author

@pchakraborty, I pushed the update to declare private by default, and public for the existing functions. Heads up this convention needs to be applied to several other existing files in the repo.

@mathomp4

Copy link
Copy Markdown
Member

@lizziel Can you maybe make a trivial commit somewhere and re-push. CircleCI wasn't set up to handle forks. I think I toggled something to allow it, but I can't figure out how to have it see your branch.

I'm hoping a trivial commit like, I dunno, turning IMPLICIT NONE to implicit none in fv_shared.F90 and pushing will now trigger the CI.

Signed-off-by: Lizzie Lundgren <elundgren@seas.harvard.edu>
@lizziel

lizziel commented Jul 21, 2026

Copy link
Copy Markdown
Author

Okay, I pushed some no diff changes. They go a bit off-topic of the PR, by declaring access in existing files jw.f90 and sw.f90. But this was a natural next step based on @pchakraborty's comment about standard convention for access declaration.

@mathomp4

Copy link
Copy Markdown
Member

Yay. CircleCI ran. I forgot I need to approve the GitHub Actions. Weirdly, I can't figure out how to do the same with CircleCI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

0 diff The changes in this pull request have verified to be zero-diff with the target branch. MAPL3 MAPL 3 Related Skip Changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants