Segments of Phases#

Things you’ll learn through this example

• What are segments?

• How does the number and order of segments affect the solution?

• How to use the Dymos run_problem function to find the right number of segments automatically.

What are segments?#

In the previous section we showed a converged trajectory that didn’t really match the state propagation found using Scipy’s variable step solve_ivp method.

class OscillatorODE(om.ExplicitComponent):
"""
A Dymos ODE for a damped harmonic oscillator.
"""

def initialize(self):
self.options.declare('num_nodes', types=int)

def setup(self):
nn = self.options['num_nodes']

# Inputs

# self.add_output('x_dot', val=np.zeros(nn), desc='rate of change of displacement', units='m/s')
self.add_output('v_dot', val=np.zeros(nn), desc='rate of change of velocity', units='m/s**2')

self.declare_partials(of='*', wrt='*', method='fd')

def compute(self, inputs, outputs):
x = inputs['x']
v = inputs['v']
k = inputs['k']
c = inputs['c']
m = inputs['m']

f_spring = -k * x
f_damper = -c * v

outputs['v_dot'] = (f_spring + f_damper) / m

import openmdao.api as om
import dymos as dm
import matplotlib.pyplot as plt

from dymos.examples.oscillator.oscillator_ode import OscillatorODE

# Instantiate an OpenMDAO Problem instance.
prob = om.Problem()

# Instantiate a Dymos Trajectory and add it to the Problem model.
traj = dm.Trajectory()

# Instantiate a Phase and add it to the Trajectory.
# Here the transcription is necessary but not particularly relevant.

# Tell Dymos the states to be propagated using the given ODE.

# The spring constant, damping coefficient, and mass are inputs to the system
# that are constant throughout the phase.

# Setup the OpenMDAO problem
prob.setup()

# Assign values to the times and states
prob.set_val('traj.phase0.t_initial', 0.0)
prob.set_val('traj.phase0.t_duration', 15.0)

prob.set_val('traj.phase0.states:x', 10.0)
prob.set_val('traj.phase0.states:v', 0.0)

prob.set_val('traj.phase0.parameters:k', 1.0)
prob.set_val('traj.phase0.parameters:c', 0.5)
prob.set_val('traj.phase0.parameters:m', 1.0)

# Perform a single execution of the model (executing the model is required before simulation).
prob.run_model()

# Perform an explicit simulation of our ODE from the initial conditions.
sim_out = traj.simulate(times_per_seg=50)

# Plot the state values obtained from the phase timeseries objects in the simulation output.
t_sol = prob.get_val('traj.phase0.timeseries.time')
t_sim = sim_out.get_val('traj.phase0.timeseries.time')

states = ['x', 'v']
fig, axes = plt.subplots(len(states), 1)
for i, state in enumerate(states):
sol = axes[i].plot(t_sol, prob.get_val(f'traj.phase0.timeseries.states:{state}'), 'o')
sim = axes[i].plot(t_sim, sim_out.get_val(f'traj.phase0.timeseries.states:{state}'), '-')
axes[i].set_ylabel(state)
axes[-1].set_xlabel('time (s)')
fig.legend((sol[0], sim[0]), ('solution', 'simulation'), 'lower right', ncol=2)
plt.tight_layout()
plt.show()

--- Constraint Report [traj] ---
--- phase0 ---
None

Simulating trajectory traj
Done simulating trajectory traj

/tmp/ipykernel_5576/2310660929.py:60: MatplotlibDeprecationWarning: Passing the loc parameter of __init__() positionally is deprecated since Matplotlib 3.6; the parameter will become keyword-only two minor releases later.
fig.legend((sol[0], sim[0]), ('solution', 'simulation'), 'lower right', ncol=2)


Why does this happen? The implicit collocation techniques used by Dymos (the Radau Pseudospectral Method and Legendre-Gauss-Lobatto collocation) work by discretizing a continuous function (the state time-history) into a series of discrete points. It does this by breaking the time domain of each phase into multiple polynomial segments. On each segment, each state is treated as a continuous polynomial of some given order. In Dymos, segments must have an order of at least 3. That is also the default order for segments.

How does the number and order of segments affect the solution?#

Obviously, a single third-order polynomial won’t be able to fit highly oscillatory behavior. In this case, our guess of using four segments (equally spaced) in the phase wasn’t quite sufficient. Let’s try increasing that number to ten third-order segments.

import openmdao.api as om
import dymos as dm
import matplotlib.pyplot as plt

from dymos.examples.oscillator.oscillator_ode import OscillatorODE

# Instantiate an OpenMDAO Problem instance.
prob = om.Problem()

# We need an optimization driver.  To solve this simple problem ScipyOptimizerDriver will work.
prob.driver = om.ScipyOptimizeDriver()

# Instantiate a Dymos Trajectory and add it to the Problem model.
traj = dm.Trajectory()

# Instantiate a Phase and add it to the Trajectory.

# Tell Dymos that the duration of the phase is bounded.
phase.set_time_options(fix_initial=True, fix_duration=True)

# Tell Dymos the states to be propagated using the given ODE.

# The spring constant, damping coefficient, and mass are inputs to the system that
# are constant throughout the phase.

# Since we're using an optimization driver, an objective is required.  We'll minimize
# the final time in this case.

# Setup the OpenMDAO problem
prob.setup()

# Assign values to the times and states
prob.set_val('traj.phase0.t_initial', 0.0)
prob.set_val('traj.phase0.t_duration', 15.0)

prob.set_val('traj.phase0.states:x', 10.0)
prob.set_val('traj.phase0.states:v', 0.0)

prob.set_val('traj.phase0.parameters:k', 1.0)
prob.set_val('traj.phase0.parameters:c', 0.5)
prob.set_val('traj.phase0.parameters:m', 1.0)

# Now we're using the optimization driver to iteratively run the model and vary the
# phase duration until the final y value is 0.
prob.run_driver()

# Perform an explicit simulation of our ODE from the initial conditions.
sim_out = traj.simulate(times_per_seg=50)

# Plot the state values obtained from the phase timeseries objects in the simulation output.
t_sol = prob.get_val('traj.phase0.timeseries.time')
t_sim = sim_out.get_val('traj.phase0.timeseries.time')

states = ['x', 'v']
fig, axes = plt.subplots(len(states), 1)
for i, state in enumerate(states):
sol = axes[i].plot(t_sol, prob.get_val(f'traj.phase0.timeseries.states:{state}'), 'o')
sim = axes[i].plot(t_sim, sim_out.get_val(f'traj.phase0.timeseries.states:{state}'), '-')
axes[i].set_ylabel(state)
axes[-1].set_xlabel('time (s)')
fig.legend((sol[0], sim[0]), ('solution', 'simulation'), 'lower right', ncol=2)
plt.tight_layout()
plt.show()

--- Constraint Report [traj] ---
--- phase0 ---
None

/usr/share/miniconda/envs/test/lib/python3.10/site-packages/openmdao/core/total_jac.py:1567: DerivativesWarning:Constraints or objectives [('traj.phases.phase0.time.time', inds=[39])] cannot be impacted by the design variables of the problem.

Optimization terminated successfully    (Exit mode 0)
Current function value: [15.]
Iterations: 1
Function evaluations: 2
Optimization Complete
-----------------------------------

Simulating trajectory traj
Done simulating trajectory traj

/tmp/ipykernel_5576/3442879847.py:70: MatplotlibDeprecationWarning: Passing the loc parameter of __init__() positionally is deprecated since Matplotlib 3.6; the parameter will become keyword-only two minor releases later.
fig.legend((sol[0], sim[0]), ('solution', 'simulation'), 'lower right', ncol=2)


Alternatively, we could stick with 4 segments but give each a higher order (7 in this case).

import openmdao.api as om
import dymos as dm
import matplotlib.pyplot as plt

from dymos.examples.oscillator.oscillator_ode import OscillatorODE

# Instantiate an OpenMDAO Problem instance.
prob = om.Problem()

# We need an optimization driver.  To solve this simple problem ScipyOptimizerDriver will work.
prob.driver = om.ScipyOptimizeDriver()

# Instantiate a Dymos Trajectory and add it to the Problem model.
traj = dm.Trajectory()

# Instantiate a Phase and add it to the Trajectory.

# Tell Dymos that the duration of the phase is bounded.
phase.set_time_options(fix_initial=True, fix_duration=True)

# Tell Dymos the states to be propagated using the given ODE.

# The spring constant, damping coefficient, and mass are inputs to the system that are
# constant throughout the phase.

# Since we're using an optimization driver, an objective is required.  We'll minimize
# the final time in this case.

# Setup the OpenMDAO problem
prob.setup()

# Assign values to the times and states
prob.set_val('traj.phase0.t_initial', 0.0)
prob.set_val('traj.phase0.t_duration', 15.0)

prob.set_val('traj.phase0.states:x', 10.0)
prob.set_val('traj.phase0.states:v', 0.0)

prob.set_val('traj.phase0.parameters:k', 1.0)
prob.set_val('traj.phase0.parameters:c', 0.5)
prob.set_val('traj.phase0.parameters:m', 1.0)

# Now we're using the optimization driver to iteratively run the model and vary the
# phase duration until the final y value is 0.
prob.run_driver()

# Perform an explicit simulation of our ODE from the initial conditions.
sim_out = traj.simulate(times_per_seg=50)

# Plot the state values obtained from the phase timeseries objects in the simulation output.
t_sol = prob.get_val('traj.phase0.timeseries.time')
t_sim = sim_out.get_val('traj.phase0.timeseries.time')

states = ['x', 'v']
fig, axes = plt.subplots(len(states), 1)
for i, state in enumerate(states):
sol = axes[i].plot(t_sol, prob.get_val(f'traj.phase0.timeseries.states:{state}'), 'o')
sim = axes[i].plot(t_sim, sim_out.get_val(f'traj.phase0.timeseries.states:{state}'), '-')
axes[i].set_ylabel(state)
axes[-1].set_xlabel('time (s)')
fig.legend((sol[0], sim[0]), ('solution', 'simulation'), 'lower right', ncol=2)
plt.tight_layout()
plt.show()

--- Constraint Report [traj] ---
--- phase0 ---
None

Optimization terminated successfully    (Exit mode 0)
Current function value: [15.]
Iterations: 1
Function evaluations: 2
Optimization Complete
-----------------------------------

/usr/share/miniconda/envs/test/lib/python3.10/site-packages/openmdao/core/total_jac.py:1567: DerivativesWarning:Constraints or objectives [('traj.phases.phase0.time.time', inds=[31])] cannot be impacted by the design variables of the problem.

Simulating trajectory traj
Done simulating trajectory traj

/tmp/ipykernel_5576/2579984739.py:70: MatplotlibDeprecationWarning: Passing the loc parameter of __init__() positionally is deprecated since Matplotlib 3.6; the parameter will become keyword-only two minor releases later.
fig.legend((sol[0], sim[0]), ('solution', 'simulation'), 'lower right', ncol=2)


In both these cases, we obtained a better match of the dynamics using either more segments or higher-order segments. This gives the state interpolating polynomials enough freedom to more accurately match the true behavior of the system. Increasing the number of segments and increasing the segment orders both increase the number of discrete points, and thus slow down the solution a bit. Theres a balance to be found between using enough discretization points to get an accurate solution, and slowing down the analysis due to having an overabundance of points. In general, using a high number of low-order segments is preferable to using fewer high-order segments because it makes the constraint jacobian more sparse.

In addition to the number and order of the segments, the user can also provide the transcription the argument segment_ends. If None, the segments are equally distributed in time throughout the phase. Otherwise, segment_ends should be a monotonically increasing sequence of length num_segments + 1.

Each element in the sequence provides the location of a segment boundary in the phase. The items in segment_ends are normalized by Dymos, so feel free to provide them in whatever scale makes sense. That is, segment_ends=[0, 1, 2, 5] is equivalent to segment_ends=[10, 20, 30, 60].

Letting Dymos automatically find the right segmentation of the phase#

Manually tweaking the “grid” (the number of segments, their order, and relative spacing) isn’t ideal. In reality, another nested level of iteration is required:

1. Problem.run_model() evaluates the model and computes constraints and objectives based on the current design variables.

2. Problem.run_driver() iteratively calls Problem.run_model() while varying the design variables in order to find a feasible, optimal design point.

3. Some “outer” function iterates on run_driver(), varying the grid until a satisfactory accuracy is achieved.

This third level is filled by the role of automated grid refinement via the dymos.run_problem. In the next section, we’ll learn how to use automated grid refinement in Dymos.