GEOS-ESM / GEOS-ESM/GEOS_Util

Migrate use MAPL_ConstantsMod to use MAPL_Constants (MAPL3 compatibility)

Open
#191 0 comments 0 reactions 1 assignee View on GitHub

@mathomp4 is already working on this.

Since Mar 26, 2026.

MAPL3
Dominant language
Fortran
Stars
2
Forks
1
Avg merge
1d 2h
Merged PRs (30d)
10

Description

Background

MAPL3 has reorganized `shared/Constants` as part of GEOS-ESM/MAPL#4568 (issue #4567).

As part of that cleanup, the legacy alias module `MAPL_ConstantsMod` has been removed. The module naming convention in MAPL3 drops the `Mod` suffix from all module names.

Target branch

Changes should be made on the `release/MAPL-v3` branch of this repo.

Required change

All files that currently have:

```fortran
use MAPL_ConstantsMod
```

must be updated to:

```fortran
use MAPL_Constants
```

Note also that MAPL3 introduces descriptive aliases for the old cryptic constant names (e.g. `MAPL_GRAVITY` for `MAPL_GRAV`, `MAPL_DRY_AIR_GAS_CONSTANT` for `MAPL_RDRY`). The old names are retained as `! DEPRECATED` parameter aliases and will continue to work, but migrating to the descriptive names is encouraged.

Affected files (~15 found via code search)

  • `post/TEM.F90`
  • `post/stats.F90`
  • `post/rs_vinterp.F90`
  • `post/rs_vinterp_scm.F90`
  • `post/ec_prs2eta.F`
  • `post/ec_prs2fv.F`
  • `post/ec_eta2fv.F`
  • `post/era5_prs2eta.F`
  • `post/eta2prs.F`
  • `post/convert_eta.F`
  • `post/gg2eta.F`
  • `post/gg2fv.F`
  • `post/windfix.F`
  • `post/ncep_prs2fv.F`
  • `post/rsg3_vinterp.F`
  • `post/rs_hinterp.F`
  • `plots/zonal.f`

Timing

This change is required for MAPL3 compatibility. The MAPL PR (#4568) is currently labeled "contingent" pending this migration in downstream repos. A companion issue has been filed against GEOS-ESM/GEOSgcm_GridComp#1233.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.