Post Optimization Validations
@ehariton is already working on this.
Since Feb 13, 2026.
- Dominant language
- Python
- Stars
- 287
- Forks
- 140
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 18
Description
Desired capability or behavior.
At the moment Aviary does not have a component that allows for post model run validations. These checks might include checking the values of subsystem outputs that are not formal optimization constraints, but might still be of interest to the user/aircraft designer.
The fuel system is a good example - it is possible to ignore the excess fuel constraint, but it would be good to flag the excess fuel values to the user if they are negative. The user might also want to compare the values of internally computed aviary values, with those that were user overrides, e.g. Wing fuel, fuselage fuel, auxiliary fuel capacity computed vs override.
It is possible we can do this on a per subsystem basis using the OpenMDAO validate functionality:
https://openmdao.org/newdocs/versions/latest/features/core_features/running_your_models/run_validation.html
Solving this issue requires:
- Designing the architecture for handling this validation
- adding validation to warn user if excess_fuel is negative and validate the fuel subsystem to warn if fuselage or aux fuel capacity is negative at the end of the optimization.
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.