Main differences between V1.2.1 and V1.3
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 (specially with its new management of exceptions due to divisions by zero).
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.
Moreover, for events which manage multiple occurences, changes occured to be more obvious for the user with now three entries:
- From nth occurence - Every n occurence - Until nth occurence
=> incompatibility in the code due to the possibility to specify the list of available actions and to the occurence management
GPVehicle
The way to manage mass properties have ween 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.
=> incompatibility in the code due to additional arguments for the full constructor
GPAttitudeSequence
It is now possible to define an attitude sequence more simply that using switches, using a single attitude law.
Moreover, 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 lsits as allowed by the GENIUS GComponentList widget)
=> 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 ellipsoîd used as an entry is now mandatory 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
