Voir la source de Main differences between V11.3 and V11.4

== Compatibility with PATRIUS ==

This version is compatible with the version 4.4 of the [http://patrius.cnes.fr PATRIUS] library.

== New maneuvers trigerring criteriae ==

Thanks to the V2.1 version of [http://genopus.cnes.fr GENOPUS], new criteriae on nodes and apsides have been added to the previous ones (relative or absolute dates and <font color=#FF8C00 title="Argument Of Latitude">AOL</font>)

== Impulsive maneuvers with orbital parameters criteriae ==

Thanks to the V2.1 version of [http://genopus.cnes.fr GENOPUS], it is now possible to define an impulsive maneuver giving orbital parameters increments:
* on semi-major axis
* on eccentricity (and semi-major axis eventually)
* on inclination (and semi-major axis eventually)

== Recurrent date events ==

Thanks to the V2.1 version of [http://genopus.cnes.fr GENOPUS], it is now possible to define date (relative or absolute ones) events with a recurrence (for example each day).

== Minimum step citeria on Dormand Price 853 integrator ==

Thanks to the V4.4 version of [http://patrius.cnes.fr PATRIUS] and the V2.1 version of [http://genopus.cnes.fr GENOPUS] with its new specific widget, it is now possible to by-pass the <font color=#FF8C00>Dormand Price 853</font> error mode on the minimum step. When this solution is chosen, the propagation will go on even if the conditions on precision will not be temporary fulfilled.

== Additional validity criteria on PRS coefficients ==

Thanks to the V2.1 version of [http://genopus.cnes.fr GENOPUS], besides validity interval of [0,1] for each coefficient, there is an additional test on the sum of the three coefficients (absorption, specular and diffuse) that must be equal to 1.

== Altitudes on stop criteria ==

It is now possible to choose if the stop criteria will be a geocentric or geodetic altitude.

== Best management of consistency between force model and vehicle panels ==

In the previous versions, if we decided to select an atmospheric model without entering data on mass and aerodynamic coefficients, the error was only detected when launching the propagation. Now it is detected sooner and the vehicle tab becomes red as it shifts in error mode.

== By default attitude law ==

Now an attitude law is defined by default (TNW) to avoid to select if it is not critical.

== Ergonomics change for output variables selection ==

TBW ...

== New output variables ==

New variables are now available:
* '''F107''' (Solar Flux / 0 if the atmospheric model does not use it)
* '''AP''' (Geomagnetic index / 0 if the atmospheric model does not use it)
* '''DV''' (Cumulated velocity increment in m/s / 0 if no maneuvers)

Moreover, the time scale used for dates may be selected in the [[Output#List_of_available_variables|Output]] panel (<font color=#FF8C00 title="Coordinated Universal Time">UTC</font> by default)

== Possibility to customize its own output variables ==

TBW …

== New output modes ==

Previously, using <font color=#FF8C00>Java</font> interface, only three output modes were available:

* StorageType.'''MEMORY''' ⇒ spacecraft states memory stored
* StorageType.'''FILE_SC_BINARY''' ⇒ spacecraft states directly stored in a [http://genius.cnes.fr/index.php/ResultsFileManagement#SqLite_files SQLite format] file
* StorageType.'''FILE_COLUMNS''' ⇒ output variables stored in a [http://genius.cnes.fr/index.php/ResultsFileManagement#SqLite_files SQLite format] file

Now, it is possible to combine any kind of output modes, using the following states:

* StorageType.'''MEMORY_SC''' (ex StorageType.'''MEMORY''') ⇒ spacecraft states memory stored
* StorageType.'''MEMORY_COL''' ⇒ output variables memory stored; possibility to get them using <font color=#4169E1>getVarsList()</font>, <font color=#4169E1>getVars(index)</font>, <font color=#4169E1>getVar(index,key)</font> methods
* StorageType.'''MEMORY_ALL''' ⇒ '''MEMORY_SC''' et '''MEMORY_COL''' 
* StorageType.'''NONE''' ⇒ no memory storage

* StorageType.'''FILE_SC''' (ex StorageType.'''FILE_SC_BINARY''') ⇒ spacecraft states stored in a file
* StorageType.'''FILE_COL''' (ex StorageType.'''FILE_COLUMNS''') ⇒ output variables stored in a file
* StorageType.'''FILE_ALL''' ⇒ StorageType.'''FILE_SC''' et StorageType.'''FILE_COL'''
* StorageType.'''NONE''' ⇒ no files

In order to differentiate memory vs file choice, the <font color=#4169E1>propagateInMasterMode()</font> method can accept both states as in the examples below:

<syntaxhighlight lang="java">
test.propagateInMasterMode(output, events, StorageType.MEMORY_SC, StorageType.NONE);
</syntaxhighlight>

⇒ only spacecraft states memory stored (equivalent to the old '''MEMORY''' state)

<syntaxhighlight lang="java">
test.propagateInMasterMode(output, events, StorageType.NONE, StorageType.File_COL);
</syntaxhighlight>

⇒ no memory storage and output variables stored in a file (as the old '''FILE_COLUMNS''' state)

<syntaxhighlight lang="java">
test.propagateInMasterMode(output, events, StorageType.MEMORY_SC, StorageType.File_ALL);
</syntaxhighlight>

⇒ spacecraft states stored both in memory and file as output variables will be stored in a file.

At last, to manage output variables as spacecraft states, these methods are available:

* <font color=#4169E1>getVariablesList()</font>, <font color=#4169E1>getVariablesWithoutEventsList()</font>, <font color=#4169E1>getVariablesOnlyEventsList()</font>
* <font color=#4169E1>getVariables(index)</font>, <font color=#4169E1>getVariablesWithoutEvents(index)</font>, <font color=#4169E1>getVariablesOnlyEvents(index)</font>
* <font color=#4169E1>getVariable (index, key)</font>, <font color=#4169E1>getVariableWithoutEvents(index, key)</font>, <font color=#4169E1>getVariableOnlyEvents(index, key)</font>

== Some new util methods ==

The Following methods have been declared as "public":

* to read a [http://genius.cnes.fr/index.php/ResultsFileManagement#SqLite_files SQLite format] file and extract  spacecraft states:

<syntaxhighlight lang="java">
public static List<SpacecraftState> readSpacecraftStatesFromFile ( final boolean isEphem, final boolean isEvent, final String outputDirectory, final String nameFile, final String varName )
</syntaxhighlight>

* to convert a spacecraft state in String and vice versa:

<syntaxhighlight lang="java">
public static SpacecraftState fromBase64(final String spacecraftStateString)
public static String toBase64(final SpacecraftState currentState)
</syntaxhighlight>

* to read a [http://genius.cnes.fr/index.php/ResultsFileManagement#SqLite_files SQLite format] file and extract a list of variables:

<syntaxhighlight lang="java">
public static List<HashMap<String, Object>> readVariablesFromFile( final boolean isEphem, final boolean isEvent, final String outputDirectory, final String nameFile, final ArrayList<String> listOfVarnames )
</syntaxhighlight>

== Anomaly corrections ==

* Corrections due to [http://genopus.cnes.fr GENOPUS] anomalies
** Impossibility to initialize an orbit using a H0-n frame.
**  Calling [{{PathCurrentJavaDoc}}/fr/cnes/genopus/events/GPVisibilityFromStationDetector.html GPVisibilityFromStationDetector] or [{{PathCurrentJavaDoc}}/fr/cnes/genopus/attitudes/GPAttitudeSequence.html GPAttitudeSequence] widgets make the tool incompatible with a headless mode (no display).
* <font color=#556B2F>'''PSIMU'''</font> is now able to propagate a trajectory using initial orbital parameters correspond to an hyperbolic trajectory.
* when propagation duration is exactly equals to zero, <font color=#556B2F>'''PSIMU'''</font> will no more exit in error.
* use of mean zonal terms was previously wrong in case of ''Droziner'' or ''Cunningham'' équations  (not available in <font color=#FF8C00 title="Graphical User Interface">GUI</font> mode); it is now corrected.
* In <font color=#FF8C00>Java</font> mode, using '''FILE_SC_BINARY''' output option, calling <font color=#4169E1>getSpacecraftStateList()</font> or <font color=#4169E1>getSpacecraftState(i)</font> methods now gives the same kind of results (sort problem corrected).
* geocentric altitude and latitude (so in <font color=#FF8C00 title="International Terrestrial Reference Frame">ITRF</font> frame) are now correctly computed.