Main differences between V11.0 and V11.1 - Historique des versions

Admin : /* Anomaly corrections */

2017-11-16T10:09:25Z

Anomaly corrections

← Version précédente		Version du 16 novembre 2017 à 10:09
Ligne 63 :		Ligne 63 :
	== Anomaly corrections ==		== Anomaly corrections ==

	* In the previous version, sometimes the JVM continued to run after exiting the GUI application		* In the previous version, sometimes the <font color=#FF8C00 title="Java Virtual Machine">JVM</font> continued to run after exiting the <font color=#FF8C00 title="Graphical User Interface">GUI</font> application
	* After reading a scenario file, if an error (exception) is raised as the absolute path of the file contains some blank characters, nothing previously occured (i.e. no messages appeared while data do not have been loaded) => now corrected in V11.1		* After reading a scenario file, if an error (exception) is raised as the absolute path of the file contains some blank characters, nothing previously occured (i.e. no messages appeared while data do not have been loaded) => now corrected in V11.1
	* bug when displaying perigee altitude.		* bug when displaying perigee altitude.
	* bad update of the units for date offsets.		* bad update of the units for date offsets.

Admin : /* Improvement of graphical displays */

2017-11-16T10:06:50Z

Improvement of graphical displays

← Version précédente		Version du 16 novembre 2017 à 10:06
Ligne 38 :		Ligne 38 :
	== Improvement of graphical displays ==		== Improvement of graphical displays ==

	Now, it is not necessary to load the current result file. Moreover some improvement ~~have~~ been implemented as a better up to date of the title or the management of discontinuities (for example when plotting latitudes or longitudes).		Now, it is not necessary to load the current result file. Moreover some improvement has been implemented as a better up to date of the title or the management of discontinuities (for example when plotting latitudes or longitudes).

	== Variable names ==		== Variable names ==

Admin : /* GUI improvements */

2017-11-16T10:05:29Z

GUI improvements

← Version précédente		Version du 16 novembre 2017 à 10:05
Ligne 7 :		Ligne 7 :
	== GUI improvements ==		== GUI improvements ==

	* Some '''Copy&Paste''' (and '''Import/Export''') ~~functionnalities~~ have been added to some widgets as for the orbital initial conditions or the maneuvers.		* Some '''Copy&Paste''' (and '''Import/Export''') functionalities have been added to some widgets as for the orbital initial conditions or the maneuvers.
	* For events which manage multiple occurrences, changes occurred to be more obvious for the user with now three entries:		* 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		** From n<sup>th</sup> occurrence

Admin : /* Compatibility with PATRIUS V3.3 */

2017-11-16T10:04:48Z

Compatibility with PATRIUS V3.3

← Version précédente		Version du 16 novembre 2017 à 10:04
Ligne 3 :		Ligne 3 :
	== Compatibility with PATRIUS V3.3 ==		== Compatibility with PATRIUS V3.3 ==

	This <font color=#556B2F>'''PSIMU'''</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 as well as corrections when taking into account surface force models in conjunction with continuous thrust (numerical aspects).		This <font color=#556B2F>'''PSIMU'''</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 as well as corrections when taking into account surface force models in conjunction with continuous thrust (numerical aspects).

	== GUI improvements ==		== GUI improvements ==

Admin le 16 novembre 2017 à 10:03

2017-11-16T10:03:05Z

← Version précédente		Version du 16 novembre 2017 à 10:03
Ligne 1 :		Ligne 1 :
	This version includes essentially ~~ergonomy~~ improvement of the tool. Nevertheless, some new functionalities as [https://www.sqlite.org/ SQLite] output files have a real interest.		This version includes essentially ergonomic improvement of the tool. Nevertheless, some new functionalities as [https://www.sqlite.org/ SQLite] output files have a real interest.

	== Compatibility with PATRIUS V3.3 ==		== Compatibility with PATRIUS V3.3 ==

Admin : /* Output storage */

2017-11-16T09:41:40Z

Output storage

← Version précédente		Version du 16 novembre 2017 à 09:41
Ligne 55 :		Ligne 55 :
	== Output storage ==		== Output storage ==

	Rather than to use a binary file as in the previous version, the output of the computation including all computed intermediate parameters (with the output step as defined by the user as well as orbital events) are stored in a [https://www.sqlite.org/ SQLite] formatted file which can be read directly by <font color=#556B2F>'''PSIMU'''</font> plots but also by other tools compatible with this format.		Rather than to use a binary file as in the previous version, the output of the computation including all computed intermediate parameters (with the output step as defined by the user as well as orbital events) are stored in a [https://www.sqlite.org/ SQLite] formatted file which can be read directly by <font color=#556B2F>'''PSIMU'''</font> plots but also by many other tools (some are free) compatible with this format.

	Moreover, when using the master mode, an additional parameter is used to define how output data are stored.		Moreover, when using the master mode, an additional parameter is used to define how output data are stored.

Admin : /* Output storage */

2017-11-07T16:37:48Z

Output storage

← Version précédente		Version du 7 novembre 2017 à 16:37
Ligne 59 :		Ligne 59 :
	Moreover, when using the master mode, an additional parameter is used to define how output data are stored.		Moreover, when using the master mode, an additional parameter is used to define how output data are stored.

	=> <font color=#990099>incompatibility in the code due to an additional argument in the ~~OutputConfig constructor~~. ~~Moreoever, method~~ getListOfSpacecraftStates() is renamed as getSpacecraftStateList().</font>		=> <font color=#990099>incompatibility in the code due to an additional argument in the propagateInMasterMode() method. Method getListOfSpacecraftStates() is also renamed as getSpacecraftStateList().</font>

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

Admin : /* Output storage */

2017-11-07T16:35:24Z

Output storage

← Version précédente		Version du 7 novembre 2017 à 16:35
Ligne 59 :		Ligne 59 :
	Moreover, when using the master mode, an additional parameter is used to define how output data are stored.		Moreover, when using the master mode, an additional parameter is used to define how output data are stored.

	=> <font color=#990099>incompatibility in the code due to an additional argument in the OutputConfig constructor. ~~Method~~ getListOfSpacecraftStates() is renamed as getSpacecraftStateList()</font>		=> <font color=#990099>incompatibility in the code due to an additional argument in the OutputConfig constructor. Moreoever, method getListOfSpacecraftStates() is renamed as getSpacecraftStateList().</font>

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

Admin : /* Output storage */

2017-11-07T16:34:46Z

Output storage

← Version précédente		Version du 7 novembre 2017 à 16:34
Ligne 56 :		Ligne 56 :

	Rather than to use a binary file as in the previous version, the output of the computation including all computed intermediate parameters (with the output step as defined by the user as well as orbital events) are stored in a [https://www.sqlite.org/ SQLite] formatted file which can be read directly by <font color=#556B2F>'''PSIMU'''</font> plots but also by other tools compatible with this format.		Rather than to use a binary file as in the previous version, the output of the computation including all computed intermediate parameters (with the output step as defined by the user as well as orbital events) are stored in a [https://www.sqlite.org/ SQLite] formatted file which can be read directly by <font color=#556B2F>'''PSIMU'''</font> plots but also by other tools compatible with this format.

			Moreover, when using the master mode, an additional parameter is used to define how output data are stored.

			=> <font color=#990099>incompatibility in the code due to an additional argument in the OutputConfig constructor. Method getListOfSpacecraftStates() is renamed as getSpacecraftStateList()</font>

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

Admin : /* Anomaly corrections */

2017-10-26T15:25:30Z

Anomaly corrections

← Version précédente		Version du 26 octobre 2017 à 15:25
Ligne 59 :		Ligne 59 :
	== Anomaly corrections ==		== Anomaly corrections ==

			* In the previous version, sometimes the JVM continued to run after exiting the GUI application
			* After reading a scenario file, if an error (exception) is raised as the absolute path of the file contains some blank characters, nothing previously occured (i.e. no messages appeared while data do not have been loaded) => now corrected in V11.1
	* bug when displaying perigee altitude.		* bug when displaying perigee altitude.
	* bad update of the units for date offsets.		* bad update of the units for date offsets.

Main differences between V11.0 and V11.1 - Historique des versions

Admin : /* Anomaly corrections */

Admin : /* Improvement of graphical displays */

Admin : /* GUI improvements */

Admin : /* Compatibility with PATRIUS V3.3 */

Admin le 16 novembre 2017 à 10:03

Admin : /* Output storage */

Admin : /* Output storage */

Admin : /* Output storage */

Admin : /* Output storage */

Admin : /* Anomaly corrections */

Admin : /* Anomaly corrections */

Admin : /* Improvement of graphical displays */

Admin : /* GUI improvements */

Admin : /* Compatibility with PATRIUS V3.3 */

Admin : /* Output storage */

Admin : /* Output storage */

Admin : /* Output storage */

Admin : /* Output storage */

Admin : /* Anomaly corrections */