OpenMDAO / OpenMDAO/Aviary

Formalize preprocessors

Open
#391 2 comments 0 reactions 4 assignees View on GitHub

@cmbenne3 is already working on this.

Since Feb 11, 2026.

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

Description

Desired capability or behavior.

The placement of preprocessors should be more carefully considered (i.e. when should they be run during a standard run_aviary execution). There is likely additional code that should be migrated to a preprocessor as well.

@jdgratz10: Note that the new detailed takeoff and landing stuff has some phase_builder level preprocessing that should be included here.
@johnjasa: Additionally, these preprocessors could do small computations needed to translate between the input file and the model setup.

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.