You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Parameters have been included in the timeseries outputs by default for some time. This was done to maintain consistency with older versions of Dymos. However, this adds a lot of data without much benefit (seeing values of the parameters across all nodes in a phase isn't necessary, since parameters are static.
Parameter values have been available as outputs from dymos phases for several releases now as f'{phase_path}.parameter_vals:{param_name}'.
This change is backwards incompatible if users were relying on getting parameter values from the timeseries!
Once this change takes place, parameters will ONLY be available as f'{phase_path}.parameter_vals:{param_name}', not f{phase_path}.timeseries.parameters:{param_name}.
Previous behavior can be recovered by setting the include_timeseries option on the parameter to True.
Example
No response
The text was updated successfully, but these errors were encountered:
Proposed feature.
Parameters have been included in the timeseries outputs by default for some time. This was done to maintain consistency with older versions of Dymos. However, this adds a lot of data without much benefit (seeing values of the parameters across all nodes in a phase isn't necessary, since parameters are static.
Parameter values have been available as outputs from dymos phases for several releases now as
f'{phase_path}.parameter_vals:{param_name}'
.This change is backwards incompatible if users were relying on getting parameter values from the timeseries!
Once this change takes place, parameters will ONLY be available as
f'{phase_path}.parameter_vals:{param_name}'
, notf{phase_path}.timeseries.parameters:{param_name}
.Previous behavior can be recovered by setting the
include_timeseries
option on the parameter toTrue
.Example
No response
The text was updated successfully, but these errors were encountered: