Main differences between V1.2.1 and V1.3 : Différence entre versions
De Wiki
(→Compatibility with PATRIUS V3.3) |
|||
| (30 révisions intermédiaires par le même utilisateur non affichées) | |||
| Ligne 1 : | Ligne 1 : | ||
| − | Some corrections and new features mainly due to the update of the | + | Some corrections and new features mainly due to the update of the [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] version (3.3) and use of <font color=#556B2F>'''GENOPUS'''</font> by [http://10.120.3.224/index.php/WELCOME_TO_THE_PSIMU_WIKI PSIMU]. |
== Compatibility with PATRIUS V3.3 == | == Compatibility with PATRIUS V3.3 == | ||
| − | This <font color=#556B2F>'''GENOPUS'''</font> version is compatible with | + | This <font color=#556B2F>'''GENOPUS'''</font> version is compatible with [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] V3.3 (especially with its new management of exceptions due to divisions by zero). |
| − | == | + | == Copy&Paste == |
| − | + | Some '''Copy&Paste''' (and '''Import/Export''') functionnalities have been added to <font color=#556B2F>'''GENOPUS'''</font> widgets as [{{PathCurrentJavaDoc}}/fr/cnes/genopus/orbits/GPOrbit.html GPOrbit], [{{PathCurrentJavaDoc}}/fr/cnes/genopus/vehicle/GPVehicle.html GPVehicle], [{{PathCurrentJavaDoc}}/fr/cnes/genopus/maneuvers/GPManeuverSequence.html GPManeuverSequence], ...) | |
| − | + | == GPFramesConfiguration == | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | => <font color=#990099>incompatibility in the code due to the possibility to specify the list of available actions and to the | + | It is now possible to initialize the [{{PathCurrentJavaDoc}}/fr/cnes/genopus/frames/GPFramesConfiguration.html GPFramesConfiguration] widget with a specific configuration not necessarily issued from a Factory thanks to <font color=#4169E1>setFramesConfiguration()</font>, <font color=#4169E1>setDefaultFramesConfiguration()</font> and <font color=#4169E1>setSavedFramesConfiguration()</font> as well as adapted constructors with a <font color=#4169E1>FramesConfiguration</font> object as input. |
| + | |||
| + | == GPEventDetectors == | ||
| + | |||
| + | * It is now possible to specify the list of available actions associated to the event and, when only one action is indicated, it does not appear on the <font color=#FF8C00 title="Graphical User Interface">GUI</font>. | ||
| + | * for events which manage multiple occurrences, changes occurred to be more obvious for the user with now three entries: | ||
| + | ** From n<sup>th</sup> occurrence | ||
| + | ** Every n occurrence | ||
| + | ** Until n<sup>th</sup> occurrence | ||
| + | * There is no more CodingEvents in the events definition | ||
| + | |||
| + | => <font color=#990099>incompatibility in the code due to the possibility to specify the list of available actions and to the occurrence management</font> | ||
== GPVehicle == | == GPVehicle == | ||
| − | The way to manage mass properties | + | The way to manage mass properties has been improved in order to allow to make mandatory the fact to display dry mass value. Moreover, when this value is equal to zero, it raises a warning and no more an error. |
== GPForceModels == | == GPForceModels == | ||
| − | It is possible now to hide the choice of the "attraction models" (i.e. Balmino, Cunnigham, ...) as well as to define which models will be displayed. | + | * It is possible now to hide the choice of the "attraction models" (i.e. <font color=#FF8C00>Balmino</font>, <font color=#FF8C00>Cunnigham</font>, ...) as well as to define which models will be displayed. |
| + | * Maximum degrees are now displayed when variable potential is selected. | ||
| + | * By default values are proposed for <font color=#FF8C00 title="Solar Radiative Pressure">SRP</font>. | ||
| + | * Name of the model must be set as a new parameter of the constructor. | ||
=> <font color=#990099>incompatibility in the code due to additional arguments for the full constructor</font> | => <font color=#990099>incompatibility in the code due to additional arguments for the full constructor</font> | ||
| − | == | + | == GPManeuvers == |
| − | + | * If engines and/or tanks needed to define a maneuver is set to '''NONE''', the maneuver (and the sequence) raised an error. | |
| + | * by default, maneuvers components are set to "'''Angular'''" as event is a "'''Relative date'''". | ||
| − | + | == GPAttitudeSequence == | |
| + | |||
| + | * It is now possible to define an attitude sequence more simply that using switches, using a single attitude law. | ||
| + | * the constructor has changed as it is also possible to define how the attitude laws list wil be displayed (one by one or all in a vertical lists allowed by the [http://10.120.3.216/index.php/GComponentList GENIUS GComponentList] widget. | ||
| + | * If an attitude law is set to '''NONE''', the sequence raised an error. | ||
| + | * only '''RESET_STATE''' or '''RESET_DERIVATIVE''' may be selected as actions for switch events. | ||
| + | * by default, attitude laws angular bias definition is set to "'''ZYX Cardan Angles'''". | ||
=> <font color=#990099>incompatibility in the code due to the new boolean flag</font> | => <font color=#990099>incompatibility in the code due to the new boolean flag</font> | ||
| Ligne 42 : | Ligne 60 : | ||
== CustomUS76, CustomMSISE2000 == | == CustomUS76, CustomMSISE2000 == | ||
| − | The | + | The ellipsoid used as an entry is now necessarily a [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] <font color=#4169E1>ExtendedOneAxisellipoid</font> object and no more a <font color=#4169E1>BodyShape</font> which is one of its interface. |
=> <font color=#990099>may be some incompatibility in the code if the BodyShape interface was used</font> | => <font color=#990099>may be some incompatibility in the code if the BodyShape interface was used</font> | ||
| + | |||
| + | == Variable names == | ||
| + | |||
| + | Some names changed in the XML files in order to be more consistent (for example, capitals vs lowercase letters). | ||
| + | |||
| + | => <font color=#990099>some incompatibility with old XML files</font> | ||
| + | |||
| + | == Anomaly corrections == | ||
| + | |||
| + | * bad management of the clear function of the [{{PathCurrentJavaDoc}}/fr/cnes/genopus/vehicle/GPVehicle.html GPVehicle] when it is noit yet initialized | ||
| + | * problem in the <font color=#4169E1>getLaw()</font> method of the [{{PathCurrentJavaDoc}}/fr/cnes/genopus/attitudes/GPSunPointingAttitudeLaw.html GPSunPointingAttitudeLaw] class as the first argument when creating the [{{PathCurrentJavaDoc}}/fr/cnes/genopus/nonWidget/attitudes/CustomSunPointing.html CustomSunPointing] object was the Sun. It implied that the second direction was normal to the satellite orbit rather than the poles axis as described. | ||
| + | * bad update of the units for the [{{PathCurrentJavaDoc}}/fr/cnes/genopus/time/GPDateOffset.html GPDateOffset] widget. | ||
| + | * bug when the initial list of maneuvers was null. | ||
| + | * bug when a rotation was initialized | ||
Version actuelle en date du 14 novembre 2017 à 12:30
Some corrections and new features mainly due to the update of the [PATRIUS] version (3.3) and use of GENOPUS by PSIMU.
Sommaire
Compatibility with PATRIUS V3.3
This GENOPUS version is compatible with [PATRIUS] V3.3 (especially with its new management of exceptions due to divisions by zero).
Copy&Paste
Some Copy&Paste (and Import/Export) functionnalities have been added to GENOPUS widgets as GPOrbit, GPVehicle, GPManeuverSequence, ...)
GPFramesConfiguration
It is now possible to initialize the GPFramesConfiguration widget with a specific configuration not necessarily issued from a Factory thanks to setFramesConfiguration(), setDefaultFramesConfiguration() and setSavedFramesConfiguration() as well as adapted constructors with a FramesConfiguration object as input.
GPEventDetectors
- It is now possible to specify the list of available actions associated to the event and, when only one action is indicated, it does not appear on the GUI.
- for events which manage multiple occurrences, changes occurred to be more obvious for the user with now three entries:
- From nth occurrence
- Every n occurrence
- Until nth occurrence
- There is no more CodingEvents in the events definition
=> incompatibility in the code due to the possibility to specify the list of available actions and to the occurrence management
GPVehicle
The way to manage mass properties has been improved in order to allow to make mandatory the fact to display dry mass value. Moreover, when this value is equal to zero, it raises a warning and no more an error.
GPForceModels
- It is possible now to hide the choice of the "attraction models" (i.e. Balmino, Cunnigham, ...) as well as to define which models will be displayed.
- Maximum degrees are now displayed when variable potential is selected.
- By default values are proposed for SRP.
- Name of the model must be set as a new parameter of the constructor.
=> incompatibility in the code due to additional arguments for the full constructor
GPManeuvers
- If engines and/or tanks needed to define a maneuver is set to NONE, the maneuver (and the sequence) raised an error.
- by default, maneuvers components are set to "Angular" as event is a "Relative date".
GPAttitudeSequence
- It is now possible to define an attitude sequence more simply that using switches, using a single attitude law.
- the constructor has changed as it is also possible to define how the attitude laws list wil be displayed (one by one or all in a vertical lists allowed by the GENIUS GComponentList widget.
- If an attitude law is set to NONE, the sequence raised an error.
- only RESET_STATE or RESET_DERIVATIVE may be selected as actions for switch events.
- by default, attitude laws angular bias definition is set to "ZYX Cardan Angles".
=> incompatibility in the code due to the new boolean flag
GPGeodeticPoint
A new argument has been added to the constructor with a boolean that indicates if the name of the geodetic point will be displayed or not.
=> incompatibility in the code due to the new boolean flag
CustomUS76, CustomMSISE2000
The ellipsoid used as an entry is now necessarily a [PATRIUS] ExtendedOneAxisellipoid object and no more a BodyShape which is one of its interface.
=> may be some incompatibility in the code if the BodyShape interface was used
Variable names
Some names changed in the XML files in order to be more consistent (for example, capitals vs lowercase letters).
=> some incompatibility with old XML files
Anomaly corrections
- bad management of the clear function of the GPVehicle when it is noit yet initialized
- problem in the getLaw() method of the GPSunPointingAttitudeLaw class as the first argument when creating the CustomSunPointing object was the Sun. It implied that the second direction was normal to the satellite orbit rather than the poles axis as described.
- bad update of the units for the GPDateOffset widget.
- bug when the initial list of maneuvers was null.
- bug when a rotation was initialized
