Current mass scaling in flight_phase_builder is not ideal.
Open
@Kenneth-T-Moore is already working on this.
Since Feb 12, 2026.
- Dominant language
- Python
- Stars
- 287
- Forks
- 140
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 18
Description
Description
Currently, the mass state is added in flight_phase_builder.py with a ref of 1e4 and a defect _ref of 1e6.
- I think these are actually switched from what they should be. The 1e6 on the defect ref means the optimizer doesn't see the mass defects as important as other defects. We have had some success in Jes's detailed take-off case with using a smaller value (1e3), so that when the optimizer couldn't satisfy all the constraints, it didn't leave you with large mass discontinuities.
- These values are hardcoded, and it would be beneficial for them to be added to the phase_info parameters so that a user can control them directly.
Example
Contact Ken and Jes for specific cases, though item 2 above can be done without one.
Aviary Version
0.9.4-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.