Some intermediate forces from trajectory analysis should be more accessible for debugging

[jkirk5]

Desired capability or behavior.

from @dlcaldwelljr-ama-inc: Some intermediate forces from trajectory analysis should be more accessible for debugging. A few examples are:

GASP based "thrust_along_flightpath" and "thrust_across_flightpath"; FLOPS based "required_thrust" and "forces_perpendicular".

• When necessary, add these forces to the Aviary variable hierarchy.
• When appropriate, use uniform variable names across the board, regardless if the selected analysis is GASP based or FLOPS based.
• When appropriate, such variables should be available as timeseries output.

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

No response

Associated Bug Report

No response

[jkirk5]

IMO unifying variable names should be sufficient for now. I'd like to keep the Aviary hierarchy as clean as possible with intermediate computations only added if they are commonly needed as constraints or their final values checked by users. Open to further discussion on what should/should not get added