NASA’s ORDEM 3.2 model is now integrated and can be used for analysis.

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

Please be aware that the scripting editor is not compatible with interplanetary mission definitions. You can use such files only for batch configuration (basis file as is without modifications).

Please be aware that the current GUI design is mainly designed for Full-HD resolution and a windows visualisation scale of 100%. Lower resolutions/a higher scale can lead to some windows not showing all its contents. E.g. for the frame pointing option window, the “ok” and “cancel” buttons might not be visible. Hence, the setting can not be confirmed and applied. In this case, please try to apply a smaller windows visualisation scaling as a first approach or a higher resolution.

Please consider that MEMR2 relies on Microsoft Visual Studio C++ Redistributables 2008 (32bit). If you have the problem that during the analysis with MEMR2 the Spd… files are not found, please go to “ESABASE2-ROOTFOLDER\Solver\DEBRIS\MEMR2” and double click on “MEMR2CLW.exe”. If you get a message pointing out a problem with “Side-by-Side” installation, then you need to install the MSVC 2008 Redistributables (32bit), e.g. can be found in E2_ROOT\components\install-supplements.

When using the OEM2SPK converter, please make sure no major step size from one step to another occur, since this exceeds the default threshold for the MAXIMUM_SEP_QUOTIENT parameter of OEM2SPK which is currently used. For more information, refer to https://naif.jpl.nasa.gov/pub/naif/utilities/PC_Windows_64bit/spk2oem.ug.

The externally provided OEM2SPK only processes input arguments with maximum 80 characters within it’s setup file. This may lead to problems when trying to use the meta kernel e.g. So keep in mind to keep the number of characters lower this threshold to avoid errors during the conversion process.

Please consider that the maximum time span for a S/C trajectory is 100 years, you will not be able to use trajectory kernels including longer mission durations. (This does not apply for the basic kernels provided by the Meta Kernel, but only the trajectory kernel with the trajectory to be analysed.)

There are inconsistencies with the time representation in the mission file. Each point of 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 with subtracting one hour from the times of the visualised trajectory list. As a consequence, for manually adding individual trajectory points, one hour offset needs to be foreseen.

NASA’s ORDEM 3.2 model is now integrated and can be used for analysis.

Several minor bugs have been fixed.

A new version (1.21) of the Framework User Manual was established.

A new version (1.17) of the ESABASE2/Debris User Manual was established.

A new version (1.10) of the ESABASE2/Debris Technical Description was established.

Post processor is currently not available.

NetGen is currently not available in ESABASE2 Linux Version.

ORDEM2K is currently not usable under Linux.

Insufficient error message is provided in the case Weak-Spot visualisation is selected for mission results.

Currently the direct definition of minimum and maximum values in the 2D diagrams are not applied correctly. However, the zoom function can be used to get the desired closer look.

There are inconsistencies with the time representation in the mission file. (See Notes).