What's New | System Requirements | Resolved Issues | Transition Issues | Known Issues | Tracking Data Interface Version Changes | Background Information | Online Help Resources |
ODTK 6.4.2 Release Notes
What's New in ODTK 6.4.2?
ODTK 6.4.2 is primarily a maintenance release with a couple of small new features.
GNSS
The various GNSS constellation catalog files have been updated to reflect the latest launches and constellation changes (note: these can also be obtained online via the Data Update Utility).
Added the ability to estimate an antenna offset when processing NAVSOL measurements.
The NAVSOL tracking data format now allows you to specify component based measurement sigmas. This is useful if these are available from your GNSS receiver.
Facility
Added new report and graph styles to display an ellipse representing a facility location estimate.
Least Squares
The least squares object can now solve for a transponder bias.
Maneuvers
Maneuvers using acceleration history files can now artificially lengthen or shorten the maneuver without editing the file directly.
Measurement editing
The Custom Data Editing rules on the Filter and Least Squares objects now allows a description to be entered for each rule.
Filter
Vasicek model parameters can now be updated without causing a complete drop/add of the filter state in the restart record. This allows the end user to preserve the cross-correlations.
Tracking data
We now support the TDRS CCSDS XML tracking data format.
Gravity fields
We've added support for the Mars MGM2011 gravity field.
ODTK 6.4.2 Capabilities and resolved issues
| New Capabilities and Resolved Issues in ODTK 6.4.2 | |
|---|---|
| Tracking No. | Description |
| 57939 | The capability was added for LS to solve for transponder bias. This includes capability to optionally solve for the transponder bias or include the transponder bias as a consider state. The option to include the transponder apriori covariance was also added. |
| 78896 | The CCSDS Tracking Data Message (TDM) reader now supports XML formatted TDM files. Support for the TDRSS SGSS-CCSDS update to the TDM features has been added. |
| 83919 | The atmospheric density plugin point released in ODTK 6.4.1 has been extended to allow the estimation of parameters within the atmospheric density model. Parameter corrections estimated in one (typically multi-satellite) run may also be used as inputs to subsequent (typically single satellite) runs. |
| 84363 | The Vasicek sequence uses a couple of settings to control the uncertainty in the long term mean: a minimum uncertainty ("Error Threshold") and a process noise bump ("PNStep") used to enforce that minimum. The capability to modify these settings from a restart without causing a state drop/add has been added. These settings are modified in the restart state whenever the corresponding values are modified in the object settings and are modified without regard to the setting of the Filter.Restart.Stochastic.ModelUpdate.Source flag. |
| 84455 | In previous releases, all Java related files were located in the "JavaDevKit" sub-directory. Going forward, all Java files will be located in the Bin directory. This was done to maintain consistency between Windows and Linux builds. |
| 85377 | The capability was added to process GPS measurements tagged in the "raw" receiving clock time (as opposed to GPS system time). |
| 86765 | GPS antenna locations can now be estimated using navigation solution measurements. |
| 87318 | A units error was corrected in the Average Transponder Bias report style. |
System requirements
This section includes ODTK system requirements.
Supported Operating Systems
- Windows Vista 32-bit and 64-bit
- Windows 7 32-bit and 64-bit
- Windows Server 2008
- Starting with version 6.3.2, ODTK is not supported on Windows XP.
- ODTK runs as a 32-bit application in a 64-bit Windows environment. Code samples are compiled for use in Visual Studio 2008 and 2010.
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 |
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:
|
| 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. |