Main differences between V2.1 and V2.1.1 : Différence entre versions

Version du 31 octobre 2019 à 11:20

This version is mainly due to the correction of both 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 tolérances 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 tolérances 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 tolérances > 0
    • relative toerances >=0.
  • methods to get reduced tolérances (see corresponding anomalies).

• in GPDop85.3 widget :
  • method to get the widget giving help for tolérances 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.