OpenMDAO / OpenMDAO/Aviary

Overhaul Aviary Time calculations

Open
#1,045 1 comment 0 reactions 2 assignees View on GitHub

@ehariton is already working on this.

Since Apr 2, 2026.

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

Description

Desired capability or behavior.

Aviary should calculate some mission time variables that correspond to useful durations within the mission.

Currently there is a variable Mission.Final_Time which is the duration of the dymos modelled regular phases within the mission. Depending on whether detailed takeoff and landing are used, or 2dof equations of motion are used then this might or might not include takeoff and landing.

Suggested change will ensure Aviary calculates the following:
Mission.BLOCK_TIME = Mission.Taxi.OUT_TIME + Mission.Takeoff.TIME + Mission.FLIGHT_TIME + Mission.APPROACH_TIME + Mission.Landing.TIME + Mission.Taxi.IN_TIME

Not all of these are modeled at the moment.

Logic will need to be added to sum the correct times with/without taxi, takeoff, approach and landing, depending what phases are modelled in dymos, and whether simple or detailed takeoff/landing are modeled.

Aviary should also calculate the Mission.RESERVE_TIME (which should be the duration of the reserve phases + holds etc)

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

  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.