Replace internal MAPL module references with USE MAPL or USE MAPL_Constants
Nobody has claimed this yet.
- Dominant language
- Fortran
- Stars
- 29
- Forks
- 22
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 4
Description
Problem
Several compiled GOCART files reference internal MAPL submodules directly instead of going through the public `USE MAPL` or `USE MAPL_Constants` wrapper modules.
Affected Files
| File | Internal Module(s) Used |
|---|---|
| `ESMF/Apps/aop_calculator.F90` | `MAPL_LatLonGridFactoryMod` |
| `ESMF/GOCART2G_GridComp/CA2G_GridComp/CA2G_GridCompMod.F90` | `MAPL_StringTemplate`, `MAPL_PackedTimeMod` |
| `ESMF/GOCART2G_GridComp/DU2G_GridComp/DU2G_GridCompMod.F90` | `MAPL_PackedTimeMod`, `MAPL_StringTemplate` |
| `ESMF/GOCART2G_GridComp/SU2G_GridComp/SU2G_GridCompMod.F90` | `MAPL_StringTemplate`, `MAPL_PackedTimeMod` |
Required Change
Replace all internal `USE MAPL_*` module references with `USE MAPL` (with appropriate `only:` clauses), so that all MAPL symbols are accessed through the public wrapper interface.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the four listed files: ESMF/Apps/aop_calculator.F90 and the CA2G, DU2G, and SU2G GridComp modules. Inspect the existing MAPL module imports and the public symbols exposed by MAPL and MAPL_Constants, then compile the affected GOCART components. Done means all listed internal MAPL references are replaced with appropriate public USE statements and the affected files compile successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 74/100