« Catégorie:Patrius Backward Compatibility 4.14 » : différence entre les versions

De Patrius
Aller à la navigation Aller à la recherche
Page créée avec « == Introduction == This section describes attitude features of Patrius: attitude laws, slew, guidance, etc. == Overview == The Attitude package of the PATRIUS library ha... »
 
Aucun résumé des modifications
Ligne 1 : Ligne 1 :


== Introduction ==
== Introduction ==
This section describes attitude features of Patrius: attitude laws, slew, guidance, etc.
A specific backward compatibility mechanism is implemented in PATRIUS allowing by default to have a backward compatibility with PATRIUS version 4.12 propagation models and/or optimisation algorithms.
If any action is provided by the user, the '''backward compatibility is activated by default in PATRIUS''' : this means that external users will see their code/functions working with some of the propagation models/optimisation algorithms of PATRIUS version 4.12.


== Overview ==
== Options available ==
The Attitude package of the PATRIUS library has been developed according to the SIRIUS Scope Statement '''[A1]'''. The themes developed are described hereafter :
Three options are available for users via the enum <code>PatriusVersionCompatibility</code> of the class <code>PatriusConfiguration</code>:
* OLD_MODELS : the user will use the propagation models and optimisation algorithms coded in PATRIUS version 4.12;
* MIXED_MODELS : the user will juste use propagation models coded in PATRIUS version 4.12 (no backward compatibility on optimisation algorithms)
* NEW_MODELS : no backward compatibility mechanism is used.


; Directions
== Backward compatibility for propagation models ==
: Implementation of directions of space that can evolve in time.


; Attitude laws
== Backward compatibility for optimisation algorithms ==
: Several attitude laws are available. These laws were originally designed for orbit determination needs: in order to broaden their applications, a wrapper object has been created to meet the spacecraft attitude field needs.


; Attitudes sequence
== How to set our own Patrius compatibility configuration ==
: Implementation of an attitudes sequence for orbit determination: it is possible to define an attitude law as a series of attitude laws in the context of a propagation.
The class <code>PatriusConfiguration</code> contains a setter <code>setPatriusCompatibilityMode(PatriusVersionCompatibility)</code> that allows to switch our own configuration as a function of the user needs.


; Attitude legs sequence
: Implementation for spacecraft attitude field of an attitude sequence: it is possible to define an attitude leg as a series of attitude legs.
; Attitude composition
: Implementation of an object that enables to define an attitude law as a composition of several laws.
; Orientation
: Orientations are similar to attitude providers except that it returns only one angle.
; Slew
: Implementation of slew. Slews are used in the attitudes sequence to define the transition between two laws. Slews are splits into two functions: slew computations through dedicated classes and slew realization.
; Kinematics
: Implementation of a tool box for kinematics calculations.
; Guidance command
: Implementation of the ground and the on-board guidance commands. The first one is computed, the second one is simulated. In both cases, it should be possible to compute the guidance command from a law and to consider the guidance command itself as a law.


[[Category:User_Manual_4.14]]
[[Category:User_Manual_4.14]]

Version du 5 septembre 2024 à 16:06

Introduction

A specific backward compatibility mechanism is implemented in PATRIUS allowing by default to have a backward compatibility with PATRIUS version 4.12 propagation models and/or optimisation algorithms. If any action is provided by the user, the backward compatibility is activated by default in PATRIUS : this means that external users will see their code/functions working with some of the propagation models/optimisation algorithms of PATRIUS version 4.12.

Options available

Three options are available for users via the enum PatriusVersionCompatibility of the class PatriusConfiguration:

  • OLD_MODELS : the user will use the propagation models and optimisation algorithms coded in PATRIUS version 4.12;
  • MIXED_MODELS : the user will juste use propagation models coded in PATRIUS version 4.12 (no backward compatibility on optimisation algorithms)
  • NEW_MODELS : no backward compatibility mechanism is used.

Backward compatibility for propagation models

Backward compatibility for optimisation algorithms

How to set our own Patrius compatibility configuration

The class PatriusConfiguration contains a setter setPatriusCompatibilityMode(PatriusVersionCompatibility) that allows to switch our own configuration as a function of the user needs.

Cette catégorie ne contient actuellement aucune page ni aucun média.