Psimu - Contributions [fr]

Modèle:PathCurrentJavaDoc

2025-10-13T09:39:47Z

Admin :

{{CurrentServer}}//images/upload/JavaDocs/V11.8

Java Doc

2025-10-13T09:37:10Z

Admin :

[{{PathCurrentJavaDoc}} Current Java Doc] 

[{{CurrentServer}}/images/upload/JavaDocs/V11.8 Java Doc 11.8] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.7.4 Java Doc 11.7.4] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.7.3 Java Doc 11.7.3] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.7.2 Java Doc 11.7.2] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.7.1 Java Doc 11.7.1] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.6.2 Java Doc 11.6.2] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.5 Java Doc 11.5] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.4.1 Java Doc 11.4.1] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.4 Java Doc 11.4] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.3 Java Doc 11.3] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.2 Java Doc 11.2] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.1 Java Doc 11.1] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.0 Java Doc 11.0]

Fichier:TutorialsForV11.8.zip

2025-10-10T15:34:33Z

Admin :

MediaWiki:Sidebar

2025-10-10T15:33:26Z

Admin :

*
* PSIMU
** WELCOME_TO_THE_PSIMU_WIKI|Welcome
** Quick_start|Quick start
** News|News
* GUI Mode
** Overall_Presentation|Overall presentation
** Initial_Orbit|Initial Orbit
** Earth_Features|Earth features
** Vehicle|Vehicle
** Forces|Forces
** Maneuvers|Maneuvers
** Attitude|Attitude
** Integrator|Integrator
** Events|Events
** Output|Output
** Console|Console
* Batch mode
** BatchMode|How to call it
* Java interface
** Basic_Principle|Basic principle
** Data_initialization|Data initialization
** Propagation|Propagation
** Printing|Printing results
** Customize_output_variables|Customize output variables
* Evolutions
** Main_differences_between_V11.7.4_and_V11.8|Main differences between V11.7.4 and V11.8
** Main_differences_between_V11.7.3_and_V11.7.4|Main differences between V11.7.3 and V11.7.4
** Main_differences_between_V11.7.2_and_V11.7.3|Main differences between V11.7.2 and V11.7.3
** Main_differences_between_V11.7.1_and_V11.7.2|Main differences between V11.7.1 and V11.7.2
** Main_differences_between_V11.6.2_and_V11.7.1|Main differences between V11.6.2 and V11.7.1
** Main_differences_between_V11.5_and_V11.6.2|Main differences between V11.5 and V11.6.2
** Main_differences_between_V11.4.1_and_V11.5|Main differences between V11.4.1 and V11.5
** Main_differences_between_V11.4_and_V11.4.1|Main differences between V11.4 and V11.4.1
** Main_differences_between_V11.3_and_V11.4|Main differences between V11.3 and V11.4
** Main_differences_between_V11.2_and_V11.3|Main differences between V11.2 and V11.3
** Main_differences_between_V11.1_and_V11.2|Main differences between V11.1 and V11.2
** Main_differences_between_V11.0_and_V11.1|Main differences between V11.0 and V11.1
* Training
** :File:TutorialsForV11.8.zip|Tutorials package for V11.8
** :File:TutorialsForV11.7.1.zip|Tutorials package for V11.7.x
** :File:TutorialsForV11.6.zip|Tutorials package for V11.6
** :File:TutorialsForV11.5.zip|Tutorials package for V11.5
** :File:TutorialsForV11.4.zip|Tutorials package for V11.4
** :File:TutorialsForV11.3.zip|Tutorials package for V11.3
** :File:TutorialsForV11.2.zip|Tutorials package for V11.2
** :File:TutorialsForV11.0.zip|Tutorials package for V11.0
* Links
** https://logiciels.cnes.fr/en/home|CNES freeware server

Current version

2025-10-10T15:32:29Z

Admin :

See [http://psimu.cnes.fr/index.php/Main_differences_between_V11.7.4_and_V11.8 here].

Known bugs of this version:

Dependencies

2025-10-10T15:31:30Z

Admin :

{| class="wikitable"
|-
|Version
|style="text-align:center;"|11.8
|style="text-align:center;"|11.7.4
|style="text-align:center;"|11.7.1/11.7.2/11.7.3
|style="text-align:center;"|11.6.2
|style="text-align:center;"|11.5
|style="text-align:center;"|11.4 / 11.4.1
|style="text-align:center;"|11.3
|style="text-align:center;"|11.2 / 11.2.1
|style="text-align:center;"|11.1
|style="text-align:center;"|11.0
|-
|Disponibility
|style="text-align:center;"|from 10th Oct 2025
|style="text-align:center;"|from 6th Dec 2023
|style="text-align:center;"|from 8th Jun 2023
|style="text-align:center;"|from 7th Mar 2022
|style="text-align:center;"|from 18th Feb 2021
|style="text-align:center;"|from 8th Nov 2019
|style="text-align:center;"|from 14th Dec 2018
|style="text-align:center;"|from 14th Nov 2017
|style="text-align:center;"| -
|style="text-align:center;"| -
|-
|Javadoc
|style="text-align:center;"|yes
|style="text-align:center;"|yes
|style="text-align:center;"|yes
|style="text-align:center;"|yes
|style="text-align:center;"|yes
|style="text-align:center;"|yes
|style="text-align:center;"|yes
|style="text-align:center;"|yes
|style="text-align:center;"|yes
|- style="vertical-align:top;"
|Dependencies
|style="text-align:center;"|Java 1.8 Patrius 4.14.1 (not compatible with other versions) PatriusDataset 1.4.3 Genopus 2.5.3 Genius 1.13.3 Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.5.0 commons-io 2.4 sqlite-jdbc 3.15.1 exp4j 0.4.8
|style="text-align:center;"|Java 1.8 Patrius 4.10.2 (not compatible with other versions) PatriusDataset 1.4.3 Genopus 2.4.2 Genius 1.12.1 Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4 sqlite-jdbc 3.15.1 exp4j 0.4.8
|style="text-align:center;"|Java 1.8 Patrius 4.10.2 (not compatible with other versions) PatriusDataset 1.4.3 Genopus 2.4.1 Genius 1.12.1 Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4 sqlite-jdbc 3.15.1 exp4j 0.4.8
|style="text-align:center;"|Java 1.8 Patrius 4.8 (not compatible with other versions) PatriusDataset 1.1.0 Genopus 2.3.3 Genius 1.11.4 Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4 sqlite-jdbc 3.15.1 exp4j 0.4.8
|style="text-align:center;"|Java 1.8 Patrius 4.6 (not compatible with other versions) PatriusDataset 1.1.0 Genopus 2.2 Genius 1.10.1 Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4 sqlite-jdbc 3.15.1
|style="text-align:center;"|Java 1.8 Patrius 4.4 (not compatible with other versions) PatriusDataset 1.1.0 Genopus 2.1.1 Genius 1.9.1 Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4 sqlite-jdbc 3.15.1
|style="text-align:center;"|Java 1.7 Patrius 4.1.1 (not compatible with other versions) PatriusDataset 1.1.0 Genopus 2.0.1 Genius 1.8 Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4 sqlite-jdbc 3.15.1
|style="text-align:center;"|Java 1.7 Patrius 3.3 (not compatible with other versions) PatriusDataset 1.0.3 Genopus 1.3.1 Genius 1.7 Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4 sqlite-jdbc 3.15.1
|style="text-align:center;"|Java 1.7 Patrius 3.3 (not compatible with other versions) PatriusDataset 1.0.2 Genopus 1.3 Genius 1.7 Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4 sqlite-jdbc 3.15.1
|style="text-align:center;"|Java 1.7 Patrius 3.2 (not compatible with other versions) PatriusDataset 1.0.2 Genopus 1.2.1 Genius 1.6.x Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4
|}

News

2025-10-10T15:29:35Z

Admin :

__NOTOC__
=== 10th October 2025 ===
* New V11.7.4 version

=== 6th December 2023 ===
* New V11.7.4 version

=== 16th November 2023 ===
* New V11.7.3 version

=== 10th October 2023 ===
* An anomaly has been found : see [[Main_differences_between_V11.7.2_and_V11.7.3|here]]

=== 5th July 2023 ===
* Wiki update thanks to the new V11.7.2 version.

=== 8th June 2023 ===
* Wiki update thanks to the new V11.7.1 version.

=== 8th March 2022 ===
* Wiki update thanks to the new V11.6.2 version.

=== 18th February 2021 ===

* New V11.5 version.

=== 16th December 2020 ===

* Some information about [https://logiciels.cnes.fr/en/content/patriusdataset Patrius Dataset] initialization (see [[Basic Principle|here]]).
* Precision about units in output files versus Java code output (see [[Propagation#Master mode|here]]).

=== 25th August 2020 ===

* When reading the initial orbit, '''PSIMU''' has not already read [[Earth_Features|Earth Features characteristics]]. So, in some cases, it may exit in an error mode (for example when using H0-n frames) saying that no EOP are available even if we do not need them as it will use the [[http://patrius.cnes.fr PATRIUS]] by default configuration.

=== 13rd May 2020 ===

* When using the Java API, due to a [http://patrius.cnes.fr PATRIUS] anomaly, if the user needs to define solar panels characteristics, it is mandatory to use the Vehicle constructor with all parameters and the VehiculeSurfaceModel including the panels as above (and not a list of Facet); also, do not use the setters methods.

=== 14th February 2020 ===

* New V11.4.1 version.

=== 28th January 2020 ===

* Identification of a bug when maneuvers are too near from the initial date.

=== 21st Jan 2020 ===
* Update of the the Wiki main page.

=== 13th January 2020 ===

* Identification of a bug with the header of ephemeris/events files for date variables.

=== 27th November 2019 ===

* Identification of a bug using the [[Output#Custom_plots|Custom plots]] tab.

=== 8th November 2019 ===

* Update thanks to the V11.4 version.

=== 23th September 2019 ===

* Information on the next V11.4 version.

=== 11th Sep 2019 ===
New predicted solar activity files are available [[:File:actsol.zip|here]].

=== 6th Sep 2019 ===

Provision of the XML structure corresponding to aerodynamic coefficients depending on altitude as used in the [https://logiciels.cnes.fr/en/content/stela STELA S/W]: [[:File:Stela_drag_coefficient.zip]]

=== 26th Aug 2019 ===

* New [[:File:gplot-1.9.zip|GPLOT utility]] availability thanks to [http://genius.cnes.fr GENIUS V1.9] version.

=== 29th May 2019 ===

* Three other "minor" bugs have been identified (see [[WELCOME_TO_THE_PSIMU_WIKI#CURRENT VERSION_:_V11.3|here]]).

=== 21st Jan 2019 ===

* Two "minor" bugs have been identified : cases of hyperbolic trajectories or zero propagation duration (see [[WELCOME_TO_THE_PSIMU_WIKI#CURRENT VERSION_:_V11.3|here]]).

=== 11th Jan 2019 ===

* An additional explanation about the Copy/Paste facility on orbit data (see [[Initial_Orbit#Copy/Paste|here]]).

=== 21st Dec 2018 ===

* Adding the possibility to download a utility to plot previously saved results (see [[Output#Plots#Custom_plots|here]]).

=== 20th Dec 2018 ===

* Explaining how to extract solar activity files (see [[Forces#Atmosphere|here]]).

=== 14th Dec 2018 ===

* Update due to the V11.3 version.

=== 1st Aug 2018 ===

* Explaining how to put additional data for Earth features (see [[Earth_Features#How_to_update_data|here]]).

WELCOME TO THE PSIMU WIKI

2025-10-10T15:29:03Z

Admin : /* DESCRIPTION */

__NOTOC__
Welcome to the '''PSIMU''' wiki, a [https://cnes.fr/fr '''CNES'''] flight dynamics tool. As it is coded in Java, this product is available for any kind of platforms owning a JVM.

== DESCRIPTION ==

[[What_is_Psimu|'''What is PSIMU?''']]

::'''PSIMU''' is a [https://cnes.fr/fr '''CNES'''] tool allowing to propagate trajectories around the Earth.

[[Current_version|'''Current version''']]

::The current version is: '''V11.8'''.

[[Previous_versions|'''Previous versions''']]

::Describes evolutions thanks to previous versions.

== USE IT ==

[[Where_to_get_it|'''Where to get it?''']]

::Where to download it.

[[Quick start|'''Quick start''']]

::First steps with '''PSIMU'''

[[User_Manual|'''User Manual''']]

::'''PSIMU''' may be used very quickly via its '''GUI''' facilitating context elaboration and results exploitation. No code knowledge is necessary.
::Anyway, it is also possible to use it in '''batch''' mode (especially on grid computers with no display properties) or using its '''Java''' interface.

== DOCUMENTATION ==

[[Java_Doc|'''Java Doc''']]

::Access to current and old Java doc.

[[Dependencies|'''Dependencies''']]

::Describes dependencies with other products.

[[News|'''News''']]

::Main evolutions of the tool or its Wiki.

Main differences between V11.7.4 and V11.8

2025-10-10T15:18:27Z

Admin : /* Date entry */

== 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 a different "Look And Feel" amongst this list:

* MetalLookAndFeel (by default)
* NimbusLookAndFeel
* MotifLookAndFeel
* WindowsLookAndFeel
* WindowsClassicLookAndFeel
* FlatLightLaf
* FlatDarkLaf
* FlatIntelliJLaf
* FlatDarculaLaf

== Date entry ==
Thanks to a new [https://www.connectbycnes.fr/en/genopus GENOPUS] version, a date entry is really easier to do !

== 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.
* Some corrections thanks to new version of [https://www.connectbycnes.fr/en/genopus GENOPUS].

Main differences between V11.7.4 and V11.8

2025-10-10T15:17:07Z

Admin : /* Date entry */

== 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 a different "Look And Feel" amongst this list:

* MetalLookAndFeel (by default)
* NimbusLookAndFeel
* MotifLookAndFeel
* WindowsLookAndFeel
* WindowsClassicLookAndFeel
* FlatLightLaf
* FlatDarkLaf
* FlatIntelliJLaf
* FlatDarculaLaf

== Date entry ==
Thanks to a new [https://www.connectbycnes.fr/en/genopus GENOPUS] version, it is really easier to change a date !

== 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.
* Some corrections thanks to new version of [https://www.connectbycnes.fr/en/genopus GENOPUS].

Main differences between V11.7.4 and V11.8

2025-10-10T15:16:50Z

Admin : /* Date entry */

== 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 a different "Look And Feel" amongst this list:

* MetalLookAndFeel (by default)
* NimbusLookAndFeel
* MotifLookAndFeel
* WindowsLookAndFeel
* WindowsClassicLookAndFeel
* FlatLightLaf
* FlatDarkLaf
* FlatIntelliJLaf
* FlatDarculaLaf

== Date entry ==
Thanks to annew [https://www.connectbycnes.fr/en/genopus GENOPUS] version, it is really easier to change a date !

== 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.
* Some corrections thanks to new version of [https://www.connectbycnes.fr/en/genopus GENOPUS].

Main differences between V11.7.4 and V11.8

2025-10-10T15:16:38Z

Admin :

== 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 a different "Look And Feel" amongst this list:

* MetalLookAndFeel (by default)
* NimbusLookAndFeel
* MotifLookAndFeel
* WindowsLookAndFeel
* WindowsClassicLookAndFeel
* FlatLightLaf
* FlatDarkLaf
* FlatIntelliJLaf
* FlatDarculaLaf

== Date entry ==
Thnaks to annew [https://www.connectbycnes.fr/en/genopus GENOPUS] version, it is really easier to change a date !

== 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.
* Some corrections thanks to new version of [https://www.connectbycnes.fr/en/genopus GENOPUS].

Data initialization

2025-10-10T11:59:28Z

Admin : /* Solar radiative pressure */

The main modifications between V11.3 and previous versions are due to the use of original [http://patrius.cnes.fr PATRIUS] classes rather than to use "Custom" classes originally proposed by [http://genopus.cnes.fr GENOPUS]. Anyway, some "Custom" classes still remain as [http://patrius.cnes.fr PATRIUS] classes are not sufficiently consistent.

== Orbit ==

To initialize an orbit, we simply have to build it using [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] object. For example:

<syntaxhighlight lang="java">
final TimeScale TUC = TimeScalesFactory.getUTC();
final AbsoluteDate date = new AbsoluteDate("2010-01-01T12:00:00.000", TUC);
final double sma = Constants.WGS84_EARTH_EQUATORIAL_RADIUS + 250.e3;
final double ecc = 0.;
final double inc = FastMath.toRadians(51.6);
final double raan = FastMath.toRadians(0.);
final double pa = FastMath.toRadians(0.);
final double ano = FastMath.toRadians(0.);
final Frame GCRF = FramesFactory.getGCRF();
final KeplerianOrbit iniOrbit =
new KeplerianOrbit(sma, ecc, inc, raan, pa, ano, PositionAngle.MEAN, GCRF, date, MU);
</syntaxhighlight>

== Earth features ==

Data equivalent to the “[[Earth_Features|Earth features]]” tab are distributed via two arguments:

:1. A ExtendedOneAxisEllipsoid object which will define the shape of the planet
<syntaxhighlight lang="java">
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, FramesFactory.getITRF(), "EARTH");
</syntaxhighlight>
:2. A type of enumerates that will propose some pre-defined configurations as:
:* '''NOTHING''' (all options set to null)
:* '''ONLY_PREC_NUT''' (only precession and nutation)
:* '''FACTORY''' (equivalent to the most complete definition as in the GUI)
:* '''IGNORE''' (nothing is define internally by '''PSIMU''' which will take into account the user parametrization previously done)

== Vehicle ==

Since V11.3, it is no more necessary to pass an Assembly object but a Vehicle one. Anyway, it is allways mandatory to pass a MassProvider object, issued from the Vehicle one. It could seem curious but it is due to the fact that, if we have maneuvers, it will be mandatory to initialize them with the same MassProvider (see example [[#Maneuvers|here]]).

In fact, we need to pass both an Assembly and a MassProvider. It could seem curious but it is due to the fact that, if we have maneuvers, it will be mandatory to initialize them with the same MassProvider (see example [[#Maneuvers|here]]). To get them, we will use the createAssembly() method given by Vehicle class.

<syntaxhighlight lang="java">
final Assembly assembly = vehicle.createAssembly(GCRF);
final MassProvider mm = new MassModel(assembly);
</syntaxhighlight>

'''''Note : for CPU time purpose it is recommanded that the frame (GCRF in the previous example), mandatory in the construction of the vehicle, must be exactly the same that the one used for the propagation.'''''

In the example below, we will then use the Vehicle class initializing mass and aerodynamic properties (here no engines and no tanks):

<syntaxhighlight lang="java">
// Dry mass
final double dryMass = 1000.;
final MassProperty dryMassProperty = new MassProperty(dryMass);

// Shape
final double sref = 5.0;
Sphere sphere = new Sphere(sref);
final RightParallelepiped solarPanels = new RightParallelepiped(10., 0., 0.);
VehicleSurfaceModel vehicleRefSurface = new VehicleSurfaceModel(sphere, solarPanels);

// Aerodynamic properties
final double cd = 2.0;
final double cl = 0.;
final AerodynamicProperties aerodynamicProperties = new AerodynamicProperties(vehicleRefSurface, cd, cl);

final Vehicle vehicle = new Vehicle(vehicleRefSurface, null, dryMassProperty, aerodynamicProperties, null, null, null);

final Assembly assembly = vehicle.createAssembly(GCRF);
final MassProvider mm = new MassModel(assembly);
</syntaxhighlight>

'''''Note : due to a PATRIUS anomaly, if the user needs to define solar panels characteristics, it is mandatory to use the Vehicle constructor with all parameters and the VehiculeSurfaceModel including the panels as above (and not a list of Facet); also, do not use the setters methods.'''''

== Forces ==

Since V11.3, to define, which forces will be applied along the trajectory, we use the [http://patrius.cnes.fr PATRIUS] ForceModelsData class (no more necessary to use the specific CustomForceModels class which does not exist anymore).

=== Potential ===
In the following example, we will initialize the potential model ('''mandatory''').

<syntaxhighlight lang="java">
// Potential
final ForceModel potential = new DirectBodyAttraction(EarthGravitationalModelFactory.getBalmino(GravityFieldNames.GRGS, "grim4s4_gr", 0, 0, true));

final ForceModelsData forces = new ForceModelsData(potential, null, null, null, null, null, null, null, null, null, null, null, null, null, null);
</syntaxhighlight>

=== Aerodynamic ===

Then we could add an aerodynamic force model. Since V11.3, it is no more necessary to use "Custom" classes.

<syntaxhighlight lang="java">
final double REQ = Constants.WGS84_EARTH_EQUATORIAL_RADIUS;
final double FLAT = Constants.WGS84_EARTH_FLATTENING;
final Frame ITRF = FramesFactory.getITRF();
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, (CelestialBodyFrame)ITRF, "EARTH");

final Atmosphere atmosphere = new US76(EARTH);
final DragForce dragForce = new DragForce(1., atmosphere, assembly);

forces.setDragForce(dragForce);
</syntaxhighlight>

=== Solar radiative pressure ===

Here are explained how to use both radiative pressure and rediffused radiative pressure force models. Again, since V11.3, no more tu use old "Custom" classes.

<syntaxhighlight lang="java">
final CelestialBody sunBody = new MeeusSun();
final double dRef = 1.4959787E11;
final double pRef = 4.5605E-6;
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, (CelestialBodyFrame)ITRF, "EARTH");

SolarRadiationPressureEllipsoid radPres = new SolarRadiationPressureEllipsoid(dRef, pRef, sunBody, sunBody.getShape().getEncompassingSphereRadius(), EARTH, assembly, 1.);

forces.setSolarRadiationPressure(radPres);

// By default values used when GUI mode ...
final int inCorona = 1;
final int inMeridian = 10;
final IEmissivityModel inEmissivityModel = new KnockeRiesModel();
// Value accessible via GUI mode
final boolean inAlbedo = false;
final boolean inIr = false;
final double coefAlbedo = 1.;
final double coefIr = 1.;

RediffusedRadiativeModel rdm = new RediffusedRadiativeModel(inAlbedo, inIr, coefAlbedo, coefIr, assembly);
RediffusedRadiationPressure reDiff = new RediffusedRadiationPressure(sunBody, (CelestialBodyFrame)GCRF, inCorona, inMeridian, inEmissivityModel, rdm);

forces.setRediffusedRadiationPressure(reDiff);
</syntaxhighlight>

=== Specific forces ===

It is also possible to add specific forces via the addForceModel() method as below:

<syntaxhighlight lang="java">
final Psimu test = new Psimu(...);
test.addForceModel(myForce);
</syntaxhighlight>

== Maneuvers ==

If the user wants to add some maneuvers, it will have to do it using the [[https://logiciels.cnes.fr/en/node/78?type=desc GENOPUS]] Custom ManeuverSequence class. Indeed, this class is derivated from the PATRIUS ManeuverSequence but allows taking into account Engines and Tanks notion. From [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] V3.4, it will be possible to directly use [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] class.

=== Propulsive properties ===

First, the user will have to define propulsive properties with engine(s) and tank(s).

<syntaxhighlight lang="java">
// Propulsive properties
final PropulsiveProperty engine = new PropulsiveProperty(400, 320.);
engine.setPartName("ENGINE");
final ArrayList<PropulsiveProperty> listOfEngines = new ArrayList<PropulsiveProperty>();
listOfEngines.add(engine);
final TankProperty tank = new TankProperty(200.);
tank.setPartName("TANK");
final ArrayList<TankProperty> listOfTanks = new ArrayList<TankProperty>();
listOfTanks.add(tank);
listOfTanks.add(tank);

final Vehicle vehicle = new Vehicle(vehicleRefSurface, null, dryMassProperty, null, null, listOfEngines, listOfTanks);
</syntaxhighlight>

=== Sequence ===

Then, a maneuver sequence will be created thanks to the CustomManeuverSequence (the [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] ManeuverSequence is not directly used as it does not still manage events.

=== Impulsive maneuver ===

Here we have an example of a 10m/s impulse maneuver in TNW occuring for an AOL of 180 degrees:

<syntaxhighlight lang="java">
final double aol = FastMath.toRadians(180.);
final CustomAOLDetector aolDetector = new CustomAOLDetector(aol, PositionAngle.TRUE, GCRF, MAXCHECK, THRESHOLD, Action.STOP);
final IntervalOccurrenceDetectorWrapper impEvent = new IntervalOccurrenceDetectorWrapper(aolDetector, 1, 1, 1, Action.STOP);
final Vector3D deltaV = new Vector3D(10., 0., 0.);
final CustomImpulseManeuver imp = new CustomImpulseManeuver("Impulse maneuver", listOfEngines.get(0), listOfTanks.get(0), LOFType.TNW, impEvent, deltaV, mm);
</syntaxhighlight>

''
'''Note: it is mandatory to configure the event with a STOP action (needed by [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]]).'''
''

At last, the user will create the maneuver sequence to pass to '''PSIMU''':

<syntaxhighlight lang="java">
final CustomManeuverSequence manSeq = new CustomManeuverSequence(0., 0.);
manSeq.addManeuver(imp);
</syntaxhighlight>

=== Constant thrust maneuver ===

The next source code shows how to define a constant thrust maneuver …

<syntaxhighlight lang="java">
final double start = iniOrbit.getKeplerianPeriod();
final AbsoluteDate startDate = date.shiftedBy(start);
final CustomDateDetector startEvent = new CustomDateDetector(startDate, MAXCHECK, THRESHOLD, Action.STOP);
final double dur = 1000.;
final AbsoluteDate endDate = startDate.shiftedBy(dur);
final CustomDateDetector stopEvent = new CustomDateDetector(endDate, MAXCHECK, THRESHOLD, Action.STOP);
final Vector3D direction = new Vector3D(-1., 0., 0.);
CustomConstantManeuver cont =
new CustomConstantManeuver("Continuous maneuver", listOfEngines.get(0), listOfTanks.get(0), LOFType.TNW, startEvent, stopEvent, direction, mm);
</syntaxhighlight>

== Attitude ==

It is mandatory to get at least one attitude law. With the V11.0, it is not possible to have only one law and it is mandatory to use the “switch” possibility by using the [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] AttitudesSequence class.

This example shows how to define a single law (available since V11.1):

<syntaxhighlight lang="java">
final AttitudeLaw attitudeLaw = new LofOffset(LOFType.TNW);
</syntaxhighlight>

This other example uses a switching possibility:

<syntaxhighlight lang="java">
final AttitudeLaw law = new LofOffset(LOFType.TNW, RotationOrder.ZYX, 0., 0., 0.);
final double maxCheck = AbstractDetector.DEFAULT_MAXCHECK;
final double threshold = AbstractDetector.DEFAULT_THRESHOLD;
final EventDetector event =
new DateDetector(date, maxCheck, threshold, Action.RESET_STATE);
final AttitudesSequence seqAtt = new AttitudesSequence();
seqAtt.addSwitchingCondition(law, event, true, false, law);
</syntaxhighlight>

'''''Note : be very careful not to use by default constructors for event detectors as they introduce a STOP event, so your propagation will stop anyway !'''''

== Integration ==

Then integration data have to be defined. Here an example with RK4 integrator …

<syntaxhighlight lang="java">
final double duration = 86400.;
final double hStop = 120.e+3;
final PsimuPropagationData propagationData = new PsimuPropagationData(duration, GCRF, hStop);
final double step = 5.;
final RK4data integrationData = new RK4data(propagationData, step);
</syntaxhighlight>

… or with the DOP integrator …

<syntaxhighlight lang="java">
final double minStep = 0.1;
final double maxStep = 30.;
final double[] vecAbsoluteTolerance =
{ 1.0E-5, 1.0E-5, 1.0E-5, 1.0E-8, 1.0E-8, 1.0E-8 };
final double[] vecRelativeTolerance =
{ 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8 };
final double absMassTolerance = 1.0E-3;
final double relMassTolerance = 1.0E-2;
final double positionError = 0.;
final DopData intData = new DopData(propagationData, minStep, maxStep, vecAbsoluteTolerance, vecRelativeTolerance, absMassTolerance, relMassTolerance);
</syntaxhighlight>

== PSIMU object ==

As we have all mandatory data to initialize PSIMU, we can build such an object (note that in this example there is a “null” argument for the sequence of maneuvers.

<syntaxhighlight lang="java">
final Psimu test = new Psimu(iniOrbit, EARTH, UserFramesConfsEnum.IGNORE, integrationData, vehicle, mm, forces, manSeq, attitudeLaw);
</syntaxhighlight>

Data initialization

2025-10-10T11:58:02Z

Admin : /* Solar radiative pressure */

The main modifications between V11.3 and previous versions are due to the use of original [http://patrius.cnes.fr PATRIUS] classes rather than to use "Custom" classes originally proposed by [http://genopus.cnes.fr GENOPUS]. Anyway, some "Custom" classes still remain as [http://patrius.cnes.fr PATRIUS] classes are not sufficiently consistent.

== Orbit ==

To initialize an orbit, we simply have to build it using [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] object. For example:

<syntaxhighlight lang="java">
final TimeScale TUC = TimeScalesFactory.getUTC();
final AbsoluteDate date = new AbsoluteDate("2010-01-01T12:00:00.000", TUC);
final double sma = Constants.WGS84_EARTH_EQUATORIAL_RADIUS + 250.e3;
final double ecc = 0.;
final double inc = FastMath.toRadians(51.6);
final double raan = FastMath.toRadians(0.);
final double pa = FastMath.toRadians(0.);
final double ano = FastMath.toRadians(0.);
final Frame GCRF = FramesFactory.getGCRF();
final KeplerianOrbit iniOrbit =
new KeplerianOrbit(sma, ecc, inc, raan, pa, ano, PositionAngle.MEAN, GCRF, date, MU);
</syntaxhighlight>

== Earth features ==

Data equivalent to the “[[Earth_Features|Earth features]]” tab are distributed via two arguments:

:1. A ExtendedOneAxisEllipsoid object which will define the shape of the planet
<syntaxhighlight lang="java">
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, FramesFactory.getITRF(), "EARTH");
</syntaxhighlight>
:2. A type of enumerates that will propose some pre-defined configurations as:
:* '''NOTHING''' (all options set to null)
:* '''ONLY_PREC_NUT''' (only precession and nutation)
:* '''FACTORY''' (equivalent to the most complete definition as in the GUI)
:* '''IGNORE''' (nothing is define internally by '''PSIMU''' which will take into account the user parametrization previously done)

== Vehicle ==

Since V11.3, it is no more necessary to pass an Assembly object but a Vehicle one. Anyway, it is allways mandatory to pass a MassProvider object, issued from the Vehicle one. It could seem curious but it is due to the fact that, if we have maneuvers, it will be mandatory to initialize them with the same MassProvider (see example [[#Maneuvers|here]]).

In fact, we need to pass both an Assembly and a MassProvider. It could seem curious but it is due to the fact that, if we have maneuvers, it will be mandatory to initialize them with the same MassProvider (see example [[#Maneuvers|here]]). To get them, we will use the createAssembly() method given by Vehicle class.

<syntaxhighlight lang="java">
final Assembly assembly = vehicle.createAssembly(GCRF);
final MassProvider mm = new MassModel(assembly);
</syntaxhighlight>

'''''Note : for CPU time purpose it is recommanded that the frame (GCRF in the previous example), mandatory in the construction of the vehicle, must be exactly the same that the one used for the propagation.'''''

In the example below, we will then use the Vehicle class initializing mass and aerodynamic properties (here no engines and no tanks):

<syntaxhighlight lang="java">
// Dry mass
final double dryMass = 1000.;
final MassProperty dryMassProperty = new MassProperty(dryMass);

// Shape
final double sref = 5.0;
Sphere sphere = new Sphere(sref);
final RightParallelepiped solarPanels = new RightParallelepiped(10., 0., 0.);
VehicleSurfaceModel vehicleRefSurface = new VehicleSurfaceModel(sphere, solarPanels);

// Aerodynamic properties
final double cd = 2.0;
final double cl = 0.;
final AerodynamicProperties aerodynamicProperties = new AerodynamicProperties(vehicleRefSurface, cd, cl);

final Vehicle vehicle = new Vehicle(vehicleRefSurface, null, dryMassProperty, aerodynamicProperties, null, null, null);

final Assembly assembly = vehicle.createAssembly(GCRF);
final MassProvider mm = new MassModel(assembly);
</syntaxhighlight>

'''''Note : due to a PATRIUS anomaly, if the user needs to define solar panels characteristics, it is mandatory to use the Vehicle constructor with all parameters and the VehiculeSurfaceModel including the panels as above (and not a list of Facet); also, do not use the setters methods.'''''

== Forces ==

Since V11.3, to define, which forces will be applied along the trajectory, we use the [http://patrius.cnes.fr PATRIUS] ForceModelsData class (no more necessary to use the specific CustomForceModels class which does not exist anymore).

=== Potential ===
In the following example, we will initialize the potential model ('''mandatory''').

<syntaxhighlight lang="java">
// Potential
final ForceModel potential = new DirectBodyAttraction(EarthGravitationalModelFactory.getBalmino(GravityFieldNames.GRGS, "grim4s4_gr", 0, 0, true));

final ForceModelsData forces = new ForceModelsData(potential, null, null, null, null, null, null, null, null, null, null, null, null, null, null);
</syntaxhighlight>

=== Aerodynamic ===

Then we could add an aerodynamic force model. Since V11.3, it is no more necessary to use "Custom" classes.

<syntaxhighlight lang="java">
final double REQ = Constants.WGS84_EARTH_EQUATORIAL_RADIUS;
final double FLAT = Constants.WGS84_EARTH_FLATTENING;
final Frame ITRF = FramesFactory.getITRF();
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, (CelestialBodyFrame)ITRF, "EARTH");

final Atmosphere atmosphere = new US76(EARTH);
final DragForce dragForce = new DragForce(1., atmosphere, assembly);

forces.setDragForce(dragForce);
</syntaxhighlight>

=== Solar radiative pressure ===

Here are explained how to use both radiative pressure and rediffused radiative pressure force models. Again, since V11.3, no more tu use old "Custom" classes.

<syntaxhighlight lang="java">
final CelestialBody sunBody = new MeeusSun();
final double dRef = 1.4959787E11;
final double pRef = 4.5605E-6;
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, (CelestialBodyFrame)ITRF, "EARTH");

SolarRadiationPressureEllipsoid radPres = new SolarRadiationPressureEllipsoid(dRef, pRef, sunBody, EARTH, assembly, 1.);

forces.setSolarRadiationPressure(radPres);

// By default values used when GUI mode ...
final int inCorona = 1;
final int inMeridian = 10;
final IEmissivityModel inEmissivityModel = new KnockeRiesModel();
// Value accessible via GUI mode
final boolean inAlbedo = false;
final boolean inIr = false;
final double coefAlbedo = 1.;
final double coefIr = 1.;

RediffusedRadiativeModel rdm = new RediffusedRadiativeModel(inAlbedo, inIr, coefAlbedo, coefIr, assembly);
RediffusedRadiationPressure reDiff = new RediffusedRadiationPressure(sunBody, GCRF, inCorona, inMeridian, inEmissivityModel, rdm);

forces.setRediffusedRadiationPressure(reDiff);
</syntaxhighlight>

=== Specific forces ===

It is also possible to add specific forces via the addForceModel() method as below:

<syntaxhighlight lang="java">
final Psimu test = new Psimu(...);
test.addForceModel(myForce);
</syntaxhighlight>

== Maneuvers ==

If the user wants to add some maneuvers, it will have to do it using the [[https://logiciels.cnes.fr/en/node/78?type=desc GENOPUS]] Custom ManeuverSequence class. Indeed, this class is derivated from the PATRIUS ManeuverSequence but allows taking into account Engines and Tanks notion. From [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] V3.4, it will be possible to directly use [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] class.

=== Propulsive properties ===

First, the user will have to define propulsive properties with engine(s) and tank(s).

<syntaxhighlight lang="java">
// Propulsive properties
final PropulsiveProperty engine = new PropulsiveProperty(400, 320.);
engine.setPartName("ENGINE");
final ArrayList<PropulsiveProperty> listOfEngines = new ArrayList<PropulsiveProperty>();
listOfEngines.add(engine);
final TankProperty tank = new TankProperty(200.);
tank.setPartName("TANK");
final ArrayList<TankProperty> listOfTanks = new ArrayList<TankProperty>();
listOfTanks.add(tank);
listOfTanks.add(tank);

final Vehicle vehicle = new Vehicle(vehicleRefSurface, null, dryMassProperty, null, null, listOfEngines, listOfTanks);
</syntaxhighlight>

=== Sequence ===

Then, a maneuver sequence will be created thanks to the CustomManeuverSequence (the [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] ManeuverSequence is not directly used as it does not still manage events.

=== Impulsive maneuver ===

Here we have an example of a 10m/s impulse maneuver in TNW occuring for an AOL of 180 degrees:

<syntaxhighlight lang="java">
final double aol = FastMath.toRadians(180.);
final CustomAOLDetector aolDetector = new CustomAOLDetector(aol, PositionAngle.TRUE, GCRF, MAXCHECK, THRESHOLD, Action.STOP);
final IntervalOccurrenceDetectorWrapper impEvent = new IntervalOccurrenceDetectorWrapper(aolDetector, 1, 1, 1, Action.STOP);
final Vector3D deltaV = new Vector3D(10., 0., 0.);
final CustomImpulseManeuver imp = new CustomImpulseManeuver("Impulse maneuver", listOfEngines.get(0), listOfTanks.get(0), LOFType.TNW, impEvent, deltaV, mm);
</syntaxhighlight>

''
'''Note: it is mandatory to configure the event with a STOP action (needed by [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]]).'''
''

At last, the user will create the maneuver sequence to pass to '''PSIMU''':

<syntaxhighlight lang="java">
final CustomManeuverSequence manSeq = new CustomManeuverSequence(0., 0.);
manSeq.addManeuver(imp);
</syntaxhighlight>

=== Constant thrust maneuver ===

The next source code shows how to define a constant thrust maneuver …

<syntaxhighlight lang="java">
final double start = iniOrbit.getKeplerianPeriod();
final AbsoluteDate startDate = date.shiftedBy(start);
final CustomDateDetector startEvent = new CustomDateDetector(startDate, MAXCHECK, THRESHOLD, Action.STOP);
final double dur = 1000.;
final AbsoluteDate endDate = startDate.shiftedBy(dur);
final CustomDateDetector stopEvent = new CustomDateDetector(endDate, MAXCHECK, THRESHOLD, Action.STOP);
final Vector3D direction = new Vector3D(-1., 0., 0.);
CustomConstantManeuver cont =
new CustomConstantManeuver("Continuous maneuver", listOfEngines.get(0), listOfTanks.get(0), LOFType.TNW, startEvent, stopEvent, direction, mm);
</syntaxhighlight>

== Attitude ==

It is mandatory to get at least one attitude law. With the V11.0, it is not possible to have only one law and it is mandatory to use the “switch” possibility by using the [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] AttitudesSequence class.

This example shows how to define a single law (available since V11.1):

<syntaxhighlight lang="java">
final AttitudeLaw attitudeLaw = new LofOffset(LOFType.TNW);
</syntaxhighlight>

This other example uses a switching possibility:

<syntaxhighlight lang="java">
final AttitudeLaw law = new LofOffset(LOFType.TNW, RotationOrder.ZYX, 0., 0., 0.);
final double maxCheck = AbstractDetector.DEFAULT_MAXCHECK;
final double threshold = AbstractDetector.DEFAULT_THRESHOLD;
final EventDetector event =
new DateDetector(date, maxCheck, threshold, Action.RESET_STATE);
final AttitudesSequence seqAtt = new AttitudesSequence();
seqAtt.addSwitchingCondition(law, event, true, false, law);
</syntaxhighlight>

'''''Note : be very careful not to use by default constructors for event detectors as they introduce a STOP event, so your propagation will stop anyway !'''''

== Integration ==

Then integration data have to be defined. Here an example with RK4 integrator …

<syntaxhighlight lang="java">
final double duration = 86400.;
final double hStop = 120.e+3;
final PsimuPropagationData propagationData = new PsimuPropagationData(duration, GCRF, hStop);
final double step = 5.;
final RK4data integrationData = new RK4data(propagationData, step);
</syntaxhighlight>

… or with the DOP integrator …

<syntaxhighlight lang="java">
final double minStep = 0.1;
final double maxStep = 30.;
final double[] vecAbsoluteTolerance =
{ 1.0E-5, 1.0E-5, 1.0E-5, 1.0E-8, 1.0E-8, 1.0E-8 };
final double[] vecRelativeTolerance =
{ 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8 };
final double absMassTolerance = 1.0E-3;
final double relMassTolerance = 1.0E-2;
final double positionError = 0.;
final DopData intData = new DopData(propagationData, minStep, maxStep, vecAbsoluteTolerance, vecRelativeTolerance, absMassTolerance, relMassTolerance);
</syntaxhighlight>

== PSIMU object ==

As we have all mandatory data to initialize PSIMU, we can build such an object (note that in this example there is a “null” argument for the sequence of maneuvers.

<syntaxhighlight lang="java">
final Psimu test = new Psimu(iniOrbit, EARTH, UserFramesConfsEnum.IGNORE, integrationData, vehicle, mm, forces, manSeq, attitudeLaw);
</syntaxhighlight>

Data initialization

2025-10-10T11:57:39Z

Admin : /* Aerodynamic */

The main modifications between V11.3 and previous versions are due to the use of original [http://patrius.cnes.fr PATRIUS] classes rather than to use "Custom" classes originally proposed by [http://genopus.cnes.fr GENOPUS]. Anyway, some "Custom" classes still remain as [http://patrius.cnes.fr PATRIUS] classes are not sufficiently consistent.

== Orbit ==

To initialize an orbit, we simply have to build it using [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] object. For example:

<syntaxhighlight lang="java">
final TimeScale TUC = TimeScalesFactory.getUTC();
final AbsoluteDate date = new AbsoluteDate("2010-01-01T12:00:00.000", TUC);
final double sma = Constants.WGS84_EARTH_EQUATORIAL_RADIUS + 250.e3;
final double ecc = 0.;
final double inc = FastMath.toRadians(51.6);
final double raan = FastMath.toRadians(0.);
final double pa = FastMath.toRadians(0.);
final double ano = FastMath.toRadians(0.);
final Frame GCRF = FramesFactory.getGCRF();
final KeplerianOrbit iniOrbit =
new KeplerianOrbit(sma, ecc, inc, raan, pa, ano, PositionAngle.MEAN, GCRF, date, MU);
</syntaxhighlight>

== Earth features ==

Data equivalent to the “[[Earth_Features|Earth features]]” tab are distributed via two arguments:

:1. A ExtendedOneAxisEllipsoid object which will define the shape of the planet
<syntaxhighlight lang="java">
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, FramesFactory.getITRF(), "EARTH");
</syntaxhighlight>
:2. A type of enumerates that will propose some pre-defined configurations as:
:* '''NOTHING''' (all options set to null)
:* '''ONLY_PREC_NUT''' (only precession and nutation)
:* '''FACTORY''' (equivalent to the most complete definition as in the GUI)
:* '''IGNORE''' (nothing is define internally by '''PSIMU''' which will take into account the user parametrization previously done)

== Vehicle ==

Since V11.3, it is no more necessary to pass an Assembly object but a Vehicle one. Anyway, it is allways mandatory to pass a MassProvider object, issued from the Vehicle one. It could seem curious but it is due to the fact that, if we have maneuvers, it will be mandatory to initialize them with the same MassProvider (see example [[#Maneuvers|here]]).

In fact, we need to pass both an Assembly and a MassProvider. It could seem curious but it is due to the fact that, if we have maneuvers, it will be mandatory to initialize them with the same MassProvider (see example [[#Maneuvers|here]]). To get them, we will use the createAssembly() method given by Vehicle class.

<syntaxhighlight lang="java">
final Assembly assembly = vehicle.createAssembly(GCRF);
final MassProvider mm = new MassModel(assembly);
</syntaxhighlight>

'''''Note : for CPU time purpose it is recommanded that the frame (GCRF in the previous example), mandatory in the construction of the vehicle, must be exactly the same that the one used for the propagation.'''''

In the example below, we will then use the Vehicle class initializing mass and aerodynamic properties (here no engines and no tanks):

<syntaxhighlight lang="java">
// Dry mass
final double dryMass = 1000.;
final MassProperty dryMassProperty = new MassProperty(dryMass);

// Shape
final double sref = 5.0;
Sphere sphere = new Sphere(sref);
final RightParallelepiped solarPanels = new RightParallelepiped(10., 0., 0.);
VehicleSurfaceModel vehicleRefSurface = new VehicleSurfaceModel(sphere, solarPanels);

// Aerodynamic properties
final double cd = 2.0;
final double cl = 0.;
final AerodynamicProperties aerodynamicProperties = new AerodynamicProperties(vehicleRefSurface, cd, cl);

final Vehicle vehicle = new Vehicle(vehicleRefSurface, null, dryMassProperty, aerodynamicProperties, null, null, null);

final Assembly assembly = vehicle.createAssembly(GCRF);
final MassProvider mm = new MassModel(assembly);
</syntaxhighlight>

'''''Note : due to a PATRIUS anomaly, if the user needs to define solar panels characteristics, it is mandatory to use the Vehicle constructor with all parameters and the VehiculeSurfaceModel including the panels as above (and not a list of Facet); also, do not use the setters methods.'''''

== Forces ==

Since V11.3, to define, which forces will be applied along the trajectory, we use the [http://patrius.cnes.fr PATRIUS] ForceModelsData class (no more necessary to use the specific CustomForceModels class which does not exist anymore).

=== Potential ===
In the following example, we will initialize the potential model ('''mandatory''').

<syntaxhighlight lang="java">
// Potential
final ForceModel potential = new DirectBodyAttraction(EarthGravitationalModelFactory.getBalmino(GravityFieldNames.GRGS, "grim4s4_gr", 0, 0, true));

final ForceModelsData forces = new ForceModelsData(potential, null, null, null, null, null, null, null, null, null, null, null, null, null, null);
</syntaxhighlight>

=== Aerodynamic ===

Then we could add an aerodynamic force model. Since V11.3, it is no more necessary to use "Custom" classes.

<syntaxhighlight lang="java">
final double REQ = Constants.WGS84_EARTH_EQUATORIAL_RADIUS;
final double FLAT = Constants.WGS84_EARTH_FLATTENING;
final Frame ITRF = FramesFactory.getITRF();
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, (CelestialBodyFrame)ITRF, "EARTH");

final Atmosphere atmosphere = new US76(EARTH);
final DragForce dragForce = new DragForce(1., atmosphere, assembly);

forces.setDragForce(dragForce);
</syntaxhighlight>

=== Solar radiative pressure ===

Here are explained how to use both radiative pressure and rediffused radiative pressure force models. Again, since V11.3, no more tu use old "Custom" classes.

<syntaxhighlight lang="java">
final CelestialBody sunBody = new MeeusSun();
final double dRef = 1.4959787E11;
final double pRef = 4.5605E-6;
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, ITRF, "EARTH");

SolarRadiationPressureEllipsoid radPres = new SolarRadiationPressureEllipsoid(dRef, pRef, sunBody, EARTH, assembly, 1.);

forces.setSolarRadiationPressure(radPres);

// By default values used when GUI mode ...
final int inCorona = 1;
final int inMeridian = 10;
final IEmissivityModel inEmissivityModel = new KnockeRiesModel();
// Value accessible via GUI mode
final boolean inAlbedo = false;
final boolean inIr = false;
final double coefAlbedo = 1.;
final double coefIr = 1.;

RediffusedRadiativeModel rdm = new RediffusedRadiativeModel(inAlbedo, inIr, coefAlbedo, coefIr, assembly);
RediffusedRadiationPressure reDiff = new RediffusedRadiationPressure(sunBody, GCRF, inCorona, inMeridian, inEmissivityModel, rdm);

forces.setRediffusedRadiationPressure(reDiff);
</syntaxhighlight>

=== Specific forces ===

It is also possible to add specific forces via the addForceModel() method as below:

<syntaxhighlight lang="java">
final Psimu test = new Psimu(...);
test.addForceModel(myForce);
</syntaxhighlight>

== Maneuvers ==

If the user wants to add some maneuvers, it will have to do it using the [[https://logiciels.cnes.fr/en/node/78?type=desc GENOPUS]] Custom ManeuverSequence class. Indeed, this class is derivated from the PATRIUS ManeuverSequence but allows taking into account Engines and Tanks notion. From [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] V3.4, it will be possible to directly use [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] class.

=== Propulsive properties ===

First, the user will have to define propulsive properties with engine(s) and tank(s).

<syntaxhighlight lang="java">
// Propulsive properties
final PropulsiveProperty engine = new PropulsiveProperty(400, 320.);
engine.setPartName("ENGINE");
final ArrayList<PropulsiveProperty> listOfEngines = new ArrayList<PropulsiveProperty>();
listOfEngines.add(engine);
final TankProperty tank = new TankProperty(200.);
tank.setPartName("TANK");
final ArrayList<TankProperty> listOfTanks = new ArrayList<TankProperty>();
listOfTanks.add(tank);
listOfTanks.add(tank);

final Vehicle vehicle = new Vehicle(vehicleRefSurface, null, dryMassProperty, null, null, listOfEngines, listOfTanks);
</syntaxhighlight>

=== Sequence ===

Then, a maneuver sequence will be created thanks to the CustomManeuverSequence (the [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] ManeuverSequence is not directly used as it does not still manage events.

=== Impulsive maneuver ===

Here we have an example of a 10m/s impulse maneuver in TNW occuring for an AOL of 180 degrees:

<syntaxhighlight lang="java">
final double aol = FastMath.toRadians(180.);
final CustomAOLDetector aolDetector = new CustomAOLDetector(aol, PositionAngle.TRUE, GCRF, MAXCHECK, THRESHOLD, Action.STOP);
final IntervalOccurrenceDetectorWrapper impEvent = new IntervalOccurrenceDetectorWrapper(aolDetector, 1, 1, 1, Action.STOP);
final Vector3D deltaV = new Vector3D(10., 0., 0.);
final CustomImpulseManeuver imp = new CustomImpulseManeuver("Impulse maneuver", listOfEngines.get(0), listOfTanks.get(0), LOFType.TNW, impEvent, deltaV, mm);
</syntaxhighlight>

''
'''Note: it is mandatory to configure the event with a STOP action (needed by [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]]).'''
''

At last, the user will create the maneuver sequence to pass to '''PSIMU''':

<syntaxhighlight lang="java">
final CustomManeuverSequence manSeq = new CustomManeuverSequence(0., 0.);
manSeq.addManeuver(imp);
</syntaxhighlight>

=== Constant thrust maneuver ===

The next source code shows how to define a constant thrust maneuver …

<syntaxhighlight lang="java">
final double start = iniOrbit.getKeplerianPeriod();
final AbsoluteDate startDate = date.shiftedBy(start);
final CustomDateDetector startEvent = new CustomDateDetector(startDate, MAXCHECK, THRESHOLD, Action.STOP);
final double dur = 1000.;
final AbsoluteDate endDate = startDate.shiftedBy(dur);
final CustomDateDetector stopEvent = new CustomDateDetector(endDate, MAXCHECK, THRESHOLD, Action.STOP);
final Vector3D direction = new Vector3D(-1., 0., 0.);
CustomConstantManeuver cont =
new CustomConstantManeuver("Continuous maneuver", listOfEngines.get(0), listOfTanks.get(0), LOFType.TNW, startEvent, stopEvent, direction, mm);
</syntaxhighlight>

== Attitude ==

It is mandatory to get at least one attitude law. With the V11.0, it is not possible to have only one law and it is mandatory to use the “switch” possibility by using the [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] AttitudesSequence class.

This example shows how to define a single law (available since V11.1):

<syntaxhighlight lang="java">
final AttitudeLaw attitudeLaw = new LofOffset(LOFType.TNW);
</syntaxhighlight>

This other example uses a switching possibility:

<syntaxhighlight lang="java">
final AttitudeLaw law = new LofOffset(LOFType.TNW, RotationOrder.ZYX, 0., 0., 0.);
final double maxCheck = AbstractDetector.DEFAULT_MAXCHECK;
final double threshold = AbstractDetector.DEFAULT_THRESHOLD;
final EventDetector event =
new DateDetector(date, maxCheck, threshold, Action.RESET_STATE);
final AttitudesSequence seqAtt = new AttitudesSequence();
seqAtt.addSwitchingCondition(law, event, true, false, law);
</syntaxhighlight>

'''''Note : be very careful not to use by default constructors for event detectors as they introduce a STOP event, so your propagation will stop anyway !'''''

== Integration ==

Then integration data have to be defined. Here an example with RK4 integrator …

<syntaxhighlight lang="java">
final double duration = 86400.;
final double hStop = 120.e+3;
final PsimuPropagationData propagationData = new PsimuPropagationData(duration, GCRF, hStop);
final double step = 5.;
final RK4data integrationData = new RK4data(propagationData, step);
</syntaxhighlight>

… or with the DOP integrator …

<syntaxhighlight lang="java">
final double minStep = 0.1;
final double maxStep = 30.;
final double[] vecAbsoluteTolerance =
{ 1.0E-5, 1.0E-5, 1.0E-5, 1.0E-8, 1.0E-8, 1.0E-8 };
final double[] vecRelativeTolerance =
{ 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8 };
final double absMassTolerance = 1.0E-3;
final double relMassTolerance = 1.0E-2;
final double positionError = 0.;
final DopData intData = new DopData(propagationData, minStep, maxStep, vecAbsoluteTolerance, vecRelativeTolerance, absMassTolerance, relMassTolerance);
</syntaxhighlight>

== PSIMU object ==

As we have all mandatory data to initialize PSIMU, we can build such an object (note that in this example there is a “null” argument for the sequence of maneuvers.

<syntaxhighlight lang="java">
final Psimu test = new Psimu(iniOrbit, EARTH, UserFramesConfsEnum.IGNORE, integrationData, vehicle, mm, forces, manSeq, attitudeLaw);
</syntaxhighlight>

Data initialization

2025-10-10T11:57:11Z

Admin : /* Aerodynamic */

The main modifications between V11.3 and previous versions are due to the use of original [http://patrius.cnes.fr PATRIUS] classes rather than to use "Custom" classes originally proposed by [http://genopus.cnes.fr GENOPUS]. Anyway, some "Custom" classes still remain as [http://patrius.cnes.fr PATRIUS] classes are not sufficiently consistent.

== Orbit ==

To initialize an orbit, we simply have to build it using [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] object. For example:

<syntaxhighlight lang="java">
final TimeScale TUC = TimeScalesFactory.getUTC();
final AbsoluteDate date = new AbsoluteDate("2010-01-01T12:00:00.000", TUC);
final double sma = Constants.WGS84_EARTH_EQUATORIAL_RADIUS + 250.e3;
final double ecc = 0.;
final double inc = FastMath.toRadians(51.6);
final double raan = FastMath.toRadians(0.);
final double pa = FastMath.toRadians(0.);
final double ano = FastMath.toRadians(0.);
final Frame GCRF = FramesFactory.getGCRF();
final KeplerianOrbit iniOrbit =
new KeplerianOrbit(sma, ecc, inc, raan, pa, ano, PositionAngle.MEAN, GCRF, date, MU);
</syntaxhighlight>

== Earth features ==

Data equivalent to the “[[Earth_Features|Earth features]]” tab are distributed via two arguments:

:1. A ExtendedOneAxisEllipsoid object which will define the shape of the planet
<syntaxhighlight lang="java">
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, FramesFactory.getITRF(), "EARTH");
</syntaxhighlight>
:2. A type of enumerates that will propose some pre-defined configurations as:
:* '''NOTHING''' (all options set to null)
:* '''ONLY_PREC_NUT''' (only precession and nutation)
:* '''FACTORY''' (equivalent to the most complete definition as in the GUI)
:* '''IGNORE''' (nothing is define internally by '''PSIMU''' which will take into account the user parametrization previously done)

== Vehicle ==

Since V11.3, it is no more necessary to pass an Assembly object but a Vehicle one. Anyway, it is allways mandatory to pass a MassProvider object, issued from the Vehicle one. It could seem curious but it is due to the fact that, if we have maneuvers, it will be mandatory to initialize them with the same MassProvider (see example [[#Maneuvers|here]]).

In fact, we need to pass both an Assembly and a MassProvider. It could seem curious but it is due to the fact that, if we have maneuvers, it will be mandatory to initialize them with the same MassProvider (see example [[#Maneuvers|here]]). To get them, we will use the createAssembly() method given by Vehicle class.

<syntaxhighlight lang="java">
final Assembly assembly = vehicle.createAssembly(GCRF);
final MassProvider mm = new MassModel(assembly);
</syntaxhighlight>

'''''Note : for CPU time purpose it is recommanded that the frame (GCRF in the previous example), mandatory in the construction of the vehicle, must be exactly the same that the one used for the propagation.'''''

In the example below, we will then use the Vehicle class initializing mass and aerodynamic properties (here no engines and no tanks):

<syntaxhighlight lang="java">
// Dry mass
final double dryMass = 1000.;
final MassProperty dryMassProperty = new MassProperty(dryMass);

// Shape
final double sref = 5.0;
Sphere sphere = new Sphere(sref);
final RightParallelepiped solarPanels = new RightParallelepiped(10., 0., 0.);
VehicleSurfaceModel vehicleRefSurface = new VehicleSurfaceModel(sphere, solarPanels);

// Aerodynamic properties
final double cd = 2.0;
final double cl = 0.;
final AerodynamicProperties aerodynamicProperties = new AerodynamicProperties(vehicleRefSurface, cd, cl);

final Vehicle vehicle = new Vehicle(vehicleRefSurface, null, dryMassProperty, aerodynamicProperties, null, null, null);

final Assembly assembly = vehicle.createAssembly(GCRF);
final MassProvider mm = new MassModel(assembly);
</syntaxhighlight>

'''''Note : due to a PATRIUS anomaly, if the user needs to define solar panels characteristics, it is mandatory to use the Vehicle constructor with all parameters and the VehiculeSurfaceModel including the panels as above (and not a list of Facet); also, do not use the setters methods.'''''

== Forces ==

Since V11.3, to define, which forces will be applied along the trajectory, we use the [http://patrius.cnes.fr PATRIUS] ForceModelsData class (no more necessary to use the specific CustomForceModels class which does not exist anymore).

=== Potential ===
In the following example, we will initialize the potential model ('''mandatory''').

<syntaxhighlight lang="java">
// Potential
final ForceModel potential = new DirectBodyAttraction(EarthGravitationalModelFactory.getBalmino(GravityFieldNames.GRGS, "grim4s4_gr", 0, 0, true));

final ForceModelsData forces = new ForceModelsData(potential, null, null, null, null, null, null, null, null, null, null, null, null, null, null);
</syntaxhighlight>

=== Aerodynamic ===

Then we could add an aerodynamic force model. Since V11.3, it is no more necessary to use "Custom" classes.

<syntaxhighlight lang="java">
final double REQ = Constants.WGS84_EARTH_EQUATORIAL_RADIUS;
final double FLAT = Constants.WGS84_EARTH_FLATTENING;
final Frame ITRF = FramesFactory.getITRF();
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, FramesFactory.getITRF(), "EARTH");

final Atmosphere atmosphere = new US76(EARTH);
final DragForce dragForce = new DragForce(1., atmosphere, assembly);

forces.setDragForce(dragForce);
</syntaxhighlight>

=== Solar radiative pressure ===

Here are explained how to use both radiative pressure and rediffused radiative pressure force models. Again, since V11.3, no more tu use old "Custom" classes.

<syntaxhighlight lang="java">
final CelestialBody sunBody = new MeeusSun();
final double dRef = 1.4959787E11;
final double pRef = 4.5605E-6;
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, ITRF, "EARTH");

SolarRadiationPressureEllipsoid radPres = new SolarRadiationPressureEllipsoid(dRef, pRef, sunBody, EARTH, assembly, 1.);

forces.setSolarRadiationPressure(radPres);

// By default values used when GUI mode ...
final int inCorona = 1;
final int inMeridian = 10;
final IEmissivityModel inEmissivityModel = new KnockeRiesModel();
// Value accessible via GUI mode
final boolean inAlbedo = false;
final boolean inIr = false;
final double coefAlbedo = 1.;
final double coefIr = 1.;

RediffusedRadiativeModel rdm = new RediffusedRadiativeModel(inAlbedo, inIr, coefAlbedo, coefIr, assembly);
RediffusedRadiationPressure reDiff = new RediffusedRadiationPressure(sunBody, GCRF, inCorona, inMeridian, inEmissivityModel, rdm);

forces.setRediffusedRadiationPressure(reDiff);
</syntaxhighlight>

=== Specific forces ===

It is also possible to add specific forces via the addForceModel() method as below:

<syntaxhighlight lang="java">
final Psimu test = new Psimu(...);
test.addForceModel(myForce);
</syntaxhighlight>

== Maneuvers ==

If the user wants to add some maneuvers, it will have to do it using the [[https://logiciels.cnes.fr/en/node/78?type=desc GENOPUS]] Custom ManeuverSequence class. Indeed, this class is derivated from the PATRIUS ManeuverSequence but allows taking into account Engines and Tanks notion. From [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] V3.4, it will be possible to directly use [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] class.

=== Propulsive properties ===

First, the user will have to define propulsive properties with engine(s) and tank(s).

<syntaxhighlight lang="java">
// Propulsive properties
final PropulsiveProperty engine = new PropulsiveProperty(400, 320.);
engine.setPartName("ENGINE");
final ArrayList<PropulsiveProperty> listOfEngines = new ArrayList<PropulsiveProperty>();
listOfEngines.add(engine);
final TankProperty tank = new TankProperty(200.);
tank.setPartName("TANK");
final ArrayList<TankProperty> listOfTanks = new ArrayList<TankProperty>();
listOfTanks.add(tank);
listOfTanks.add(tank);

final Vehicle vehicle = new Vehicle(vehicleRefSurface, null, dryMassProperty, null, null, listOfEngines, listOfTanks);
</syntaxhighlight>

=== Sequence ===

Then, a maneuver sequence will be created thanks to the CustomManeuverSequence (the [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] ManeuverSequence is not directly used as it does not still manage events.

=== Impulsive maneuver ===

Here we have an example of a 10m/s impulse maneuver in TNW occuring for an AOL of 180 degrees:

<syntaxhighlight lang="java">
final double aol = FastMath.toRadians(180.);
final CustomAOLDetector aolDetector = new CustomAOLDetector(aol, PositionAngle.TRUE, GCRF, MAXCHECK, THRESHOLD, Action.STOP);
final IntervalOccurrenceDetectorWrapper impEvent = new IntervalOccurrenceDetectorWrapper(aolDetector, 1, 1, 1, Action.STOP);
final Vector3D deltaV = new Vector3D(10., 0., 0.);
final CustomImpulseManeuver imp = new CustomImpulseManeuver("Impulse maneuver", listOfEngines.get(0), listOfTanks.get(0), LOFType.TNW, impEvent, deltaV, mm);
</syntaxhighlight>

''
'''Note: it is mandatory to configure the event with a STOP action (needed by [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]]).'''
''

At last, the user will create the maneuver sequence to pass to '''PSIMU''':

<syntaxhighlight lang="java">
final CustomManeuverSequence manSeq = new CustomManeuverSequence(0., 0.);
manSeq.addManeuver(imp);
</syntaxhighlight>

=== Constant thrust maneuver ===

The next source code shows how to define a constant thrust maneuver …

<syntaxhighlight lang="java">
final double start = iniOrbit.getKeplerianPeriod();
final AbsoluteDate startDate = date.shiftedBy(start);
final CustomDateDetector startEvent = new CustomDateDetector(startDate, MAXCHECK, THRESHOLD, Action.STOP);
final double dur = 1000.;
final AbsoluteDate endDate = startDate.shiftedBy(dur);
final CustomDateDetector stopEvent = new CustomDateDetector(endDate, MAXCHECK, THRESHOLD, Action.STOP);
final Vector3D direction = new Vector3D(-1., 0., 0.);
CustomConstantManeuver cont =
new CustomConstantManeuver("Continuous maneuver", listOfEngines.get(0), listOfTanks.get(0), LOFType.TNW, startEvent, stopEvent, direction, mm);
</syntaxhighlight>

== Attitude ==

It is mandatory to get at least one attitude law. With the V11.0, it is not possible to have only one law and it is mandatory to use the “switch” possibility by using the [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] AttitudesSequence class.

This example shows how to define a single law (available since V11.1):

<syntaxhighlight lang="java">
final AttitudeLaw attitudeLaw = new LofOffset(LOFType.TNW);
</syntaxhighlight>

This other example uses a switching possibility:

<syntaxhighlight lang="java">
final AttitudeLaw law = new LofOffset(LOFType.TNW, RotationOrder.ZYX, 0., 0., 0.);
final double maxCheck = AbstractDetector.DEFAULT_MAXCHECK;
final double threshold = AbstractDetector.DEFAULT_THRESHOLD;
final EventDetector event =
new DateDetector(date, maxCheck, threshold, Action.RESET_STATE);
final AttitudesSequence seqAtt = new AttitudesSequence();
seqAtt.addSwitchingCondition(law, event, true, false, law);
</syntaxhighlight>

'''''Note : be very careful not to use by default constructors for event detectors as they introduce a STOP event, so your propagation will stop anyway !'''''

== Integration ==

Then integration data have to be defined. Here an example with RK4 integrator …

<syntaxhighlight lang="java">
final double duration = 86400.;
final double hStop = 120.e+3;
final PsimuPropagationData propagationData = new PsimuPropagationData(duration, GCRF, hStop);
final double step = 5.;
final RK4data integrationData = new RK4data(propagationData, step);
</syntaxhighlight>

… or with the DOP integrator …

<syntaxhighlight lang="java">
final double minStep = 0.1;
final double maxStep = 30.;
final double[] vecAbsoluteTolerance =
{ 1.0E-5, 1.0E-5, 1.0E-5, 1.0E-8, 1.0E-8, 1.0E-8 };
final double[] vecRelativeTolerance =
{ 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8 };
final double absMassTolerance = 1.0E-3;
final double relMassTolerance = 1.0E-2;
final double positionError = 0.;
final DopData intData = new DopData(propagationData, minStep, maxStep, vecAbsoluteTolerance, vecRelativeTolerance, absMassTolerance, relMassTolerance);
</syntaxhighlight>

== PSIMU object ==

As we have all mandatory data to initialize PSIMU, we can build such an object (note that in this example there is a “null” argument for the sequence of maneuvers.

<syntaxhighlight lang="java">
final Psimu test = new Psimu(iniOrbit, EARTH, UserFramesConfsEnum.IGNORE, integrationData, vehicle, mm, forces, manSeq, attitudeLaw);
</syntaxhighlight>

Data initialization

2025-10-10T11:56:55Z

Admin : /* Earth features */

The main modifications between V11.3 and previous versions are due to the use of original [http://patrius.cnes.fr PATRIUS] classes rather than to use "Custom" classes originally proposed by [http://genopus.cnes.fr GENOPUS]. Anyway, some "Custom" classes still remain as [http://patrius.cnes.fr PATRIUS] classes are not sufficiently consistent.

== Orbit ==

To initialize an orbit, we simply have to build it using [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] object. For example:

<syntaxhighlight lang="java">
final TimeScale TUC = TimeScalesFactory.getUTC();
final AbsoluteDate date = new AbsoluteDate("2010-01-01T12:00:00.000", TUC);
final double sma = Constants.WGS84_EARTH_EQUATORIAL_RADIUS + 250.e3;
final double ecc = 0.;
final double inc = FastMath.toRadians(51.6);
final double raan = FastMath.toRadians(0.);
final double pa = FastMath.toRadians(0.);
final double ano = FastMath.toRadians(0.);
final Frame GCRF = FramesFactory.getGCRF();
final KeplerianOrbit iniOrbit =
new KeplerianOrbit(sma, ecc, inc, raan, pa, ano, PositionAngle.MEAN, GCRF, date, MU);
</syntaxhighlight>

== Earth features ==

Data equivalent to the “[[Earth_Features|Earth features]]” tab are distributed via two arguments:

:1. A ExtendedOneAxisEllipsoid object which will define the shape of the planet
<syntaxhighlight lang="java">
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, FramesFactory.getITRF(), "EARTH");
</syntaxhighlight>
:2. A type of enumerates that will propose some pre-defined configurations as:
:* '''NOTHING''' (all options set to null)
:* '''ONLY_PREC_NUT''' (only precession and nutation)
:* '''FACTORY''' (equivalent to the most complete definition as in the GUI)
:* '''IGNORE''' (nothing is define internally by '''PSIMU''' which will take into account the user parametrization previously done)

== Vehicle ==

Since V11.3, it is no more necessary to pass an Assembly object but a Vehicle one. Anyway, it is allways mandatory to pass a MassProvider object, issued from the Vehicle one. It could seem curious but it is due to the fact that, if we have maneuvers, it will be mandatory to initialize them with the same MassProvider (see example [[#Maneuvers|here]]).

In fact, we need to pass both an Assembly and a MassProvider. It could seem curious but it is due to the fact that, if we have maneuvers, it will be mandatory to initialize them with the same MassProvider (see example [[#Maneuvers|here]]). To get them, we will use the createAssembly() method given by Vehicle class.

<syntaxhighlight lang="java">
final Assembly assembly = vehicle.createAssembly(GCRF);
final MassProvider mm = new MassModel(assembly);
</syntaxhighlight>

'''''Note : for CPU time purpose it is recommanded that the frame (GCRF in the previous example), mandatory in the construction of the vehicle, must be exactly the same that the one used for the propagation.'''''

In the example below, we will then use the Vehicle class initializing mass and aerodynamic properties (here no engines and no tanks):

<syntaxhighlight lang="java">
// Dry mass
final double dryMass = 1000.;
final MassProperty dryMassProperty = new MassProperty(dryMass);

// Shape
final double sref = 5.0;
Sphere sphere = new Sphere(sref);
final RightParallelepiped solarPanels = new RightParallelepiped(10., 0., 0.);
VehicleSurfaceModel vehicleRefSurface = new VehicleSurfaceModel(sphere, solarPanels);

// Aerodynamic properties
final double cd = 2.0;
final double cl = 0.;
final AerodynamicProperties aerodynamicProperties = new AerodynamicProperties(vehicleRefSurface, cd, cl);

final Vehicle vehicle = new Vehicle(vehicleRefSurface, null, dryMassProperty, aerodynamicProperties, null, null, null);

final Assembly assembly = vehicle.createAssembly(GCRF);
final MassProvider mm = new MassModel(assembly);
</syntaxhighlight>

'''''Note : due to a PATRIUS anomaly, if the user needs to define solar panels characteristics, it is mandatory to use the Vehicle constructor with all parameters and the VehiculeSurfaceModel including the panels as above (and not a list of Facet); also, do not use the setters methods.'''''

== Forces ==

Since V11.3, to define, which forces will be applied along the trajectory, we use the [http://patrius.cnes.fr PATRIUS] ForceModelsData class (no more necessary to use the specific CustomForceModels class which does not exist anymore).

=== Potential ===
In the following example, we will initialize the potential model ('''mandatory''').

<syntaxhighlight lang="java">
// Potential
final ForceModel potential = new DirectBodyAttraction(EarthGravitationalModelFactory.getBalmino(GravityFieldNames.GRGS, "grim4s4_gr", 0, 0, true));

final ForceModelsData forces = new ForceModelsData(potential, null, null, null, null, null, null, null, null, null, null, null, null, null, null);
</syntaxhighlight>

=== Aerodynamic ===

Then we could add an aerodynamic force model. Since V11.3, it is no more necessary to use "Custom" classes.

<syntaxhighlight lang="java">
final double REQ = Constants.WGS84_EARTH_EQUATORIAL_RADIUS;
final double FLAT = Constants.WGS84_EARTH_FLATTENING;
final Frame ITRF = FramesFactory.getITRF();
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, ITRF, "EARTH");

final Atmosphere atmosphere = new US76(EARTH);
final DragForce dragForce = new DragForce(1., atmosphere, assembly);

forces.setDragForce(dragForce);
</syntaxhighlight>

=== Solar radiative pressure ===

Here are explained how to use both radiative pressure and rediffused radiative pressure force models. Again, since V11.3, no more tu use old "Custom" classes.

<syntaxhighlight lang="java">
final CelestialBody sunBody = new MeeusSun();
final double dRef = 1.4959787E11;
final double pRef = 4.5605E-6;
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, ITRF, "EARTH");

SolarRadiationPressureEllipsoid radPres = new SolarRadiationPressureEllipsoid(dRef, pRef, sunBody, EARTH, assembly, 1.);

forces.setSolarRadiationPressure(radPres);

// By default values used when GUI mode ...
final int inCorona = 1;
final int inMeridian = 10;
final IEmissivityModel inEmissivityModel = new KnockeRiesModel();
// Value accessible via GUI mode
final boolean inAlbedo = false;
final boolean inIr = false;
final double coefAlbedo = 1.;
final double coefIr = 1.;

RediffusedRadiativeModel rdm = new RediffusedRadiativeModel(inAlbedo, inIr, coefAlbedo, coefIr, assembly);
RediffusedRadiationPressure reDiff = new RediffusedRadiationPressure(sunBody, GCRF, inCorona, inMeridian, inEmissivityModel, rdm);

forces.setRediffusedRadiationPressure(reDiff);
</syntaxhighlight>

=== Specific forces ===

It is also possible to add specific forces via the addForceModel() method as below:

<syntaxhighlight lang="java">
final Psimu test = new Psimu(...);
test.addForceModel(myForce);
</syntaxhighlight>

== Maneuvers ==

If the user wants to add some maneuvers, it will have to do it using the [[https://logiciels.cnes.fr/en/node/78?type=desc GENOPUS]] Custom ManeuverSequence class. Indeed, this class is derivated from the PATRIUS ManeuverSequence but allows taking into account Engines and Tanks notion. From [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] V3.4, it will be possible to directly use [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] class.

=== Propulsive properties ===

First, the user will have to define propulsive properties with engine(s) and tank(s).

<syntaxhighlight lang="java">
// Propulsive properties
final PropulsiveProperty engine = new PropulsiveProperty(400, 320.);
engine.setPartName("ENGINE");
final ArrayList<PropulsiveProperty> listOfEngines = new ArrayList<PropulsiveProperty>();
listOfEngines.add(engine);
final TankProperty tank = new TankProperty(200.);
tank.setPartName("TANK");
final ArrayList<TankProperty> listOfTanks = new ArrayList<TankProperty>();
listOfTanks.add(tank);
listOfTanks.add(tank);

final Vehicle vehicle = new Vehicle(vehicleRefSurface, null, dryMassProperty, null, null, listOfEngines, listOfTanks);
</syntaxhighlight>

=== Sequence ===

Then, a maneuver sequence will be created thanks to the CustomManeuverSequence (the [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] ManeuverSequence is not directly used as it does not still manage events.

=== Impulsive maneuver ===

Here we have an example of a 10m/s impulse maneuver in TNW occuring for an AOL of 180 degrees:

<syntaxhighlight lang="java">
final double aol = FastMath.toRadians(180.);
final CustomAOLDetector aolDetector = new CustomAOLDetector(aol, PositionAngle.TRUE, GCRF, MAXCHECK, THRESHOLD, Action.STOP);
final IntervalOccurrenceDetectorWrapper impEvent = new IntervalOccurrenceDetectorWrapper(aolDetector, 1, 1, 1, Action.STOP);
final Vector3D deltaV = new Vector3D(10., 0., 0.);
final CustomImpulseManeuver imp = new CustomImpulseManeuver("Impulse maneuver", listOfEngines.get(0), listOfTanks.get(0), LOFType.TNW, impEvent, deltaV, mm);
</syntaxhighlight>

''
'''Note: it is mandatory to configure the event with a STOP action (needed by [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]]).'''
''

At last, the user will create the maneuver sequence to pass to '''PSIMU''':

<syntaxhighlight lang="java">
final CustomManeuverSequence manSeq = new CustomManeuverSequence(0., 0.);
manSeq.addManeuver(imp);
</syntaxhighlight>

=== Constant thrust maneuver ===

The next source code shows how to define a constant thrust maneuver …

<syntaxhighlight lang="java">
final double start = iniOrbit.getKeplerianPeriod();
final AbsoluteDate startDate = date.shiftedBy(start);
final CustomDateDetector startEvent = new CustomDateDetector(startDate, MAXCHECK, THRESHOLD, Action.STOP);
final double dur = 1000.;
final AbsoluteDate endDate = startDate.shiftedBy(dur);
final CustomDateDetector stopEvent = new CustomDateDetector(endDate, MAXCHECK, THRESHOLD, Action.STOP);
final Vector3D direction = new Vector3D(-1., 0., 0.);
CustomConstantManeuver cont =
new CustomConstantManeuver("Continuous maneuver", listOfEngines.get(0), listOfTanks.get(0), LOFType.TNW, startEvent, stopEvent, direction, mm);
</syntaxhighlight>

== Attitude ==

It is mandatory to get at least one attitude law. With the V11.0, it is not possible to have only one law and it is mandatory to use the “switch” possibility by using the [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] AttitudesSequence class.

This example shows how to define a single law (available since V11.1):

<syntaxhighlight lang="java">
final AttitudeLaw attitudeLaw = new LofOffset(LOFType.TNW);
</syntaxhighlight>

This other example uses a switching possibility:

<syntaxhighlight lang="java">
final AttitudeLaw law = new LofOffset(LOFType.TNW, RotationOrder.ZYX, 0., 0., 0.);
final double maxCheck = AbstractDetector.DEFAULT_MAXCHECK;
final double threshold = AbstractDetector.DEFAULT_THRESHOLD;
final EventDetector event =
new DateDetector(date, maxCheck, threshold, Action.RESET_STATE);
final AttitudesSequence seqAtt = new AttitudesSequence();
seqAtt.addSwitchingCondition(law, event, true, false, law);
</syntaxhighlight>

'''''Note : be very careful not to use by default constructors for event detectors as they introduce a STOP event, so your propagation will stop anyway !'''''

== Integration ==

Then integration data have to be defined. Here an example with RK4 integrator …

<syntaxhighlight lang="java">
final double duration = 86400.;
final double hStop = 120.e+3;
final PsimuPropagationData propagationData = new PsimuPropagationData(duration, GCRF, hStop);
final double step = 5.;
final RK4data integrationData = new RK4data(propagationData, step);
</syntaxhighlight>

… or with the DOP integrator …

<syntaxhighlight lang="java">
final double minStep = 0.1;
final double maxStep = 30.;
final double[] vecAbsoluteTolerance =
{ 1.0E-5, 1.0E-5, 1.0E-5, 1.0E-8, 1.0E-8, 1.0E-8 };
final double[] vecRelativeTolerance =
{ 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8 };
final double absMassTolerance = 1.0E-3;
final double relMassTolerance = 1.0E-2;
final double positionError = 0.;
final DopData intData = new DopData(propagationData, minStep, maxStep, vecAbsoluteTolerance, vecRelativeTolerance, absMassTolerance, relMassTolerance);
</syntaxhighlight>

== PSIMU object ==

As we have all mandatory data to initialize PSIMU, we can build such an object (note that in this example there is a “null” argument for the sequence of maneuvers.

<syntaxhighlight lang="java">
final Psimu test = new Psimu(iniOrbit, EARTH, UserFramesConfsEnum.IGNORE, integrationData, vehicle, mm, forces, manSeq, attitudeLaw);
</syntaxhighlight>

Data initialization

2025-10-10T11:55:50Z

Admin : /* Potential */

The main modifications between V11.3 and previous versions are due to the use of original [http://patrius.cnes.fr PATRIUS] classes rather than to use "Custom" classes originally proposed by [http://genopus.cnes.fr GENOPUS]. Anyway, some "Custom" classes still remain as [http://patrius.cnes.fr PATRIUS] classes are not sufficiently consistent.

== Orbit ==

To initialize an orbit, we simply have to build it using [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] object. For example:

<syntaxhighlight lang="java">
final TimeScale TUC = TimeScalesFactory.getUTC();
final AbsoluteDate date = new AbsoluteDate("2010-01-01T12:00:00.000", TUC);
final double sma = Constants.WGS84_EARTH_EQUATORIAL_RADIUS + 250.e3;
final double ecc = 0.;
final double inc = FastMath.toRadians(51.6);
final double raan = FastMath.toRadians(0.);
final double pa = FastMath.toRadians(0.);
final double ano = FastMath.toRadians(0.);
final Frame GCRF = FramesFactory.getGCRF();
final KeplerianOrbit iniOrbit =
new KeplerianOrbit(sma, ecc, inc, raan, pa, ano, PositionAngle.MEAN, GCRF, date, MU);
</syntaxhighlight>

== Earth features ==

Data equivalent to the “[[Earth_Features|Earth features]]” tab are distributed via two arguments:

:1. A ExtendedOneAxisEllipsoid object which will define the shape of the planet
<syntaxhighlight lang="java">
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, ITRF, "EARTH");
</syntaxhighlight>
:2. A type of enumerates that will propose some pre-defined configurations as:
:* '''NOTHING''' (all options set to null)
:* '''ONLY_PREC_NUT''' (only precession and nutation)
:* '''FACTORY''' (equivalent to the most complete definition as in the GUI)
:* '''IGNORE''' (nothing is define internally by '''PSIMU''' which will take into account the user parametrization previously done)

== Vehicle ==

Since V11.3, it is no more necessary to pass an Assembly object but a Vehicle one. Anyway, it is allways mandatory to pass a MassProvider object, issued from the Vehicle one. It could seem curious but it is due to the fact that, if we have maneuvers, it will be mandatory to initialize them with the same MassProvider (see example [[#Maneuvers|here]]).

In fact, we need to pass both an Assembly and a MassProvider. It could seem curious but it is due to the fact that, if we have maneuvers, it will be mandatory to initialize them with the same MassProvider (see example [[#Maneuvers|here]]). To get them, we will use the createAssembly() method given by Vehicle class.

<syntaxhighlight lang="java">
final Assembly assembly = vehicle.createAssembly(GCRF);
final MassProvider mm = new MassModel(assembly);
</syntaxhighlight>

'''''Note : for CPU time purpose it is recommanded that the frame (GCRF in the previous example), mandatory in the construction of the vehicle, must be exactly the same that the one used for the propagation.'''''

In the example below, we will then use the Vehicle class initializing mass and aerodynamic properties (here no engines and no tanks):

<syntaxhighlight lang="java">
// Dry mass
final double dryMass = 1000.;
final MassProperty dryMassProperty = new MassProperty(dryMass);

// Shape
final double sref = 5.0;
Sphere sphere = new Sphere(sref);
final RightParallelepiped solarPanels = new RightParallelepiped(10., 0., 0.);
VehicleSurfaceModel vehicleRefSurface = new VehicleSurfaceModel(sphere, solarPanels);

// Aerodynamic properties
final double cd = 2.0;
final double cl = 0.;
final AerodynamicProperties aerodynamicProperties = new AerodynamicProperties(vehicleRefSurface, cd, cl);

final Vehicle vehicle = new Vehicle(vehicleRefSurface, null, dryMassProperty, aerodynamicProperties, null, null, null);

final Assembly assembly = vehicle.createAssembly(GCRF);
final MassProvider mm = new MassModel(assembly);
</syntaxhighlight>

'''''Note : due to a PATRIUS anomaly, if the user needs to define solar panels characteristics, it is mandatory to use the Vehicle constructor with all parameters and the VehiculeSurfaceModel including the panels as above (and not a list of Facet); also, do not use the setters methods.'''''

== Forces ==

Since V11.3, to define, which forces will be applied along the trajectory, we use the [http://patrius.cnes.fr PATRIUS] ForceModelsData class (no more necessary to use the specific CustomForceModels class which does not exist anymore).

=== Potential ===
In the following example, we will initialize the potential model ('''mandatory''').

<syntaxhighlight lang="java">
// Potential
final ForceModel potential = new DirectBodyAttraction(EarthGravitationalModelFactory.getBalmino(GravityFieldNames.GRGS, "grim4s4_gr", 0, 0, true));

final ForceModelsData forces = new ForceModelsData(potential, null, null, null, null, null, null, null, null, null, null, null, null, null, null);
</syntaxhighlight>

=== Aerodynamic ===

Then we could add an aerodynamic force model. Since V11.3, it is no more necessary to use "Custom" classes.

<syntaxhighlight lang="java">
final double REQ = Constants.WGS84_EARTH_EQUATORIAL_RADIUS;
final double FLAT = Constants.WGS84_EARTH_FLATTENING;
final Frame ITRF = FramesFactory.getITRF();
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, ITRF, "EARTH");

final Atmosphere atmosphere = new US76(EARTH);
final DragForce dragForce = new DragForce(1., atmosphere, assembly);

forces.setDragForce(dragForce);
</syntaxhighlight>

=== Solar radiative pressure ===

Here are explained how to use both radiative pressure and rediffused radiative pressure force models. Again, since V11.3, no more tu use old "Custom" classes.

<syntaxhighlight lang="java">
final CelestialBody sunBody = new MeeusSun();
final double dRef = 1.4959787E11;
final double pRef = 4.5605E-6;
final ExtendedOneAxisEllipsoid EARTH =
new ExtendedOneAxisEllipsoid(REQ, FLAT, ITRF, "EARTH");

SolarRadiationPressureEllipsoid radPres = new SolarRadiationPressureEllipsoid(dRef, pRef, sunBody, EARTH, assembly, 1.);

forces.setSolarRadiationPressure(radPres);

// By default values used when GUI mode ...
final int inCorona = 1;
final int inMeridian = 10;
final IEmissivityModel inEmissivityModel = new KnockeRiesModel();
// Value accessible via GUI mode
final boolean inAlbedo = false;
final boolean inIr = false;
final double coefAlbedo = 1.;
final double coefIr = 1.;

RediffusedRadiativeModel rdm = new RediffusedRadiativeModel(inAlbedo, inIr, coefAlbedo, coefIr, assembly);
RediffusedRadiationPressure reDiff = new RediffusedRadiationPressure(sunBody, GCRF, inCorona, inMeridian, inEmissivityModel, rdm);

forces.setRediffusedRadiationPressure(reDiff);
</syntaxhighlight>

=== Specific forces ===

It is also possible to add specific forces via the addForceModel() method as below:

<syntaxhighlight lang="java">
final Psimu test = new Psimu(...);
test.addForceModel(myForce);
</syntaxhighlight>

== Maneuvers ==

If the user wants to add some maneuvers, it will have to do it using the [[https://logiciels.cnes.fr/en/node/78?type=desc GENOPUS]] Custom ManeuverSequence class. Indeed, this class is derivated from the PATRIUS ManeuverSequence but allows taking into account Engines and Tanks notion. From [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] V3.4, it will be possible to directly use [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] class.

=== Propulsive properties ===

First, the user will have to define propulsive properties with engine(s) and tank(s).

<syntaxhighlight lang="java">
// Propulsive properties
final PropulsiveProperty engine = new PropulsiveProperty(400, 320.);
engine.setPartName("ENGINE");
final ArrayList<PropulsiveProperty> listOfEngines = new ArrayList<PropulsiveProperty>();
listOfEngines.add(engine);
final TankProperty tank = new TankProperty(200.);
tank.setPartName("TANK");
final ArrayList<TankProperty> listOfTanks = new ArrayList<TankProperty>();
listOfTanks.add(tank);
listOfTanks.add(tank);

final Vehicle vehicle = new Vehicle(vehicleRefSurface, null, dryMassProperty, null, null, listOfEngines, listOfTanks);
</syntaxhighlight>

=== Sequence ===

Then, a maneuver sequence will be created thanks to the CustomManeuverSequence (the [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] ManeuverSequence is not directly used as it does not still manage events.

=== Impulsive maneuver ===

Here we have an example of a 10m/s impulse maneuver in TNW occuring for an AOL of 180 degrees:

<syntaxhighlight lang="java">
final double aol = FastMath.toRadians(180.);
final CustomAOLDetector aolDetector = new CustomAOLDetector(aol, PositionAngle.TRUE, GCRF, MAXCHECK, THRESHOLD, Action.STOP);
final IntervalOccurrenceDetectorWrapper impEvent = new IntervalOccurrenceDetectorWrapper(aolDetector, 1, 1, 1, Action.STOP);
final Vector3D deltaV = new Vector3D(10., 0., 0.);
final CustomImpulseManeuver imp = new CustomImpulseManeuver("Impulse maneuver", listOfEngines.get(0), listOfTanks.get(0), LOFType.TNW, impEvent, deltaV, mm);
</syntaxhighlight>

''
'''Note: it is mandatory to configure the event with a STOP action (needed by [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]]).'''
''

At last, the user will create the maneuver sequence to pass to '''PSIMU''':

<syntaxhighlight lang="java">
final CustomManeuverSequence manSeq = new CustomManeuverSequence(0., 0.);
manSeq.addManeuver(imp);
</syntaxhighlight>

=== Constant thrust maneuver ===

The next source code shows how to define a constant thrust maneuver …

<syntaxhighlight lang="java">
final double start = iniOrbit.getKeplerianPeriod();
final AbsoluteDate startDate = date.shiftedBy(start);
final CustomDateDetector startEvent = new CustomDateDetector(startDate, MAXCHECK, THRESHOLD, Action.STOP);
final double dur = 1000.;
final AbsoluteDate endDate = startDate.shiftedBy(dur);
final CustomDateDetector stopEvent = new CustomDateDetector(endDate, MAXCHECK, THRESHOLD, Action.STOP);
final Vector3D direction = new Vector3D(-1., 0., 0.);
CustomConstantManeuver cont =
new CustomConstantManeuver("Continuous maneuver", listOfEngines.get(0), listOfTanks.get(0), LOFType.TNW, startEvent, stopEvent, direction, mm);
</syntaxhighlight>

== Attitude ==

It is mandatory to get at least one attitude law. With the V11.0, it is not possible to have only one law and it is mandatory to use the “switch” possibility by using the [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] AttitudesSequence class.

This example shows how to define a single law (available since V11.1):

<syntaxhighlight lang="java">
final AttitudeLaw attitudeLaw = new LofOffset(LOFType.TNW);
</syntaxhighlight>

This other example uses a switching possibility:

<syntaxhighlight lang="java">
final AttitudeLaw law = new LofOffset(LOFType.TNW, RotationOrder.ZYX, 0., 0., 0.);
final double maxCheck = AbstractDetector.DEFAULT_MAXCHECK;
final double threshold = AbstractDetector.DEFAULT_THRESHOLD;
final EventDetector event =
new DateDetector(date, maxCheck, threshold, Action.RESET_STATE);
final AttitudesSequence seqAtt = new AttitudesSequence();
seqAtt.addSwitchingCondition(law, event, true, false, law);
</syntaxhighlight>

'''''Note : be very careful not to use by default constructors for event detectors as they introduce a STOP event, so your propagation will stop anyway !'''''

== Integration ==

Then integration data have to be defined. Here an example with RK4 integrator …

<syntaxhighlight lang="java">
final double duration = 86400.;
final double hStop = 120.e+3;
final PsimuPropagationData propagationData = new PsimuPropagationData(duration, GCRF, hStop);
final double step = 5.;
final RK4data integrationData = new RK4data(propagationData, step);
</syntaxhighlight>

… or with the DOP integrator …

<syntaxhighlight lang="java">
final double minStep = 0.1;
final double maxStep = 30.;
final double[] vecAbsoluteTolerance =
{ 1.0E-5, 1.0E-5, 1.0E-5, 1.0E-8, 1.0E-8, 1.0E-8 };
final double[] vecRelativeTolerance =
{ 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8, 1.0E-8 };
final double absMassTolerance = 1.0E-3;
final double relMassTolerance = 1.0E-2;
final double positionError = 0.;
final DopData intData = new DopData(propagationData, minStep, maxStep, vecAbsoluteTolerance, vecRelativeTolerance, absMassTolerance, relMassTolerance);
</syntaxhighlight>

== PSIMU object ==

As we have all mandatory data to initialize PSIMU, we can build such an object (note that in this example there is a “null” argument for the sequence of maneuvers.

<syntaxhighlight lang="java">
final Psimu test = new Psimu(iniOrbit, EARTH, UserFramesConfsEnum.IGNORE, integrationData, vehicle, mm, forces, manSeq, attitudeLaw);
</syntaxhighlight>

Basic Principle

2025-10-10T11:54:32Z

Admin :

'''PSIMU''' proposed a Java interface

Most of the objects to pass as input data are [https://www.connectbycnes.fr/en/patrius PATRIUS] ones. Some of them are specific to '''PSIMU''' or [https://www.connectbycnes.fr/en/genopus GENOPUS] but, in that case, most of the time, it is due to the fact that these objects are not yet included in the used [https://www.connectbycnes.fr/en/patrius PATRIUS] version: their name will then start by “''Custom…''”.

So, to use this Java interface, the developer will have to:
# Initialize [https://www.connectbycnes.fr/en/patriusdataset Patrius Dataset].
# Initialize the type of [https://www.connectbycnes.fr/en/patrius PATRIUS] MODELS (since V11.8)
# Create a '''PSIMU''' object using its available constructor.
# Calling for the propagation in master or slave mode.
# Calling for “''getter''” methods to extract after the propagation all useful information.

For the first point, there are two possibilities:

* Calling directly the [https://www.connectbycnes.fr/en/patriusdataset Patrius Dataset] method:

<syntaxhighlight lang="java">
// Patrius Dataset initialization
PatriusDataset.addResourcesFromPatriusDataset() ;
</syntaxhighlight>

* Or calling a specific '''PSIMU''' method allowing to manage both [https://www.connectbycnes.fr/en/patriusdataset Patrius Dataset] included Inside the '''PSIMU''' jar and local data (see [[Earth_Features#Frames configuration|here]]):

<syntaxhighlight lang="java">
// Patrius data set initialization
final String addDataName = AppPSimuConfigurationProperties.getInstance().getAdditionalPatriusFolder();
AppPSimuConfigurationProperties.iniPatriusDataset(addDataName);
</syntaxhighlight>

For the second point, insert this line of code ('''mandatory since V11.8'''):

<syntaxhighlight lang="java">
// Set NEW_MODELS for PATRIUS configuration
PatriusConfiguration.setPatriusCompatibilityMode(PatriusVersionCompatibility.NEW_MODELS);
</syntaxhighlight>

Basic Principle

2025-10-10T11:53:11Z

Admin :

'''PSIMU''' proposed a Java interface

Most of the objects to pass as input data are [https://www.connectbycnes.fr/en/patrius PATRIUS] ones. Some of them are specific to '''PSIMU''' or [https://www.connectbycnes.fr/en/genopus GENOPUS] but, in that case, most of the time, it is due to the fact that these objects are not yet included in the used [https://www.connectbycnes.fr/en/patrius PATRIUS] version: their name will then start by “''Custom…''”.

So, to use this Java interface, the developer will have to:
# Initialize [https://www.connectbycnes.fr/en/patriusdataset Patrius Dataset].
# Initialize the type of [https://www.connectbycnes.fr/en/patrius PATRIUS] MODELS (since V11.8)
# Create a '''PSIMU''' object using its available constructor.
# Calling for the propagation in master or slave mode.
# Calling for “''getter''” methods to extract after the propagation all useful information.

For the first point, there are two possibilities:

* Calling directly the [https://www.connectbycnes.fr/en/patriusdataset Patrius Dataset] method:

<syntaxhighlight lang="java">
// Patrius Dataset initialization
PatriusDataset.addResourcesFromPatriusDataset() ;
</syntaxhighlight>

* Or calling a specific '''PSIMU''' method allowing to manage both [https://www.connectbycnes.fr/en/patriusdataset Patrius Dataset] included Inside the '''PSIMU''' jar and local data (see [[Earth_Features#Frames configuration|here]]):

<syntaxhighlight lang="java">
// Patrius data set initialization
final String addDataName = AppPSimuConfigurationProperties.getInstance().getAdditionalPatriusFolder();
AppPSimuConfigurationProperties.iniPatriusDataset(addDataName);
</syntaxhighlight>

For the second point, insert theis line of code:

<syntaxhighlight lang="java">
// Set NEW_MODELS for PATRIUS configuration
PatriusConfiguration.setPatriusCompatibilityMode(PatriusVersionCompatibility.NEW_MODELS);
</syntaxhighlight>

Basic Principle

2025-10-10T11:52:56Z

Admin :

'''PSIMU''' proposed a Java interface

Most of the objects to pass as input data are [https://www.connectbycnes.fr/en/patrius PATRIUS] ones. Some of them are specific to '''PSIMU''' or [https://www.connectbycnes.fr/en/genopus GENOPUS] but, in that case, most of the time, it is due to the fact that these objects are not yet included in the used [https://www.connectbycnes.fr/en/patrius PATRIUS] version: their name will then start by “''Custom…''”.

So, to use this Java interface, the developer will have to:
# Initialize [https://www.connectbycnes.fr/en/patriusdataset Patrius Dataset].
# Initialize the type of [https://www.connectbycnes.fr/en/patrius PATRIUS] MODELS (since V11.8)
# Create a '''PSIMU''' object using its available constructor.
# Calling for the propagation in master or slave mode.
# Calling for “''getter''” methods to extract after the propagation all useful information.

For the first point, there are two possibilities:

* Calling directly the [https://www.connectbycnes.fr/en/patriusdataset Patrius Dataset] method:

<syntaxhighlight lang="java">
// Patrius Dataset initialization
PatriusDataset.addResourcesFromPatriusDataset() ;
</syntaxhighlight>

* Or calling a specific '''PSIMU''' method allowing to manage both [https://www.connectbycnes.fr/en/patriusdataset Patrius Dataset] included Inside the '''PSIMU''' jar and local data (see [[Earth_Features#Frames configuration|here]]):

<syntaxhighlight lang="java">
// Patrius data set initialization
final String addDataName = AppPSimuConfigurationProperties.getInstance().getAdditionalPatriusFolder();
AppPSimuConfigurationProperties.iniPatriusDataset(addDataName);
</syntaxhighlight>

For the second point, insert theis line of code:

<syntaxhighlight lang="java">
// Set NEW_MODELS for PATRIUS configuration
PatriusConfiguration.setPatriusCompatibilityMode(PatriusVersionCompatibility.NEW_MODELS);
</syntaxhighlight>

Main differences between V11.7.4 and V11.8

2025-06-20T12:19:23Z

Admin : /* Anomaly corrections */

== 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 a 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.
* Some corrections thanks to new version of [https://www.connectbycnes.fr/en/genopus GENOPUS].

Basic Principle

2025-06-20T12:17:54Z

Admin :

'''PSIMU''' proposed a Java interface

Most of the objects to pass as input data are [https://www.connectbycnes.fr/en/patrius PATRIUS] ones. Some of them are specific to '''PSIMU''' or [https://www.connectbycnes.fr/en/genopus GENOPUS] but, in that case, most of the time, it is due to the fact that these objects are not yet included in the used [https://www.connectbycnes.fr/en/patrius PATRIUS] version: their name will then start by “''Custom…''”.

So, to use this Java interface, the developer will have to:
# Initialize [https://www.connectbycnes.fr/en/patriusdataset Patrius Dataset].
# Create a '''PSIMU''' object using its available constructor.
# Calling for the propagation in master or slave mode.
# Calling for “''getter''” methods to extract after the propagation all useful information.

For the first point, there are two possibilities:

* Calling directly the [https://www.connectbycnes.fr/en/patriusdataset Patrius Dataset] method:

<syntaxhighlight lang="java">
// Patrius Dataset initialization
PatriusDataset.addResourcesFromPatriusDataset() ;
</syntaxhighlight>

* Or calling a specific '''PSIMU''' method allowing to manage both [https://www.connectbycnes.fr/en/patriusdataset Patrius Dataset] included Inside the '''PSIMU''' jar and local data (see [[Earth_Features#Frames configuration|here]]):

<syntaxhighlight lang="java">
// Patrius data set initialization
final String addDataName = AppPSimuConfigurationProperties.getInstance().getAdditionalPatriusFolder();
AppPSimuConfigurationProperties.iniPatriusDataset(addDataName);
</syntaxhighlight>

Basic Principle

2025-06-20T12:17:24Z

Admin :

'''PSIMU''' proposed a Java interface

Most of the objects to pass as input data are [https://www.connectbycnes.fr/en/patrius PATRIUS] ones. Some of them are specific to '''PSIMU''' or [https://www.connectbycnes.fr/en/genopus GENOPUS] but, in that case, most of the time, it is due to the fact that these objects are not yet included in the used [https://www.connectbycnes.fr/en/patrius PATRIUS] version: their name will then start by “''Custom…''”.

So, to use this Java interface, the developer will have to:
# Initialize [https://www.connectbycnes.fr/en/patriusdataset Patrius Dataset].
# Create a '''PSIMU''' object using its available constructor.
# Calling for the propagation in master or slave mode.
# Calling for “''getter''” methods to extract after the propagation all useful information.

For the first point, there are two possibilities:

* Calling directly the [[https://logiciels.cnes.fr/en/content/patriusdataset Patrius Dataset]] method:

<syntaxhighlight lang="java">
// Patrius Dataset initialization
PatriusDataset.addResourcesFromPatriusDataset() ;
</syntaxhighlight>

* Or calling a specific '''PSIMU''' method allowing to manage both [[https://logiciels.cnes.fr/en/content/patriusdataset Patrius Dataset]] included Inside the '''PSIMU''' jar and local data (see [[Earth_Features#Frames configuration|here]]):

<syntaxhighlight lang="java">
// Patrius data set initialization
final String addDataName = AppPSimuConfigurationProperties.getInstance().getAdditionalPatriusFolder();
AppPSimuConfigurationProperties.iniPatriusDataset(addDataName);
</syntaxhighlight>

Basic Principle

2025-06-20T12:16:02Z

Admin :

'''PSIMU''' proposed a Java interface

Most of the objects to pass as input data are [[http://patrius.cnes.fr PATRIUS]] ones. Some of them are specific to '''PSIMU''' or [https://www.connectbycnes.fr/en/genopus there] but, in that case, most of the time, it is due to the fact that these objects are not yet included in the used [[http://patrius.cnes.fr PATRIUS]] version: their name will then start by “''Custom…''”.

So, to use this Java interface, the developer will have to:
# Initialize [[https://logiciels.cnes.fr/en/content/patriusdataset Patrius Dataset]].
# Create a '''PSIMU''' object using its available constructor.
# Calling for the propagation in master or slave mode.
# Calling for “''getter''” methods to extract after the propagation all useful information.

For the first point, there are two possibilities:

* Calling directly the [[https://logiciels.cnes.fr/en/content/patriusdataset Patrius Dataset]] method:

<syntaxhighlight lang="java">
// Patrius Dataset initialization
PatriusDataset.addResourcesFromPatriusDataset() ;
</syntaxhighlight>

* Or calling a specific '''PSIMU''' method allowing to manage both [[https://logiciels.cnes.fr/en/content/patriusdataset Patrius Dataset]] included Inside the '''PSIMU''' jar and local data (see [[Earth_Features#Frames configuration|here]]):

<syntaxhighlight lang="java">
// Patrius data set initialization
final String addDataName = AppPSimuConfigurationProperties.getInstance().getAdditionalPatriusFolder();
AppPSimuConfigurationProperties.iniPatriusDataset(addDataName);
</syntaxhighlight>

Basic Principle

2025-06-20T12:15:07Z

Admin :

'''PSIMU''' proposed a Java interface

Most of the objects to pass as input data are [[http://patrius.cnes.fr PATRIUS]] ones. Some of them are specific to '''PSIMU''' or [[http://genopus.cnes.fr GENOPUS]] but, in that case, most of the time, it is due to the fact that these objects are not yet included in the used [[http://patrius.cnes.fr PATRIUS]] version: their name will then start by “''Custom…''”.

So, to use this Java interface, the developer will have to:
# Initialize [[https://logiciels.cnes.fr/en/content/patriusdataset Patrius Dataset]].
# Create a '''PSIMU''' object using its available constructor.
# Calling for the propagation in master or slave mode.
# Calling for “''getter''” methods to extract after the propagation all useful information.

For the first point, there are two possibilities:

* Calling directly the [[https://logiciels.cnes.fr/en/content/patriusdataset Patrius Dataset]] method:

<syntaxhighlight lang="java">
// Patrius Dataset initialization
PatriusDataset.addResourcesFromPatriusDataset() ;
</syntaxhighlight>

* Or calling a specific '''PSIMU''' method allowing to manage both [[https://logiciels.cnes.fr/en/content/patriusdataset Patrius Dataset]] included Inside the '''PSIMU''' jar and local data (see [[Earth_Features#Frames configuration|here]]):

<syntaxhighlight lang="java">
// Patrius data set initialization
final String addDataName = AppPSimuConfigurationProperties.getInstance().getAdditionalPatriusFolder();
AppPSimuConfigurationProperties.iniPatriusDataset(addDataName);
</syntaxhighlight>

Basic Principle

2025-06-20T12:14:22Z

Admin :

'''PSIMU''' proposed a Java interface

Most of the objects to pass as input data are [[http://patrius.cnes.fr PATRIUS]] ones. Some of them are specific to '''PSIMU''' or [[https://genopus.cnes.fr GENOPUS]] but, in that case, most of the time, it is due to the fact that these objects are not yet included in the used [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] version: their name will then start by “''Custom…''”.

So, to use this Java interface, the developer will have to:
# Initialize [[https://logiciels.cnes.fr/en/content/patriusdataset Patrius Dataset]].
# Create a '''PSIMU''' object using its available constructor.
# Calling for the propagation in master or slave mode.
# Calling for “''getter''” methods to extract after the propagation all useful information.

For the first point, there are two possibilities:

* Calling directly the [[https://logiciels.cnes.fr/en/content/patriusdataset Patrius Dataset]] method:

<syntaxhighlight lang="java">
// Patrius Dataset initialization
PatriusDataset.addResourcesFromPatriusDataset() ;
</syntaxhighlight>

* Or calling a specific '''PSIMU''' method allowing to manage both [[https://logiciels.cnes.fr/en/content/patriusdataset Patrius Dataset]] included Inside the '''PSIMU''' jar and local data (see [[Earth_Features#Frames configuration|here]]):

<syntaxhighlight lang="java">
// Patrius data set initialization
final String addDataName = AppPSimuConfigurationProperties.getInstance().getAdditionalPatriusFolder();
AppPSimuConfigurationProperties.iniPatriusDataset(addDataName);
</syntaxhighlight>

Main differences between V11.7.4 and V11.8

2025-06-20T12:09:31Z

Admin : /* Look and Feel */

== 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 a 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.

Main differences between V11.7.4 and V11.8

2025-06-20T12:08:49Z

Admin : /* Java Heap space management */

== 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.

Main differences between V11.7.4 and V11.8

2025-06-20T12:08:31Z

Admin :

== 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.

Main differences between V11.7.4 and V11.8

2025-06-20T12:08:09Z

Admin : /* Output Mean models */

== 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.

Main differences between V11.7.4 and V11.8

2025-06-20T12:07:41Z

Admin :

== Output Mean models ==

It is now possible to choose the type of mean models for the output variables in the following list:

* Lyddane longues périodes
* Lyddane séculaire
* 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.

Main differences between V11.7.4 and V11.8

2025-06-20T12:00:06Z

Admin :

== Output Mean models =

It is now possible to choose the type of mean models for the output variables in the following list:

* Lyddane longues périodes
* Lyddane séculaire
* 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.

Main differences between V11.7.4 and V11.8

2025-06-20T11:50:10Z

Admin : Page créée avec « TBW ... »

TBW ...

MediaWiki:Sidebar

2025-06-20T11:49:55Z

Admin :

*
* PSIMU
** WELCOME_TO_THE_PSIMU_WIKI|Welcome
** Quick_start|Quick start
** News|News
* GUI Mode
** Overall_Presentation|Overall presentation
** Initial_Orbit|Initial Orbit
** Earth_Features|Earth features
** Vehicle|Vehicle
** Forces|Forces
** Maneuvers|Maneuvers
** Attitude|Attitude
** Integrator|Integrator
** Events|Events
** Output|Output
** Console|Console
* Batch mode
** BatchMode|How to call it
* Java interface
** Basic_Principle|Basic principle
** Data_initialization|Data initialization
** Propagation|Propagation
** Printing|Printing results
** Customize_output_variables|Customize output variables
* Evolutions
** Main_differences_between_V11.7.4_and_V11.8|Main differences between V11.7.4 and V11.8
** Main_differences_between_V11.7.3_and_V11.7.4|Main differences between V11.7.3 and V11.7.4
** Main_differences_between_V11.7.2_and_V11.7.3|Main differences between V11.7.2 and V11.7.3
** Main_differences_between_V11.7.1_and_V11.7.2|Main differences between V11.7.1 and V11.7.2
** Main_differences_between_V11.6.2_and_V11.7.1|Main differences between V11.6.2 and V11.7.1
** Main_differences_between_V11.5_and_V11.6.2|Main differences between V11.5 and V11.6.2
** Main_differences_between_V11.4.1_and_V11.5|Main differences between V11.4.1 and V11.5
** Main_differences_between_V11.4_and_V11.4.1|Main differences between V11.4 and V11.4.1
** Main_differences_between_V11.3_and_V11.4|Main differences between V11.3 and V11.4
** Main_differences_between_V11.2_and_V11.3|Main differences between V11.2 and V11.3
** Main_differences_between_V11.1_and_V11.2|Main differences between V11.1 and V11.2
** Main_differences_between_V11.0_and_V11.1|Main differences between V11.0 and V11.1
* Training
** :File:TutorialsForV11.7.1.zip|Tutorials package for V11.7.x
** :File:TutorialsForV11.6.zip|Tutorials package for V11.6
** :File:TutorialsForV11.5.zip|Tutorials package for V11.5
** :File:TutorialsForV11.4.zip|Tutorials package for V11.4
** :File:TutorialsForV11.3.zip|Tutorials package for V11.3
** :File:TutorialsForV11.2.zip|Tutorials package for V11.2
** :File:TutorialsForV11.0.zip|Tutorials package for V11.0
* Links
** https://logiciels.cnes.fr/en/home|CNES freeware server

Java Doc

2025-02-07T14:27:57Z

Admin :

[{{PathCurrentJavaDoc}} Current Java Doc] 

[{{CurrentServer}}/images/upload/JavaDocs/V11.7.4 Java Doc 11.7.4] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.7.3 Java Doc 11.7.3] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.7.2 Java Doc 11.7.2] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.7.1 Java Doc 11.7.1] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.6.2 Java Doc 11.6.2] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.5 Java Doc 11.5] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.4.1 Java Doc 11.4.1] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.4 Java Doc 11.4] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.3 Java Doc 11.3] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.2 Java Doc 11.2] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.1 Java Doc 11.1] 
[{{CurrentServer}}/images/upload/JavaDocs/V11.0 Java Doc 11.0]

Modèle:PathCurrentJavaDoc

2025-02-07T14:26:53Z

Admin :

{{CurrentServer}}//images/upload/JavaDocs/V11.7.4

Modèle:CurrentServer

2025-02-07T13:30:53Z

Admin :

https://psimu.cnes.fr

Previous versions

2023-12-06T11:55:56Z

Admin :

* version 11.7.3: see [[Main_differences_between_V11.7.2_and_V11.7.3|here]].
* version 11.7.2: see [[Main_differences_between_V11.7.1_and_V11.7.2|here]].
* version 11.7.1: see [[Main_differences_between_V11.6.2_and_V11.7.1|here]].
* version 11.6.2: see [[Main_differences_between_V11.5_and_V11.6.2|here]].
* version 11.5: this version is essentially due to an update of the lower level libraries [http://www.genius.fr GENIUS] V1.10.1, [http://www.genius.fr GENOPUS] V2.2 and [http://www.patrius.fr PATRIUS] V4.6. For more details, see [[Main_differences_between_V11.4.1_and_V11.5|here]].
* version 11.4.1: correcting two V11.4 anomalies (see [[Main_differences_between_V11.4_and_V11.4.1|here]]).
* version 11.4: linked with [http://patrius.cnes.fr PATRIUS] V4.4 version, correcting V11.3 anomalies and with some interesting new functionalities (see [[Main_differences_between_V11.3_and_V11.4|here]]).
* version 11.3: linked with [http://patrius.cnes.fr PATRIUS] V4.1.1 version, correcting V11.2 anomalies and with some interesting new functionalities (see [[Main_differences_between_V11.2_and_V11.3|here]]).
* version 11.2/11.2.1 : first version available [https://cnes.fr/fr '''CNES'''] outside; it corrects few minor anomalies and is now linked with [https://logiciels.cnes.fr/en/content/patriusdataset PatriusDataset] 1.0.3.
* version 11.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.
* version 11.0: first Java version available only inside [https://cnes.fr/fr '''CNES'''].

Note: Java version available externally to [https://cnes.fr/fr '''CNES'''] (previous versions to V11.x were coded in Fortran 95 and V11.0 were only for internal [https://cnes.fr/fr '''CNES'''] purposes).

Current version

2023-12-06T11:55:21Z

Admin :

This version corrects an anomaly on the attitude laws display, (see [http://psimu.cnes.fr/index.php/Main_differences_between_V11.7.3_and_V11.7.4 here]).

Known bugs of this version:

Current version

2023-12-06T11:54:58Z

Admin :

This version corrects an anomaly on the attitude laws display class, (see [http://psimu.cnes.fr/index.php/Main_differences_between_V11.7.3_and_V11.7.4 here]).

Known bugs of this version:

WELCOME TO THE PSIMU WIKI

2023-12-06T11:53:24Z

Admin : /* DESCRIPTION */

__NOTOC__
Welcome to the '''PSIMU''' wiki, a [https://cnes.fr/fr '''CNES'''] flight dynamics tool. As it is coded in Java, this product is available for any kind of platforms owning a JVM.

== DESCRIPTION ==

[[What_is_Psimu|'''What is PSIMU?''']]

::'''PSIMU''' is a [https://cnes.fr/fr '''CNES'''] tool allowing to propagate trajectories around the Earth.

[[Current_version|'''Current version''']]

::The current version is: '''V11.7.4'''.

[[Previous_versions|'''Previous versions''']]

::Describes evolutions thanks to previous versions.

== USE IT ==

[[Where_to_get_it|'''Where to get it?''']]

::Where to download it.

[[Quick start|'''Quick start''']]

::First steps with '''PSIMU'''

[[User_Manual|'''User Manual''']]

::'''PSIMU''' may be used very quickly via its '''GUI''' facilitating context elaboration and results exploitation. No code knowledge is necessary.
::Anyway, it is also possible to use it in '''batch''' mode (especially on grid computers with no display properties) or using its '''Java''' interface.

== DOCUMENTATION ==

[[Java_Doc|'''Java Doc''']]

::Access to current and old Java doc.

[[Dependencies|'''Dependencies''']]

::Describes dependencies with other products.

[[News|'''News''']]

::Main evolutions of the tool or its Wiki.

Main differences between V11.7.3 and V11.7.4

2023-12-06T11:52:39Z

Admin :

The only difference is the correction of an anomaly in a [http://genopus.cnes.fr '''GENOPUS'''] class that did not allow to display the available attitude laws.

Main differences between V11.7.3 and V11.7.4

2023-12-06T11:50:23Z

Admin : Page créée avec « The only difference is the correction of an anomaly in a GENOPUS class that did not allow to display the available attitude laws. »

The only difference is the correction of an anomaly in a GENOPUS class that did not allow to display the available attitude laws.

MediaWiki:Sidebar

2023-12-06T11:49:14Z

Admin :

*
* PSIMU
** WELCOME_TO_THE_PSIMU_WIKI|Welcome
** Quick_start|Quick start
** News|News
* GUI Mode
** Overall_Presentation|Overall presentation
** Initial_Orbit|Initial Orbit
** Earth_Features|Earth features
** Vehicle|Vehicle
** Forces|Forces
** Maneuvers|Maneuvers
** Attitude|Attitude
** Integrator|Integrator
** Events|Events
** Output|Output
** Console|Console
* Batch mode
** BatchMode|How to call it
* Java interface
** Basic_Principle|Basic principle
** Data_initialization|Data initialization
** Propagation|Propagation
** Printing|Printing results
** Customize_output_variables|Customize output variables
* Evolutions
** Main_differences_between_V11.7.3_and_V11.7.4|Main differences between V11.7.3 and V11.7.4
** Main_differences_between_V11.7.2_and_V11.7.3|Main differences between V11.7.2 and V11.7.3
** Main_differences_between_V11.7.1_and_V11.7.2|Main differences between V11.7.1 and V11.7.2
** Main_differences_between_V11.6.2_and_V11.7.1|Main differences between V11.6.2 and V11.7.1
** Main_differences_between_V11.5_and_V11.6.2|Main differences between V11.5 and V11.6.2
** Main_differences_between_V11.4.1_and_V11.5|Main differences between V11.4.1 and V11.5
** Main_differences_between_V11.4_and_V11.4.1|Main differences between V11.4 and V11.4.1
** Main_differences_between_V11.3_and_V11.4|Main differences between V11.3 and V11.4
** Main_differences_between_V11.2_and_V11.3|Main differences between V11.2 and V11.3
** Main_differences_between_V11.1_and_V11.2|Main differences between V11.1 and V11.2
** Main_differences_between_V11.0_and_V11.1|Main differences between V11.0 and V11.1
* Training
** :File:TutorialsForV11.7.1.zip|Tutorials package for V11.7.x
** :File:TutorialsForV11.6.zip|Tutorials package for V11.6
** :File:TutorialsForV11.5.zip|Tutorials package for V11.5
** :File:TutorialsForV11.4.zip|Tutorials package for V11.4
** :File:TutorialsForV11.3.zip|Tutorials package for V11.3
** :File:TutorialsForV11.2.zip|Tutorials package for V11.2
** :File:TutorialsForV11.0.zip|Tutorials package for V11.0
* Links
** https://logiciels.cnes.fr/en/home|CNES freeware server

Java Doc

2023-12-06T11:48:40Z

Admin :

[{{PathCurrentJavaDoc}} Current Java Doc] 

[{{CurrentServer}}/uploads/JavaDocs/V11.7.4 Java Doc 11.7.4] 
[{{CurrentServer}}/uploads/JavaDocs/V11.7.3 Java Doc 11.7.3] 
[{{CurrentServer}}/uploads/JavaDocs/V11.7.2 Java Doc 11.7.2] 
[{{CurrentServer}}/uploads/JavaDocs/V11.7.1 Java Doc 11.7.1] 
[{{CurrentServer}}/uploads/JavaDocs/V11.6.2 Java Doc 11.6.2] 
[{{CurrentServer}}/uploads/JavaDocs/V11.5 Java Doc 11.5] 
[{{CurrentServer}}/uploads/JavaDocs/V11.4.1 Java Doc 11.4.1] 
[{{CurrentServer}}/uploads/JavaDocs/V11.4 Java Doc 11.4] 
[{{CurrentServer}}/uploads/JavaDocs/V11.3 Java Doc 11.3] 
[{{CurrentServer}}/uploads/JavaDocs/V11.2 Java Doc 11.2] 
[{{CurrentServer}}/uploads/JavaDocs/V11.1 Java Doc 11.1] 
[{{CurrentServer}}/uploads/JavaDocs/V11.0 Java Doc 11.0]

Modèle:PathCurrentJavaDoc

2023-12-06T11:48:15Z

Admin :

{{CurrentServer}}//uploads/JavaDocs/V11.7.4

Dependencies

2023-12-06T11:44:51Z

Admin :

{| class="wikitable"
|-
|Version
|style="text-align:center;"|11.7.4
|style="text-align:center;"|11.7.1/11.7.2/11.7.3
|style="text-align:center;"|11.6.2
|style="text-align:center;"|11.5
|style="text-align:center;"|11.4 / 11.4.1
|style="text-align:center;"|11.3
|style="text-align:center;"|11.2 / 11.2.1
|style="text-align:center;"|11.1
|style="text-align:center;"|11.0
|-
|Disponibility
|style="text-align:center;"|from 6th Dec 2023
|style="text-align:center;"|from 8th Jun 2023
|style="text-align:center;"|from 7th Mar 2022
|style="text-align:center;"|from 18th Feb 2021
|style="text-align:center;"|from 8th Nov 2019
|style="text-align:center;"|from 14th Dec 2018
|style="text-align:center;"|from 14th Nov 2017
|style="text-align:center;"| -
|style="text-align:center;"| -
|-
|Javadoc
|style="text-align:center;"|yes
|style="text-align:center;"|yes
|style="text-align:center;"|yes
|style="text-align:center;"|yes
|style="text-align:center;"|yes
|style="text-align:center;"|yes
|style="text-align:center;"|yes
|style="text-align:center;"|yes
|style="text-align:center;"|yes
|- style="vertical-align:top;"
|Dependencies
|style="text-align:center;"|Java 1.8 Patrius 4.10.2 (not compatible with other versions) PatriusDataset 1.4.3 Genopus 2.4.2 Genius 1.12.1 Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4 sqlite-jdbc 3.15.1 exp4j 0.4.8
|style="text-align:center;"|Java 1.8 Patrius 4.10.2 (not compatible with other versions) PatriusDataset 1.4.3 Genopus 2.4.1 Genius 1.12.1 Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4 sqlite-jdbc 3.15.1 exp4j 0.4.8
|style="text-align:center;"|Java 1.8 Patrius 4.8 (not compatible with other versions) PatriusDataset 1.1.0 Genopus 2.3.3 Genius 1.11.4 Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4 sqlite-jdbc 3.15.1 exp4j 0.4.8
|style="text-align:center;"|Java 1.8 Patrius 4.6 (not compatible with other versions) PatriusDataset 1.1.0 Genopus 2.2 Genius 1.10.1 Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4 sqlite-jdbc 3.15.1
|style="text-align:center;"|Java 1.8 Patrius 4.4 (not compatible with other versions) PatriusDataset 1.1.0 Genopus 2.1.1 Genius 1.9.1 Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4 sqlite-jdbc 3.15.1
|style="text-align:center;"|Java 1.7 Patrius 4.1.1 (not compatible with other versions) PatriusDataset 1.1.0 Genopus 2.0.1 Genius 1.8 Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4 sqlite-jdbc 3.15.1
|style="text-align:center;"|Java 1.7 Patrius 3.3 (not compatible with other versions) PatriusDataset 1.0.3 Genopus 1.3.1 Genius 1.7 Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4 sqlite-jdbc 3.15.1
|style="text-align:center;"|Java 1.7 Patrius 3.3 (not compatible with other versions) PatriusDataset 1.0.2 Genopus 1.3 Genius 1.7 Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4 sqlite-jdbc 3.15.1
|style="text-align:center;"|Java 1.7 Patrius 3.2 (not compatible with other versions) PatriusDataset 1.0.2 Genopus 1.2.1 Genius 1.6.x Miglayout 4.2 Jdom 1.1.2 Gettext-commons 0.9.8 JFreeChart 1.0.19 commons-io 2.4
|}

News

2023-12-06T11:43:46Z

Admin :

__NOTOC__
=== 6th December2023 ===
* New V11.7.4 version

=== 16th November 2023 ===
* New V11.7.3 version

=== 10th October 2023 ===
* An anomaly has been found : see [[Main_differences_between_V11.7.2_and_V11.7.3|here]]

=== 5th July 2023 ===
* Wiki update thanks to the new V11.7.2 version.

=== 8th June 2023 ===
* Wiki update thanks to the new V11.7.1 version.

=== 8th March 2022 ===
* Wiki update thanks to the new V11.6.2 version.

=== 18th February 2021 ===

* New V11.5 version.

=== 16th December 2020 ===

* Some information about [https://logiciels.cnes.fr/en/content/patriusdataset Patrius Dataset] initialization (see [[Basic Principle|here]]).
* Precision about units in output files versus Java code output (see [[Propagation#Master mode|here]]).

=== 25th August 2020 ===

* When reading the initial orbit, '''PSIMU''' has not already read [[Earth_Features|Earth Features characteristics]]. So, in some cases, it may exit in an error mode (for example when using H0-n frames) saying that no EOP are available even if we do not need them as it will use the [[http://patrius.cnes.fr PATRIUS]] by default configuration.

=== 13rd May 2020 ===

* When using the Java API, due to a [http://patrius.cnes.fr PATRIUS] anomaly, if the user needs to define solar panels characteristics, it is mandatory to use the Vehicle constructor with all parameters and the VehiculeSurfaceModel including the panels as above (and not a list of Facet); also, do not use the setters methods.

=== 14th February 2020 ===

* New V11.4.1 version.

=== 28th January 2020 ===

* Identification of a bug when maneuvers are too near from the initial date.

=== 21st Jan 2020 ===
* Update of the the Wiki main page.

=== 13th January 2020 ===

* Identification of a bug with the header of ephemeris/events files for date variables.

=== 27th November 2019 ===

* Identification of a bug using the [[Output#Custom_plots|Custom plots]] tab.

=== 8th November 2019 ===

* Update thanks to the V11.4 version.

=== 23th September 2019 ===

* Information on the next V11.4 version.

=== 11th Sep 2019 ===
New predicted solar activity files are available [[:File:actsol.zip|here]].

=== 6th Sep 2019 ===

Provision of the XML structure corresponding to aerodynamic coefficients depending on altitude as used in the [https://logiciels.cnes.fr/en/content/stela STELA S/W]: [[:File:Stela_drag_coefficient.zip]]

=== 26th Aug 2019 ===

* New [[:File:gplot-1.9.zip|GPLOT utility]] availability thanks to [http://genius.cnes.fr GENIUS V1.9] version.

=== 29th May 2019 ===

* Three other "minor" bugs have been identified (see [[WELCOME_TO_THE_PSIMU_WIKI#CURRENT VERSION_:_V11.3|here]]).

=== 21st Jan 2019 ===

* Two "minor" bugs have been identified : cases of hyperbolic trajectories or zero propagation duration (see [[WELCOME_TO_THE_PSIMU_WIKI#CURRENT VERSION_:_V11.3|here]]).

=== 11th Jan 2019 ===

* An additional explanation about the Copy/Paste facility on orbit data (see [[Initial_Orbit#Copy/Paste|here]]).

=== 21st Dec 2018 ===

* Adding the possibility to download a utility to plot previously saved results (see [[Output#Plots#Custom_plots|here]]).

=== 20th Dec 2018 ===

* Explaining how to extract solar activity files (see [[Forces#Atmosphere|here]]).

=== 14th Dec 2018 ===

* Update due to the V11.3 version.

=== 1st Aug 2018 ===

* Explaining how to put additional data for Earth features (see [[Earth_Features#How_to_update_data|here]]).

Modèle:PathCurrentJavaDoc

2023-11-16T11:41:56Z

Admin :

{{CurrentServer}}//uploads/JavaDocs/V11.7.3