TakeOffTrajectoryController¶
The settings that this solver accepts are given by a dictionary, with the following key-value pairs:
Name Type Description Default trajectory_input_filestrRoute and file name of the trajectory file given as a csv with columns: time, x, y, z NonedtfloatTime step of the simulation Nonetrajectory_methodstrTrajectory controller method. For now, “lagrange” is the supported option lagrangecontrolled_constraintstrName of the controlled constraint in the multibody context Usually, it is something like constraint_00. Nonecontroller_log_routestrDirectory where the log will be stored ./output/write_controller_logboolControls if the log from the controller is written or not. Truefree_trajectory_structural_solverstrIf different than and empty string, the structural solver will be changed after the end of the trajectory has been reached free_trajectory_structural_substepsintControls the structural solver structural substeps once the end of the trajectory has been reached 0initial_ramp_length_structural_substepsintControls the number of timesteps that are used to increase the structural substeps from 0 10Main 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.
Parameters: - 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.
Returns: A dict with structural and aero time steps and control input included.