Bug? approximate_distance = .true./.false.
Nobody has claimed this yet.
- Dominant language
- Fortran
- Stars
- 263
- Forks
- 182
- Avg merge
- 11d 12h
- Merged PRs (30d)
- 7
Description
Note on approximate_distance = .true. vs. approximate_distance = .false.
approximate_distance = .true.
one close points, distance = 0. Can it really be zero? (un)lucky observation location?
approximate_distance = .false.
five close points
Originally posted by @hkershaw-brown in https://github.com/NCAR/DART/issues/343#issuecomment-1105413795
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
The issue concerns the approximate_distance setting and compares .true. and .false. results using screenshots; no source file or test is named. Start by locating the implementation or entry point for approximate_distance and reproduce both cases. Done means determining whether a zero distance is expected and documenting or correcting the inconsistent behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100