OpenMDAO / OpenMDAO/Aviary

Create phase_info files for benchmark models

Open
#365 0 comments 0 reactions 1 assignee View on GitHub

@ehariton is already working on this.

Since Feb 11, 2026.

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

Description

Desired capability or behavior.

Mission definition for benchmark tests is created inside that test. For each aircraft we re-use the same mission constraints in each benchmark, we should instead centralize this information would help with consistency and might make it easier to create benchmarks in the future.

TLDR: models should come with a phase info that runs their design mission, and benchmark tests should pull from that phase info

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.