« Main differences between V2.1.1 and V2.2 » : différence entre les versions
Aller à la navigation
Aller à la recherche
Aucun résumé des modifications |
Aucun résumé des modifications |
||
| (5 versions intermédiaires par le même utilisateur non affichées) | |||
| Ligne 1 : | Ligne 1 : | ||
This version is essentially due to an update of the lower level libraries [http://www.genius.fr GENIUS] V1.10.1 and http://www.patrius.fr PATRIUS] V4.6. | This version is essentially due to an update of the lower level libraries [http://www.genius.fr GENIUS] V1.10.1 and [http://www.patrius.fr PATRIUS] V4.6. | ||
== New reset option in the | == New reset option in the Copy/Paste menu == | ||
Thanks to the new [http://www.genius.fr GENIUS] version, there is now a new possibility in the '''Copy/Paste/…''' menu with the "'''Reset'''" option that allows to set data to their default values. | Thanks to the new [http://www.genius.fr GENIUS] version, there is now a new possibility in the '''Copy/Paste/…''' menu with the "'''Reset'''" option that allows to set data to their default values. | ||
| Ligne 8 : | Ligne 8 : | ||
The menu '''Copy/Paste/…''' is now available for [{{CurrentServer}}/uploads/JavaDocs/V2.1/fr/cnes/genopus/math/GPIntegrator.html GPIntegrator] widget. | The menu '''Copy/Paste/…''' is now available for [{{CurrentServer}}/uploads/JavaDocs/V2.1/fr/cnes/genopus/math/GPIntegrator.html GPIntegrator] widget. | ||
== GPOrbit and GPFramesConfiguration consistency == | |||
Thanks to the [http://www.genius.fr GENIUS] Observer/Observable interfaces, it is now possible to manage consistency between [{{PathCurrentJavaDoc}}/fr/cnes/genopus/orbits/GPOrbit.html GPOrbit] and [{{PathCurrentJavaDoc}}/fr/cnes/genopus/frames/GPFramesConfiguration.html GPFramesConfiguration] widgets. | |||
== GPAttitudeSequence default laws initialization == | == GPAttitudeSequence default laws initialization == | ||
| Ligne 15 : | Ligne 19 : | ||
== Anomaly corrections == | == Anomaly corrections == | ||
* There were some problems with the fact that, since V2.0, <font color=#556B2F>'''GENOPUS'''</font> is able to store in a context file, both "'''Pivot'''" and "'''Display'''" data for orbital conditions using the [{{PathCurrentJavaDoc}}/fr/cnes/genopus/orbits/GPOrbit.html GPOrbit] class. Indeed : | * There were some problems with the fact that, since V2.0, <font color=#556B2F>'''GENOPUS'''</font> is able to store in a context file, both "'''Pivot'''" and "'''Display'''" data for orbital conditions using the [{{PathCurrentJavaDoc}}/fr/cnes/genopus/orbits/GPOrbit.html GPOrbit] class. Indeed: | ||
** if "'''Pivot'''" and "'''Display'''" frames were not the same, <font color=#556B2F>'''GENOPUS'''</font> considered orbital parameters coming from the "'''Pivot'''" data and frame characteristics from the "'''Display'''" ones <u> which was of course totally wrong</u>. | ** if "'''Pivot'''" and "'''Display'''" frames were not the same, <font color=#556B2F>'''GENOPUS'''</font> considered orbital parameters coming from the "'''Pivot'''" data and frame characteristics from the "'''Display'''" ones <u> which was of course totally wrong</u>. | ||
** if the user modified the context file not through a <font color=#556B2F>'''GENIUS/GENOPUS'''</font> <font color=#FF8C00 title="Graphical User Interface">GUI</font>, it had to modify both "'''Pivot'''" and "'''Display'''" data in order to keep consistency between both data. | ** if the user modified the context file not through a <font color=#556B2F>'''GENIUS/GENOPUS'''</font> <font color=#FF8C00 title="Graphical User Interface">GUI</font>, it had to modify both "'''Pivot'''" and "'''Display'''" data in order to keep consistency between both data. | ||
* Always using the [{{PathCurrentJavaDoc}}/fr/cnes/genopus/orbits/GPOrbit.html GPOrbit] class, when modifying constants (for example µ) of initial orbital conditions (even only the units), a conversion was done which was useless. | * Always using the [{{PathCurrentJavaDoc}}/fr/cnes/genopus/orbits/GPOrbit.html GPOrbit] class, when modifying constants (for example µ) of initial orbital conditions (even only the units), a conversion was done which was useless. | ||
* Wrong management of the [http://www.genius.fr GENIUS] Observer/Observable interfaces in some widgets. | * Wrong management of the [http://www.genius.fr GENIUS] Observer/Observable interfaces in some widgets. | ||
Dernière version du 16 février 2021 à 08:37
This version is essentially due to an update of the lower level libraries GENIUS V1.10.1 and PATRIUS V4.6.
Thanks to the new GENIUS version, there is now a new possibility in the Copy/Paste/… menu with the "Reset" option that allows to set data to their default values.
Adding Copy/Paste/… for GPIntegrator widget
The menu Copy/Paste/… is now available for GPIntegrator widget.
GPOrbit and GPFramesConfiguration consistency
Thanks to the GENIUS Observer/Observable interfaces, it is now possible to manage consistency between GPOrbit and GPFramesConfiguration widgets.
GPAttitudeSequence default laws initialization
It is now possible to better customize the default attitude laws used inside the GPAttitudeSequence widget.
Anomaly corrections
- There were some problems with the fact that, since V2.0, GENOPUS is able to store in a context file, both "Pivot" and "Display" data for orbital conditions using the GPOrbit class. Indeed:
- if "Pivot" and "Display" frames were not the same, GENOPUS considered orbital parameters coming from the "Pivot" data and frame characteristics from the "Display" ones which was of course totally wrong.
- if the user modified the context file not through a GENIUS/GENOPUS GUI, it had to modify both "Pivot" and "Display" data in order to keep consistency between both data.
- Always using the GPOrbit class, when modifying constants (for example µ) of initial orbital conditions (even only the units), a conversion was done which was useless.
- Wrong management of the GENIUS Observer/Observable interfaces in some widgets.