Attitude - Historique des versions

Admin : /* Attitude sequence */

2017-11-16T10:21:52Z

Attitude sequence

Admin le 11 juillet 2017 à 11:16

2017-07-11T11:16:11Z

Admin le 10 juillet 2017 à 07:41

2017-07-10T07:41:25Z

Admin le 6 juillet 2017 à 16:53

2017-07-06T16:53:13Z

Admin le 6 juillet 2017 à 16:52

2017-07-06T16:52:25Z

Admin : Page créée avec « This tab, dealing with attitude sequence is, perhaps, the most difficult to understand. Anyway, it is mandatory to define at least one attitude law as
2017-07-06T16:51:56Z

Page créée avec « This tab, dealing with attitude sequence is, perhaps, the most difficult to understand. Anyway, it is mandatory to define at least one attitude law as it is mandatory to define at least one attitude law as '''PSIMU''' needs to compute attitude angles as output variables.

== Reference date ==

First, as for a maneuver sequence, the user will have to select a reference date. There are two possibilities:
o “custom” : a specific date will be entered by the user
o “external” : in that case no modification of the date is available as it corresponds to the date defined in the initial orbit parameters (note that this date is automatically updated if the initial orbit date is modified).

[[Fichier:ReferenceDate.png]]

== List of laws ==

Then, a button appears that allows displaying a new window to define a set of available attitude laws. Each law is defined as below:
* Name of the law
* Type of the law (local orbital frame (LOF), inertial, Sun pointing …)
* Law evolution (constant or spinned)
* Then data linked to the type of law. As an example for LOF attitude law, the user will have to select which LOF to take into account and eventually angle bias.

[[Fichier:AttitudeLawList.png]]

At last, the user will get a choice between:
* A simple attitude sequence with only a single law chosen in the previous list (not available in V11.0 version)
* A more sophisticated definition of the attitude sequence using the [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] “'''event switch'''” possibility. The user will have to define one or several switches defined by the following data:
:- The attitude law before the event (taken in the previous list)
:- The attitude law once the event occurred (taken in the previous list)
:- The type of event and data related to it.
This “'''event switch'''” is a very powerful option that allows defining relatively shortly a whole mission. For example, if we want to define the fact that the vehicle is LVLH oriented in eclipse and Sun pointing out of eclipse, we will only have to define two switches calling to two attitude laws:
:- '''Switch #1''' with entering in eclipse as orbital event and law before "Sun pointing" and law after "LVLH"
:- '''Switch #2''' with exiting in eclipse as orbital event and law before "LVLH" and law after "Sun pointing"

[[Fichier:AttitudeSwitch.png]]

Attitude - Historique des versions

Admin : /* Attitude sequence */

Admin le 11 juillet 2017 à 11:16

Admin le 10 juillet 2017 à 07:41

Admin le 6 juillet 2017 à 16:53

Admin le 6 juillet 2017 à 16:52

Admin : /* Attitude sequence */