OpenMDAO / OpenMDAO/Aviary

Investigate ascent_duration as part of objective functions

Open
#1,079 0 comments 0 reactions 4 assignees View on GitHub

@Kenneth-T-Moore is already working on this.

Since Apr 9, 2026.

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

Description

Desired capability or behavior.

Propose to entirely remove the 'hybrid' nature of our objective functions and make fuel the default.
We think that 2dof objectives with Mission.Takeoff.ASCENT_DURATION included are possibly linked in by mistake as this input is also a design variable!

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.