Phase info requires users to know about time/distance swapping

[jkirk5]

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

[Kenneth-T-Moore]

I think the only 2dof phases that use distance as the integration variable are all in the Solved 2DOF configurator, used for detailed takeoff and landing. If we replace these with the Picard shooting, then this behavior may go away.