OpenMDAO / OpenMDAO/Aviary

Replicate FLOPS VAPPR behaviour

Open
#1,222 2 comments 0 reactions 1 assignee View on GitHub

@cmbenne3 is already working on this.

Since Jul 13, 2026.

request
Dominant language
Python
Stars
287
Forks
140
Avg merge
6d 14h
Merged PRs (30d)
18

Description

Desired capability or behavior.

Aviary should add functionality to replicate the FLOPS VAPPR behavior.

Image

This is an input variable in FLOPS which allows the user to add an upper bound constraint on the value of output VAPP. VAPP appears in the Objectives/Variables/Constraints Summary section of FLOPS output file:

Image

VAPP most closely maps to Mission.Landing.INITIAL_VELOCITY.

Suggested implementation.

Aviary could replicate the VAPPR behavior by adding a new constraint variable to the hierarchy (e.g. Mission.Constraints.MAX_APPROACH_VELOCITY), and then add a constraint:

Mission.Landing.INITIAL_VELOCITY <= Mission.Constraints.MAX_APPROACH_VELOCITY

When the value of Mission.Constraints.MAX_APPROACH_VELOCITY is greater than zero.

The FLOPS input variable AERIN.VAPPR should be mapped to this new variable (Mission.Constraints.MAX_APPROACH_VELOCITY) and handled by fortran_to_aviary conversion function.
An investigation should be conducted to see if there is an equivalent GASP variable that can also be mapped to this.
The new constraint should be made available for all problem types and equations of motion in Aviary.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.