Tutorials 4.0 Attitude : Différence entre versions
(Page créée avec « == Attitude == We must not confuse an [{{PathCurrentJavaDoc}}/fr/cnes/sirius/patrius/attitudes/Attitude.html Attitude] and an [{{PathCurrentJavaDoc}}/fr/cnes/sirius/patri... ») |
m (Admin a déplacé la page AttitudeTutorials vers Tutorials 4.0 Attitude sans laisser de redirection) |
||
(3 révisions intermédiaires par le même utilisateur non affichées) | |||
Ligne 31 : | Ligne 31 : | ||
'''Code example:''' [[SequenceOfAttitudes|create a sequence of attitude laws]] | '''Code example:''' [[SequenceOfAttitudes|create a sequence of attitude laws]] | ||
+ | |||
+ | [[Category:Tutorials 4.0]] |
Version actuelle en date du 27 mars 2018 à 14:01
Attitude
We must not confuse an Attitude and an AttitudeLaw (or AttitudeLawLeg). Indeed an Attitude is the current orientation of the spacecraft as the other ones will define the "laws" allowing to determine at each moment, the Attitude.
For example, if we have an inertial AttitudeLaw, the (inertial) Attitude of the spacecraft will be the same at each moment of the trajectory.
But if we have a Sun Pointing AttitudeLaw, the current Attitude will change at each step.
So, most of the time, users will define AttitudeLaw or AttitudeLawLeg and will get the current Attitude using the getAttitude() method.
Attitude laws
Building an attitude law is relatively easy, using one of the the constructors available depending of the kind of law you want to use. Next examples show different cases.
Code examples:
Attitude legs
To be written ...
Attitude sequence
AttitudesSequence is a very powerful concept which allows to define attitude logic all along a mission. Indeed, as it is based on orbital events detection, it avoids to define step by step attitude laws. For example, if we want to have:
- LVLH attitude during eclipse
- Sun pointing attitude else
... only two "switches" inside the attitude sequence are sufficient. It is coded in the proposed following tutorial.
Code example: create a sequence of attitude laws