ODTK 6.5.2 Release Notes

ODTK 6.5.2 adds a few new features and maintenance.

System requirements

This will be the last 32-bit ODTK release. Future versions of ODTK will be 64-bit only. This means that they will only be able to run on 64-bit operating system installs.

Reporting and Graphing

There is a new option in the Edit | Preferences menu to allow a "quiet" mode so that the Message Viewer window isn't flooded with messages when generating reports and graphs.

General

We have switched from the IRI2007 ionosphere model to the IRI2016Model.

We have added full support for 4K displays.

Satellites

We have added three new atmosphere density models: DTM 2012 (for doing OD around the Earth), and MarsGRAM 2005 and 2010 (when doing OD around Mars).

Added Martian moons as third body perturbations.

Added new drag and solar radiation pressure models that allow the use of a file based look-up table as a function of time or argument of latitude.

Added support for using VNC and VVLH frames when specifying maneuvers. This should make it easier to sync up maneuvers planned in STK/Astrogator with the equivalent model in ODTK.

Filter

The filter can now automatically drop finite maneuevers from the state space.

Simulator

We've added the ability to simulate DOR (Differential One-way Ranging) measurements to the simulator. These can then be used to produce Delta-DOR measurements for deep space tracking analysis.

Resolved issues

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.5.2
Tracking No.	Description
59317	Backwards Filter support has been added.
75474	Option to use DTM 2012 atmospheric model has been added.
82815	The MarsGRAM 2005 and 2010 Martian atmospheric density models are now available for use when propagating orbits about Mars.
86615	C# and C++ examples of using slimmed down version of ODTK Engine (both 32 and 64-bit) have been added to the help. See this page.
96389	The issuance of warning messages related to the existence of space weather information when running the Filter, Simulator, and Least Squares processes has been updated to provide more useful information to the user.
97141	The capability to use a file based time history of measurement bias values in the filter has been enhanced and clarified to allow specification of the type of bias information (complete or correction) contained in the file. In prior versions of ODTK, the data was intepreted as representing the complete definitive bias, but this was not well documented and inconsistent with the tools to generate bias history files from ODTK outputs.
97295	The ability to specify area variations via a file interface to tabulated values for the modeling of drag and solar pressure forces on a spacecraft has been added. Tabulated area values can be specified explicitly as a function of time or can be described as a function of the argument of latitude.
97296	Automatic dynamic state space operations in the Filter have been extended to include estimated finite maneuver states. This new feature will allow finite maneuver states to automatically be added and removed from state space as appropriate once the finite maneuver definition has been added to a satellite.
98919	The ability to use the VNC frame commonly used in STK Astrogator and the VVLH frame for the specification of maneuver information has been added.
99720	The ability to simulate ground based tracking data for GNSS satellites whose orbits are specified via a GNSS reference file has been added. The Filter will now also process ground based measurements against GNSS satellites whose orbits are specified via a GNSS reference file.
100601	A simulation capability for Differenced One-way Range (DOR) measurements has been added as a functional attribute on the Simulator object. Generated spacecraft and quasar DOR measurements can then be combined and processed as DeltaDOR measurements during estimation.
100905	This is to inform you that recently our installer executable has been logged as a “Trojan” from the anti-virus software product, Vir.IT eXplorer:Trojan.Win32.Generic.ZUR. Product security is of paramount importance at Analytical Graphics Inc. We would like to reassure you that we have fully investigated this finding and there is NO malicious malware hidden in the files of our product. Sixty-seven other anti-virus product scans on https://www.virustotal.com/ and at AGI have no such reports. You can go to the VirusTotal.com website and enter the hash of the file install.exe to get the report, SHA-256: 1C678E5B563A52FF03CE806B2DD00F270761BEB7DE9864FB97C9A4D8DBFDBFE6. The false positive was reported to Vir.IT eXplorer and will be updated in a subsequent release of the product’s virus definitions.

System requirements

This section includes ODTK system requirements.

Supported Operating Systems

Windows 7 32-bit and 64-bit
Windows 10
Windows Server 2008, 2012

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.

Hardware requirements

Hardware	Requirements
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

Note: 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.

Compatibility with Windows Server 2008

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 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems

We recommend reserving ~256k of Desktop Heap for each instance of ODTK running on the system.

Transition issues

It is suggested that you review the following list of cautions, workarounds and operational tips before using the current version of ODTK:

Updating Custom Report and Graph Styles for ODTK 6

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.

Changes in Database Table Contents

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.

Scripting Guide Updates

Please see the ODTK Scripting Help topics for changes to scripting interfaces and additional scripting examples.

Unresolved issues affecting the current release

The user should be aware of the following limitations and unresolved issues affecting ODTK as of the date of this release.

Unresolved Issues
Tracking No.	Description
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: AMD K8-based CPUs (Athlon 64, Sempron 64, Turion 64, etc.) AMD Phenom CPUs and newer
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: Edit the Style in question Right click on a field in question, choose "Format..." Go to the first tab and uncheck "Suppress" flag. Save report style into "My Documents/ODTK 6/Styles"
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.