« Main differences between V11.7.4 and V11.8 » : différence entre les versions
Aller à la navigation
Aller à la recherche
Aucun résumé des modifications |
|||
| Ligne 9 : | Ligne 9 : | ||
== Java Heap space management == | == Java Heap space management == | ||
The <font color=#FF8C00>Java</font> Heap space management when launching the <font color=#FF8C00 title="Graphical User Interface">'''GUI'''</font> may be done via | The <font color=#FF8C00>Java</font> Heap space management when launching the <font color=#FF8C00 title="Graphical User Interface">'''GUI'''</font> may be done via <font color=#FF8C00>Java</font> arguments but, when launching the computation via this <font color=#FF8C00 title="Graphical User Interface">'''GUI'''</font>, it was not possible to access to this option (as a new <font color=#FF8C00 title="Java Virtual Machine">'''JVM'''</font> is automatically launched to execute the propagation). Now, it is possible to specify the size of this heap space. | ||
== Look and Feel == | == Look and Feel == | ||
Version du 20 juin 2025 à 12:08
Output Mean models
It is now possible to choose the type of mean models for the output variables in the following list:
- Lyddane long periods
- Lyddane secular
- Eckstein Hechler
Java Heap space management
The Java Heap space management when launching the GUI may be done via Java arguments but, when launching the computation via this GUI, it was not possible to access to this option (as a new JVM is automatically launched to execute the propagation). Now, it is possible to specify the size of this heap space.
Look and Feel
By using the psimu.properties file, it is now possible to use different "Look And Feel" amongst this list:
- MetalLookAndFeel (by default)
- NimbusLookAndFeel
- MotifLookAndFeel
- WindowsLookAndFeel
- WindowsClassicLookAndFeel
- FlatLightLaf
- FlatDarkLaf
- FlatIntelliJLaf
- FlatDarculaLaf
Anomaly corrections
- The output mean variables were not converted in the inertial output frame but only in the inertial propagation one.
- When the initial orbit conditions were defined in a "H0-n" frame, an error message were displayed during the propagation if the epoch was after 2020.