What's New | Resolved Issues | System Requirements | Transition Issues | Known Issues | Tracking Data Interface Version Changes | Background Information | Online Help Resources | ODTK 6.6 Features | ODTK 6.5.3 Features
ODTK 6.6.1 is a maintenance release with a few minor features and some bug fixes.
The CCSDS Tracking Data Message (TDM) reader was updated to include:
The apparent Sun direction has been added to the list of directions that can be used in the definition of aligned and constrained satellite attitude profiles.
The capability to use an N Plate solar radiation pressure model has been added. Plate definitions are supplied using a file interface that also exposes acceleration scaling parameters, which can be estimated.
These release notes contain information on system and disk space requirements for installing and running ODTK; information on new capabilities and features introduced in the current version of ODTK, including issues resolved from the prior version; transition information -- cautions, workarounds and operational tips -- to help maximize your successful use of the product; and a brief introduction to online help resources.
|New Capabilities and Resolved Issues in ODTK 6.6.1|
|94222||New function Satellite.ReferenceTrajectory.UpdateInitialCondition2() was added to allow passing satellite epoch in any valid date time format.|
|97294||The capability to an N Plate solar pressure model has been added. Plate definitions are supplied using a file interface that also exposes acceleration scaling parameters, which can be estimated.|
|101694||The BeiDou, Galileo, GLONASS, and QZSS catalog files were updated to reflect the latest constellation status.|
|102481||ODTK Help system has switched from using legacy *.chm file format to HTML based. Each version of ODTK comes with the local installation of help, while the latest version is always available online at help.agi.com/ODTK.|
|102634||Updates have been made to the CCSDS TDM data reader to accomodate the latest updates to the TDRS specific version of the format and to include support for improvements to TDM support are listed here:
|104226||STK and STK/Engine have been upgraded to use the Flexlm Publisher 22.214.171.124 to address security vulnerabilities reported in CVE-2018-20032, CVE-2018-200033, and CVE-2018-20034.|
|104574||An error in the computation of the accumulated delta V over finite maneuvers specified vis delta V input parameters has been corrected. The error was most evident in the output from the smoother for maneuvers with significant relative mass loss.|
|104654||STK better detects bad file formats when reading SP3 files.|
|104690||The GNSS constellation catalog files for the Beidou, GPS, and GLONASS constellations were updated to reflect the latest constellation status.|
|104693||If EmpiricalForces estimation was enabled, filter's functional attribute Filter.ViewRestartData() would return record data without populating any EmpiricalForces states info. This has been fixed.|
|104888||New method ODTK.Application.ResetRandomNumberGenerator(long newSeed) has been added that allows you to reinitialize internal RNG to its initial state without the need to restart ODTK.
While ODTK Simulator was always managing its own RNG seed, other functions such as Updating Initial Conditions with perturbations enabled, draw random numbers from a common RNG that has its seed persisting over the lifetime of the ODTK process.
|104983||ODTK build process has switched from Visual Studio 2017.9 (v15.9.5) compiler.|
|104999||A limitation in the assignment of tracking ids which could be used when using Space Based TDOA measurements has been eliminated. Previously, the tracking id of the space based receiver tracking instrument and the satellite on which it resided had to be the same. This is no longer the case.|
|105275||Errant reporting of the atmospheric density model name when running a Filter in ODTK version 6.4.1 or later while using a restart record generated in ODTK version earlier than 6.4.1 has been corrected. The prior error did not affect any computations, just the name of the density model displayed in reports.|
|105536||An error in the value of Cd used in the generation of ephemeris from the LS process when drag is estimated using the Cd Additive correction type has been corrected. The prior error resulted in the generation of incorrect ephemeris, but did not affect the solved for state of the estimator.|
|105549||The apparent Sun direction has been added to the list of directions that can be used in the definition of aligned and constrained satellite attitude profiles.|
This section includes ODTK system requirements.
Starting with version 6.3.2, ODTK is not supported on Windows XP.
Starting with version 6.5, ODTK is not supported on Windows Vista.
ODTK runs as a 32-bit application in a 64-bit Windows environment. Code samples are compiled for use in Visual Studio 2012. This is the last release as a 32-bit application.
|CPU Speed||2+ GHz|
|Processor||Intel Core Duo, SSE2 (or greater) Pentium 4 or Xeon Processors, or AMD Phenom or better CPU|
|Memory / RAM||3+ GB|
|Disk Space||4+ GB|
|Network Hardware||Network Card required|
ODTK can use up to 3 GB of memory/RAM and will take advantage of multiple processors if available depending on the type of analysis being done.
An ODTK installation requires 200-300 MB of disk space. Running a typical scenario, such as the Sapphire demo scenario that accompanies ODTK (3 satellites, 5 trackers x 3 days), takes about 600MB disk space for simulator, filter, and smoother runs. During such a run the memory footprint of ODTK is slightly over 110Mb.
Windows Server 2008 installations must have the Desktop Experience option turned on before running the ODTK install. This option is available from the Windows Control Panel.
Microsoft recommends running services under a specific user account and does not recommend running under the SYSTEM account unless absolutely necessary.
If you run ODTK under the Local System (SYSTEM) account on a 64-bit system you will need to create a
C:\Windows\SysWOW64\config\systemprofile\Documents folder and verify that the
C:\Windows\System32\config\systemprofile\Documents folder properly links to it and that both have appropriate permissions.
If you plan to run multiple instances of ODTK on the server you will need to ensure that the system is configured to reserve enough Desktop Heap Memory for each session. See blogs.technet.com for a discussion of the settings in
We recommend reserving ~256k of Desktop Heap for each instance of ODTK running on the system.
The following table lists the specific distributions and versions tested, and for which installation directions are provided. Other Linux distributions are likely to work as well, assuming the required dependencies are installed and available.
|Operating System||Latest update or service pack tested|
|Red Hat Enterprise Linux /CentOS 7.5||Update 4|
The following table lists the hardware and software requirements.
|Development disk space||1.76 GB|
|Deployment disk space||1.25 GB minimum, possibly more depending on specific application requirements|
You can use the following commands to find the package that provides a library:
RHEL/CentOS: yum whatprovides libgfortran.so.3. On the Ubuntu website, you can search the 'Ubuntu Packages Search' page at https://packages.ubuntu.com/ for the contents of the packages by providing the file name (e.g. libgfortran.so.3) as a keyword.
The following files are included:
|odtk_binaries_v6.6.0_x64.tgz||The ODTK Runtime binaries.|
|odtk_data_v6.6.0.tgz||The core ODTK data.|
|odtk_codesamples_v6.6.0.tgz||The ODTK documentation and Cross-Platform API code samples.|
To install the core ODTK Runtime files (needed for both development and deployment), issue the following commands:
tar -xvf ./odtk_binaries_v6.6.0_x64.tgz
tar -xvf ./odtk_data_v6.6.0.tgz
tar -xvf /odtk_codesamples_v6.6.0.tgz
Three environment variables need to be set. Note that these variables can be set from the shell or at initialization in your custom application if it is more convenient for your specific workflow.
The path to the bin directory needs to be added to your LD_LIBRARY_PATH environment variable:
bash: export LD_LIBRARY_PATH=<install dir>/bin:$LD_LIBRARY_PATH
csh: setenv LD_LIBRARY_PATH=<install dir>/bin:$LD_LIBRARY_PATH
Two environment variables need to be set up to indicate where ODTK reads its data from and where it stores the user specific configuration:
export ODTK_INSTALL_DIR=<install dir>
export ODTK_USER_DIR=<location for user specific data>
csh: setenv ODTK_INSTALL_DIR=<install dir>
setenv ODTK_USER_DIR=<location for user specific data>
Optional: the location for ODTK user configuration, if omitted, is set to $ODTK_USER_DIR/Config
export ODTK_CONFIG_DIR=<location of user configuration>
setenv ODTK_CONFIG_DIR=<location for user configuration>
When you request a license, you will receive a *.lic file. You need to copy that file to one of the locations where ODTK Runtime looks for that information:
ODTK Runtime does not currently support the following features found in ODTK Desktop:
It is suggested that you review the following list of cautions, workarounds and operational tips before using the current version of ODTK:
The database tables from the various *.*run files (*.filrun, *.smtrun, etc.) used by the Static Product Builder have been updated to reflect the changes in the naming of the solar radiation pressure parameter from Cp to Cr. Additional columns have been added to support the new additive and relative options for the solar radiation pressure and drag parameters. Users that have created their own custom report and graph styles in earlier versions of ODTK will need to update them to work with ODTK 6.3.0. Use the procedure below to update your reports. Graphs do not have an equivalent procedure, however you should test each custom graph to ensure that it continues to function as desired. If not, edit the graph style and update it appropriately.
From release to release, the contents of database tables used in the definition of report and graph styles may change, usually through the addition of new elements to the record definitions. These changes can impact the content of custom report styles created by the user. Before attempting to use a report style generated with a version prior to ODTK 6.3.0, a Verify Database operation should be performed and a new copy of the report style should be saved to a new directory. Overwriting the old style will cause that style to work incorrectly with the prior version of ODTK. The Verify Database operation is performed by highlighting the report style in the Static Product Builder, clicking on the Edit button then right clicking on the Database Fields and selecting Verify Database. After the verification completes, save the style.
Please see the ODTK Scripting Guide for changes to scripting interfaces and additional scripting examples.
The user should be aware of the following limitations and unresolved issues affecting ODTK as of the date of this release.
|07071||Tracker satellites cannot share tracking IDs with GPS constellation PRN numbers. If a scenario contains both an optical tracker satellite and a GPS constellation, and the tracker satellite has a tracking ID between 1-36, the tracking ID will become ambiguous.|
|10186||Users should not name objects using class names like Filter, Smoother, Simulator. Refer to the "VBA to VB.NET Migration" section of the ODTK Help.|
|23349||LaunchPad doesn't format dates in local format, it always uses MM/DD/YYYY even if machine is configured to show dates as DD/MM/YYYY.|
|29439||To avoid abnormal terminations that may occur when FLEXlm code is run with Windows Data Execution Prevention enabled, you need to change the DEP settings: Open the "System Properties", click on the "Advanced" tab and click on "Performance, Settings" button. This will bring up a dialog with three tabs. Click on the "DEP" tab and set the option to: "Turn on DEP for essential Windows programs and services only". You may need to restart the computer after that.|
|30517||The Plugins tab does not refresh the SupportsSave column. When you add a new plugin tracking data reader and click Apply, the column labeled SupportsSave is not refreshed. By default the value in this column is false, but after you add a new tracking data reader that supports save, then the value in this column should be true. The user must dismiss the panel and pull it back up to get the correct value.|
|31034||After a long predict, the covariance is quite large. A very large measurement update can drive the filter covariance negative.|
|31802||A GPS constellation object does not populate the PRNList until properties are applied. We suggest that when you first assign a source file to a GPS constellation, you press Apply before double-clicking on the PRNList to view its contents.|
|32139||State File To SP3 utility limits output to GPSSatellites named PRN01, PRN02, etc.|
|36839||If ODTK aborts or runs out of disk space then any active runfile is not saved in a valid state. This issue cannot be corrected without a big impact on processing speed (opening and closing the file and opening to append). The user is advised to monitor disk utilization and plan for large run files from ODTK to avoid disk space issues.|
|42672||Dynamic Earth Data does not use file find paths. Do not attempt to change the location from the default location.|
|45226||ODTK does not support saving and loading of files that use multi-byte character sets.|
|52010||Older AMD chips do not support "Streaming SIMD Extensions 2 (SSE2)". SSE2 was first used in ODTK v6.0. The following AMD chips do support SSE2:
|73396||Creating a report from the Static Product Builder and then choosing to export it to "Text" format may cause a crash. This is caused by a problem in the Crystal Reports package itself. Users are recommended to export to the Tab Separated or Comma Separated Value formats instead.|
|75024||There is an issue when exporting report data to CSV or TSV format of a field or fields possibly being missing. If this occurs there is a workaround:
|77998||There are a few styles, such as Avg*, Daily Avg*, and Satellite Pos Vel*, that use suppress conditionals to produce the requested data. Some reports that contain these styles cannot be exported to a CSV format using Crystal Reports. The workaround is to use a different export format or use ODTK's native *.exp styles.|
|100422||When using native support for 4K displays, the Object Properties tree [+] and [-] boxes do not scale properly and will appear very small.|
Open topic with navigation