Range constraint in a single-phase mission
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 287
- Forks
- 140
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 18
Description
Description
I believe the range constraint is not imposed when the mission has only one phase, and target_range is ignored. This is because the connection from traj.<final_phase>.timeseries.distance[-1] to Mission.Summary.RANGE is added only when the mission has more than one phases in link_phases.
(So technically, the range constraint is imposed but Mission.Summary.RANGE is not having a valid value.)
I know single-phase missions are not practical, but I thought it would be nice to have the range constraint for any mission setup. Thank you!
Example
For example, if I add target_range to this cruise-only example, the cruise duration remains unchanged and the target range is achieved.
Aviary Version
0.9.9-dev
Relevant environment information
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.