GEOS-ESM / GEOS-ESM/FVdycoreCubed_GridComp
Create sibling data type for T_FVDYCORE_VARS
Open
Nobody has claimed this yet.
- Dominant language
- Fortran
- Stars
- 3
- Forks
- 14
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 3
Description
This data structure becomes problematic for the GridComp side of exchanges where there are now multiple pointers per field
One possibility is to keep the data type but T_FVDYCORE_STATE now has an array of VARS
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
Read the definitions and uses of T_FVDYCORE_VARS and T_FVDYCORE_STATE, then trace the GridComp exchange code that handles multiple pointers per field. Decide whether the exchange needs a sibling data type or an array of VARS in T_FVDYCORE_STATE; done means the problematic GridComp exchanges support the required pointer structure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100