The settings that this solver accepts are given by a dictionary, with the following key-value pairs:
Route and file name of the trajectory file given as a csv with columns: time, x, y, z
Time step of the simulation
Trajectory controller method. For now, “lagrange” is the supported option
Name of the controlled constraint in the multibody context Usually, it is something like constraint_00.
Directory where the log will be stored
Controls if the log from the controller is written or not.
If different than and empty string, the structural solver will be changed after the end of the trajectory has been reached
Controls the structural solver structural substeps once the end of the trajectory has been reached
Controls the number of timesteps that are used to increase the structural substeps from 0
Main routine of the controller. Input is data (the self.data in the solver), and currrent_state which is a dictionary with [‘structural’, ‘aero’] time steps for the current iteration.
data – problem data containing all the information.
controlled_state – dict with two vars: structural and aero containing the timestep_info that will be returned with the control variables.
A dict with structural and aero time steps and control input included.