OpenMDAO / OpenMDAO/Aviary

Expose a way for users to link values across phases in level 2

Open
#234 0 comments 0 reactions 2 assignees View on GitHub

@ehariton is already working on this.

Since Feb 9, 2026.

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

Description

Desired capability or behavior.

Users want to be able to link variables between phases.
These variables might be computed; an example of this is throttle.
To enforce continuity in the throttle profile across phase boundaries, users would have to add a linkage constraint.
We should expose a way in level 2 through the phase_info for a user to specify linkages between phases.

We'll have to think about the best implementation of this, especially how we expose it to the user, because these linkages would deal with multiple phases.
Should there be a separate linkages section at the top level of phase_info? Should we have a linked_variables entry in each phase and only if two (or more) neighboring phases have the variable in there do we link them?

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.