GEOS-ESM / GEOS-ESM/GEOSgcm_GridComp
[ACG] IgniGridComp: 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: IgniGridComp
Primary file: GEOSagcm_GridComp/GEOSphysics_GridComp/GEOSsurface_GridComp/GEOSland_GridComp/GEOSigni_GridComp/GEOS_IgniGridComp.F90
Sub-repo: GEOSgcm_GridComp
Effort: M
MAPL depth: leaf
Current state
- Manual
MAPL_AddImportSpec/MAPL_AddExportSpec/MAPL_AddInternalSpeccalls: 45 total VERIFY_(calls: 2
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/GEOSigni_GridComp/GEOS_IgniGridComp.F90 and review its 45 manual MAPL_AddImportSpec, MAPL_AddExportSpec, and MAPL_AddInternalSpec calls alongside the two VERIFY_( calls. Use the parent epic GEOS-ESM/GEOSgcm_GridComp#1241 for migration context; done means the component has been migrated to mapl_acg.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran
- Domain
- hpc
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100