GEOS-ESM / GEOS-ESM/GEOSgcm_GridComp
[ACG] RouteGridComp: migrate to mapl_acg
Nobody has claimed this yet.
- Dominant language
- Fortran
- Stars
- 10
- Forks
- 13
- Avg merge
- 17h 35m
- Merged PRs (30d)
- 14
Description
Component
Name: RouteGridComp
Primary file: GEOSagcm_GridComp/GEOSphysics_GridComp/GEOSsurface_GridComp/GEOSland_GridComp/GEOSroute_GridComp/GEOS_RouteGridComp.F90
Sub-repo: GEOSgcm_GridComp
Effort: S
MAPL depth: leaf
Current state
- Manual
MAPL_AddImportSpec/MAPL_AddExportSpec/MAPL_AddInternalSpeccalls: 11 total VERIFY_(calls: 9
Notes
None.
Links
- Parent epic: GEOS-ESM/GEOSgcm_GridComp#1241
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 GEOSagcm_GridComp/GEOSphysics_GridComp/GEOSsurface_GridComp/GEOSland_GridComp/GEOSroute_GridComp/GEOS_RouteGridComp.F90 and read the parent epic GEOS-ESM/GEOSgcm_GridComp#1241 for migration context. Confirm the 11 manual MAPL specification calls and 9 VERIFY_ calls, then migrate RouteGridComp to mapl_acg and verify those calls are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100