OpenMDAO / OpenMDAO/Aviary

Phase info requires users to know about time/distance swapping

Open
#856 3 comments 0 reactions 1 assignee View on GitHub

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

Since Aug 25, 2025.

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

Description

Desired capability or behavior.

For 2DOF phases that need to use distance as the integration variable, some places in phase_info require users to know about this and place distance-related values and units in the time-related options. See here for an example.

Any user-facing API should always refer to the "correct" variable, and never require users to know about and manually account for the aliasing we do under-the-hood to trick dymos.

Is your feature request related to a problem? Please describe.

Issue reported on the discussions page

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.