Currently the final timestep, which is not physical, is used to store the value that is used to constrain all the time steps to be equal. This feature request proposes storing the total time there instead.
Currently:
If a TimeStepsAllEqualConstraint is set, which is the default case for most problem templates, get_timesteps(traj)[end] will return the value of the total time step
Proposal:
Have get_timesteps(traj)[end] return the total time and the time step all equal constraints be changed accordingly (just need to divide total time by number of timesteps)
Feature Description
Currently the final timestep, which is not physical, is used to store the value that is used to constrain all the time steps to be equal. This feature request proposes storing the total time there instead.
Currently: If a
TimeStepsAllEqualConstraint
is set, which is the default case for most problem templates,get_timesteps(traj)[end]
will return the value of the total time stepProposal: Have
get_timesteps(traj)[end]
return the total time and the time step all equal constraints be changed accordingly (just need to divide total time by number of timesteps)Importance
1 (lowest)
What does this feature affect?
Other information
No response