Unify mission range and distance variable names
@jkirk5 is already working on this.
Since May 28, 2026.
- Dominant language
- Python
- Stars
- 287
- Forks
- 140
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 18
Description
Desired capability or behavior.
Dynamic.Mission.RANGE and Dynamic.Mission.DISTANCE have the same meaning in Aviary. We should choose one and rename throughout Aviary.
The difference is probably a holdover from the LEAPS2 and GASPy codes.
@johnjasa: We only need one of them. I'd say distance is probably most clear?
@ehariton: My preference is to go with Mission.Dynamic.Range since Distance could be interpreted as vertical or horizontal, but Range has a stronger connection with horizontal movement. We should leave an alias reference so people familiar with one can see that we've changed the var name.
Is your feature request related to a problem? Please describe.
No response
Associated Bug Report
No response
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.
Assessment
This issue has not been assessed yet.