scenarioAttitudeFeedback2T_stateEffTH

Overview

This scenario is an exact replica of scenarioAttitudeFeedback2T_TH. The only difference lies in the fact that this scenario uses the Module: thrusterStateEffector module instead of Module: thrusterDynamicEffector. The performance and results should be nearly identical to the original scenario, with the small difference that the thrusters do not have an on-off behavior, but instead behave like a first-order filter. For more information on the scenario setup, see scenarioAttitudeFeedback2T_TH.

To show that the Module: thrusterStateEffector thruster module works with variable time step integrators, this scenario uses an RKF78 integrator instead of the usual RK4.

Illustration of Simulation Results

show_plots = True, useDVThrusters = False

show_plots = True, useDVThrusters = True

scenarioAttitudeFeedback2T_stateEffTH.plot_OnTimeRequest(timeDataFSW, dataSchm, numTh)

Plot the thruster on time requests.

scenarioAttitudeFeedback2T_stateEffTH.plot_attitude_error(timeDataFSW, dataSigmaBR)

Plot the attitude errors.

scenarioAttitudeFeedback2T_stateEffTH.plot_rate_error(timeDataFSW, dataOmegaBR)

Plot the body angular velocity tracking errors.

scenarioAttitudeFeedback2T_stateEffTH.plot_requested_torque(timeDataFSW, dataLr)

Plot the commanded attitude control torque.

scenarioAttitudeFeedback2T_stateEffTH.plot_thrForce(timeDataFSW, dataMap, numTh)

Plot the Thruster force values.

scenarioAttitudeFeedback2T_stateEffTH.plot_trueThrForce(timeDataFSW, dataMap, numTh)

Plot the Thruster force values.

scenarioAttitudeFeedback2T_stateEffTH.run(show_plots, useDVThrusters)

The scenarios can be run with the followings setups parameters:

Parameters:

• show_plots (bool) – Determines if the script should display plots

• useDVThrusters (bool) – Use 6 DV thrusters instead of the default 8 ACS thrusters.