« Main differences between V2.1 and V2.1.1 » : différence entre les versions

De GENOPUS
Aller à la navigation Aller à la recherche
Aucun résumé des modifications
 
(Une version intermédiaire par le même utilisateur non affichée)
Ligne 22 : Ligne 22 :
** method to get the widget giving help for tolerances definition (needed to manage externally a "before/after" action on it).
** method to get the widget giving help for tolerances definition (needed to manage externally a "before/after" action on it).


At last, some constructor and methods, will potentially throw a GIntervalException (and no more a GPDateException which was not useful).
At last, some constructor and methods, will potentially throw a <font color=#4169E1>GIntervalException</font> (and no more a [{{CurrentServer}}/uploads/JavaDocs/V2.1/fr/cnes/genopus/exception/GPDateException.html GPDateException] which was not useful).


== Anomaly corrections ==
== Anomaly corrections ==


* Saving displayed orbit as well as the "pivot" reference is now correctly working. Indeed in the previous V2.1 version:
* Saving displayed orbit as well as the "pivot" reference is now correctly working. Indeed, in the previous V2.1 version:
** if the user only modified the type of anomaly then saved, this change was not recovered in the saved file. Thus, the next load displayed the original type of anomaly.
** if the user only modified the type of anomaly then saved, this change was not recovered in the saved file. Thus, the next load displayed the original type of anomaly.
** if the user modified the type of parameters and afterwards changed again the type of anomaly, for display, only the type of parameters was saved and the next load displayed a true anomaly. Note that anyway, even in this new version, when you change the type of parameters, the anomaly is automatically set to "true".
** if the user modified the type of parameters and afterwards changed again the type of anomaly, for display, only the type of parameters was saved and the next load displayed a true anomaly. Note that anyway, even in this new version, when you change the type of parameters, the anomaly is automatically set to "true".
* In the [{{CurrentServer}}/uploads/JavaDocs/V2.1/fr/cnes/genopus/math/GPIntegrator.html GPIntegrator] widget, updating tolerances was not correctly done for "Reduced" mode.
* In the [{{CurrentServer}}/uploads/JavaDocs/V2.1/fr/cnes/genopus/math/GPIntegrator.html GPIntegrator] widget, updating tolerances was not correctly done for "Reduced" mode.

Dernière version du 4 novembre 2019 à 08:44

This version is mainly due to the correction of two anomalies listes below …

Improvement of interfaces with GPIntegrator/GPDop853 widgets

To better use these widgets, some methods have been Added:

  • in GPIntegrator widget :
    • a getter to know which type of integrator has been selected.
    • a getter to know which kind of tolerances has been selected.
    • two getters to directly get the widgets used for min and max step of the Dormand Price 853 integrator (needed to manage externally a "before/after" action on them).
    • a setter allowing displaying or not tolerances on the mass.
  • in GPIntegrator and GPDop853 widgets:
    • validity intervals and methods to modify them. By default, these intervals are:
      • constant time step > 0
      • 0 < min step ≤ max step
      • absolute tolerances > 0
      • relative tolerances ≥ 0.
    • methods to get reduced tolerances (see corresponding anomalies).
  • in GPDop853 widget :
    • method to get the widget giving help for tolerances definition (needed to manage externally a "before/after" action on it).

At last, some constructor and methods, will potentially throw a GIntervalException (and no more a GPDateException which was not useful).

Anomaly corrections

  • Saving displayed orbit as well as the "pivot" reference is now correctly working. Indeed, in the previous V2.1 version:
    • if the user only modified the type of anomaly then saved, this change was not recovered in the saved file. Thus, the next load displayed the original type of anomaly.
    • if the user modified the type of parameters and afterwards changed again the type of anomaly, for display, only the type of parameters was saved and the next load displayed a true anomaly. Note that anyway, even in this new version, when you change the type of parameters, the anomaly is automatically set to "true".
  • In the GPIntegrator widget, updating tolerances was not correctly done for "Reduced" mode.