Convert missions & constraints from legacy files
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 287
- Forks
- 140
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 18
Description
Desired capability or behavior.
Update fortran_to_aviary.py to convert missions into phase_info. This should be doable mostly with existing code (we already can turn basic mission profiles into phase_info when using draw_mission.
Once the performance subsystem is done, we can also convert performance constraints in the legacy files into whatever format that subsystem ends up using to define them in Aviary.
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.
Research direction
Start in fortran_to_aviary.py and compare its legacy mission handling with the existing draw_mission path that produces phase_info. The mission portion is done when legacy missions convert into phase_info; performance constraints depend on the performance subsystem's eventual constraint format and need that design before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100