Compare to correct in location_mods
Open
Nobody has claimed this yet.
performance
- Dominant language
- Fortran
- Stars
- 263
- Forks
- 182
- Avg merge
- 11d 12h
- Merged PRs (30d)
- 7
Description
These arrays are pretty big to allocate, and are only used if you are doing COMPARE_TO_CORRECT
Originally posted by @hkershaw-brown in #910
Contributor guide
No contributing guide indexed for this repository
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 by reading assimilation_code/location/threed_sphere/location_mod.f90 around lines 1442-1444 and trace the arrays used by COMPARE_TO_CORRECT. Confirm when those arrays are needed and how their allocation is currently reached. Done means the large arrays are not allocated for other modes while COMPARE_TO_CORRECT still works correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran
- Domain
- hpc
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100