Changed to Windows 64bit (no 32bit versions for ESABASE2 release < 11)

Changed to Linux 64bit (no 32bit version for ESABASE2/Debris release 11).

Changed to Linux 64bit (no 32bit version for ESABASE2/Debris release 11).

Tested on Ubuntu 18.04 LTS 64bit, will most probably run under all common 64bit Linux distributions.

In the case of a Demo version, you should get the according hint and proceed by clicking the OK button, in the case of a bundle (e.g. Debris) you need to perform the machine binding (live or per Email).

ESABASE2 is not crashing anymore upon an allocated memory size of over 1GB. Nevertheless, it is reasonable to restart ESABASE2 occasionally, especially if working with big geometries.

Changed to Linux 64bit (no 32bit version for ESABASE2/Debris release 11).

An individual kernel containing the trajectory of the S/C (“Trajectory File”)

A Meta Kernel includes the leap seconds kernel, the planetary kernel, and the kernel of bodies that are referenced or wished to be considered.

A default Meta Kernel is provided listing the provided kernels:
latest_leapseconds.tls.pc, earth_assoc_itrf93.tf (for considering ITRF-93 reference frame in OEM files), de438.bsp, mar097.bsp.

An individual Meta Kernel can be defined and provided a listing of the kernels to be considered.

All referred objects, e.g. via the pointing based on SPICE, need to be listed within the mentioned Meta Kernel.

The default Meta Kernel is applied upon changing to interplanetary mode (placed in the “SPICEKernels” folder) but can be changed.

Tested on Ubuntu 18.04 LTS 64bit, will most probably run under all common 64bit Linux distributions.

Orbit selection extracted and independent from the orbit parameters with the selections:

Mercury

Venus

Earth (Orbit Type selections available, else generic (GEN))

Moon

Mars

Interplanetary (SUN)

Mission Editor is divided in two parts now:

Left side: orbital/trajectory/mission parameters

Right side: 3D visualization of the trajectory/orbit (only Earth and Interplanetary mode are visualized)

Interplanetary Mission:

An individual kernel containing the trajectory of the S/C (“Trajectory File”)

The S/C trajectory file is the basis for the mission definition

Probe selection (in case of multiple): The probe name and its ID are displayed.

The minimum and maximum dates of the trajectory are shown and are the default simulation start and end dates.

A stepping algorithm splits the considered trajectory duration in a number of orbital points based on the spatial density variation along the trajectory. The orbital points are listed in the “Trajectory Points” table.

Trajectory points can be added or removed by the user.

The default Meta Kernel is applied upon changing to interplanetary mode (placed in “SPICEKernels” folder) but can be changed. The S/C trajectory file is the basis for the mission definition

3D trajectory visualization:

Different information to be visualized can be activated or deactivated:

S/C trajectory (the straight connection between selected trajectory points).

Color coding of the S/C trajectory according to the spatial density (IMEM based, densities can be displayed).

Names of the planets.

The densities can be indicated by the trajectory path, coloring the trajectory part based on the previous orbital point.

Highlighting trajectory points.

Planetary orbital arcs passed during the S/C trajectory time (additionally to thin lines that visualize the orbits of the planets for slightly more than one orbit).

Cartesian grid visualization.

Coordinate system visualization, centered in each planet and the Sun.

Visualization of model range (IMEM or IMEM2 or MEMR2 Interplanetary or MEM 3). Also, it is highlighted whether the trajectory is inside the range of a model.

Please consider that the Divine-Staubach model of MASTER 8.0.2 (used by ESABASE2) has a bug and overestimates the fluxes. MASTER 8 executable will need an update after this problem is fixed by the MASTER developer.

Please consider that only the reference data (November 2016) is provided with ESABASE2 and you require the population data from https://sdup.esoc.esa.int/ to run other epochs.

If you encounter the error message “FATAL ERROR in subroutine ‘prbindexcheck’:…” running MASTER 8, please check if the population data for your epoch is available to MASTER 8.

IMEM accumulates orbital points with the same step size in groups and is executed for each group multiple times to achieve all required information per group considered.

IMEM2 accumulates orbital points with the same step size in groups and is executed once for each group to achieve all required information (one STENVI file per group).

MEM 3 is executed once for all considered points before the orbital points loop, except in the trajectory mode it is executed for each orbital point individually.

Pointing based on a NAIF ID is possible now:

For pointing, in the geometry file, “SPICE” can be selected and a NAIF ID can be defined

A SPICE kernel containing the object to be pointed at needs to be available and listed in the Meta Kernel (for the analysis).

Median, minimum-, and maximum values and both quartiles in-between for impact -azimuth, -elevation, and -velocity can be visualized in the 3D results.

The impact angles are visualized on an element by an arrow and the velocity by the color of the element with color code.

The angle definition is based on the S/C velocity and the direction to the central body.
Note: Please consider, due to the dependency on the S/C velocity the direction is only available for orbital points visualisation not for mission (changing velocity direction from OP to OP). Error message is shown in the case Weak-Spot visualisation is selected for mission results and the arrows are not visualised, only the velocity colour code.

Element results have been extended with additional visualization capabilities. Also, various export features are available for the element results. The selected exports will be stored in a folder with the name of the element’s object shape within the chosen destination folder. (R12 only)

There are inconsistencies with the time representation in the mission file. Each point of the generated trajectory points lists is having an offset of one hour (plus one hour). Manually added trajectory points appear with the exact user-defined date. However, it can be generalized that internal processing works by subtracting one hour from the times of the visualized trajectory list. As a consequence, for manually adding individual trajectory points, one one-hour offset needs to be foreseen.