Main differences between V2.0.1 and V2.1

Compatibility with PATRIUS

This version is compatible with the version 4.4 of the PATRIUS library.

New Time scales

If the default mode is the same than for the previous versions, it is now possible to customize the time scales menu of the GPAbsoluteDate widget and thus to add these additional scales (available inside the PATRIUS library) as in the example below:

ts[0] = GPDateTimeScale.GMST;
ts[1] = GPDateTimeScale.GST;
ts[2] = GPDateTimeScale.TCG;
ts[3] = GPDateTimeScale.UTC;
gpDate = new GPAbsoluteDate("Date:", date0, ts);

New maneuvers trigerring criteriae

New criteriae on nodes and apsides have been added to the previous ones (relative or absolute dates and AOL)

Impulsive maneuvers with orbital parameters criteriae

It is now possible to define an impulsive maneuver giving orbital parameters increments:

• on semi-major axis
• on eccentricity (and semi-major axis eventually)
• on inclination (and semi-major axis eventually)

Recurrent date events

It is now possible to define date (relative or absolute ones) events with a recurrence (for example each day).

New widget for numerical integrators definition

New specific widgets have been created to deal with numerical integrators as some of ones defined in PATRIUS: Runge Kutta 4, Runge Kutta 6 and Dormand Price 853

Additional validity criteria on PRS coefficients

Besides validity interval of [0,1] for each coefficient, there is an additional test on the sum of the three coefficients (absorption, specular and diffuse) that must be equal to 1.

Best management of consistency between force model and vehicle panels

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

By default attitude law

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

New autonomous tool to work on orbit data

For people who want to work on orbit characteristics (date, frame, parameters) without coding, it is now possible to use a dedicated autonomous tool with its own GUI (gporbitconvertor-2.1-jar-with-dependencies.jar).

Anomaly corrections

• Impossibility to initialize an orbit using a H0-n frame.
• Calling GPVisibilityFromStationDetector or GPAttitudeSequence widgets make the tool incompatible with a headless mode (no display).