General Information | What's New? | Transition Issues | Online Help Resources

ODTK 6.2.0 Release Notes

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.

Unless otherwise indicated, the information presented below reflects the state of ODTK as of version 6.2.0.

General information

This section includes system requirements and background information on ODTK 6.2.0.

System and disk space requirements

The following table sets out minimum and recommended system requirements for ODTK 6.2.0:

ODTK 6.2.0 System Requirements
Memory Disk Space Processor Operating System Browser
Minimum 256 MB 1 GB 800 MHz XP/XP Professional X64,
Windows Vista, Windows 7,
Windows Server 2003 and 2008
Internet Explorer 5.5
Recommended 512 MB 4 GB 2.0 GHz XP/XP Professional X64,
Windows Vista, Windows 7,
Windows Server 2003 and 2008
Internet Explorer 6.0

An ODTK 6.2.0 installation requires 200-300 MB of disk space. Running a typical scenario, such as the Sapphire demo scenario that accompanies ODTK 6.2.0 (3 satellites, 5 trackers x 3 days), takes about 600MB disk space for simulator, filter and smother runs. During such a run the memory footprint of ODTK 6.2.0 is slightly over 110Mb.

Compatibility with Windows Server 2005 and 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.

Background

ODTK 6.2.0 is built upon the same verified astrodynamics functions and coordinate conversions as STK and its modules. ODTK 6.2.0 is a matched set of modules, designed to provide orbit determination and analysis support for the entire life-cycle of satellite tracking systems. All phases of systems design can be supported with simulated tracking data, Monte Carlo analyses, and covariance analyses. ODTK 6.2.0 can produce results for satellite orbit parameters by processing one satellite at a time or multiple satellites simultaneously. ODTK is a stand-alone product, not an add-on module to STK.

The main products in this suite are a tracking data simulator, a state-of-the-art optimal sequential filter and a matched optimal sequential smoother. The sequential filter is designed to provide capabilities in support of routine satellite operations, including orbit determination, ephemeris prediction, and bias and maneuver/thruster calibration. The sequential filter produces a realistic covariance for system performance analyses, tasking optimization, and calculation of the probability of collision (in conjunction with STK/CAT). The optimal smoother provides high accuracy post-fit ephemerides in support of mission data products.

Particular care has been taken to ensure that regression tests to ODTK 5 are satisfied, that ODTK 5 scenarios will load and run in ODTK 6.2.0, and that ODTK 5 restart files will initialize in ODTK 6.2.0.

What's New in ODTK 6.2.0?

ODTK 6.2.0 is a maintenance release containing enhancements of interest to the space situational awareness community and tracking of unknown objects.

General

  • The Jacchia-Bowman 2008 atmospheric density model is now supported. Users should note that this model requires additional space weather indices beyond the usual flux data supplied by AGI.
  • STK binary ephemeris format is supported for both input and output. This reduces the size of the ephemeris files. Note that this format is only supported in STK 10 or later releases.
  • The GGM03C gravity model has been added.
  • An application level attribute ODTK.AppVersion was added to allow scripting clients to identify the ODTK version that they are connecting to.
  • Ephemeris files produced by the filter and smoother now use a nice clean ScenarioEpoch time as the reference. While it doesn’t change the overall ephemeris results, it’s easier to read and interpret the time tags when looking at a file by hand.

Satellite updates

The Satellite object has been enhanced to allow the following:

  • The solar radiation pressure (SRP) model terminology has been updated to use CR rather than CP to refer to the solar radiation pressure coefficient. This makes ODTK consistent with standard terminology used elsewhere in the industry and academia. Backwards compatibility code is in place to allow loading your existing scenarios and scripts. The standard report and graph styles shipped with ODTK have been updated appropriately. Users should review any custom styles they may have and update them. Please refer to the transition steps below for more details.
  • The drag and solar radiation pressure estimation options have been expanded to allow additive or relative terms to be estimated for each. Previously the SRP parameter (CR) that was estimated was additive and the drag parameter (β) was relative.  The SRP model also allows estimation of CrA/m. This is useful in cases where the satellite being tracked has an unknown area and mass.
  • Drag modeling may be included in the variational equations.
  • The integrator settings support a separate configuration for prediction (after the filter, smoother, or least squares runs). The standard integrator choices may be used, along with the addition of a new Gauss-Jackson integration method.

Least Squares

The Least Squares object has been enhanced to allow the following:

  • The user may now choose to use an a-priori covariance during the estimation. This allows you to constrain the state during the estimation process.
  • There is a new option to transfer the position and velocity covariance to the satellite when transferring the state. Because the least squares covariance is often optimistic (e.g. too small), you may optionally provide a multiplier for the position and velocity that will be used to inflate them when transferred.

Filter

The Filter object has been enhanced to allow the following:

  • A new option to compute global corrections to the Jacchia 1970 and Jacchia-Bowman 2008 atmospheric density models has been added. Updates may be computed via three formulations: as corrections to the nighttime minimum exospheric temperature, TC , and the inflection point temperature at 125 km altitude, TX , as correction to the global exospheric temperature T∞, or as direct relative corrections to the density, Δρ/ρ. Computed corrections can also be applied during orbit determination for satellites not used during the determination of the temperature corrections.
  • A new option for the Filter and Simulator to detect and use updated object settings for estimated stochastic parameters in restart mode. This new option provides an alternative to using the StochasticModelUpdates lists on the Filter or Simulator object to specify updates to stochastic model settings or nominal parameter values.
  • A new option to allow an external file containing sensor biases to be used during estimation rather than estimating the biases directly.

Simulator

The Simulator object has been enhanced to add new options to the interval files used with the custom tracking intervals. These include options for specifying the tracker via a tracking strand and adding a tracking granularity delta time.

Measurement Models

Trackers supporting optical measurements such as right ascension and declination (or their space-based equivalents) now support a TEME of Zero hour and TEME of Jan 0 as optical frame options.

GPS Receivers

Ground-based GPS receivers can now specify their antenna offsets in the Height, East, North convention as used in SINEX files from the IGS.

Static Product Builder

Ephemeris files can now be used as inputs for report and graph styles that use position and velocity information.

Default parameters

The default parameters for several objects in ODTK have been updated to better represent operationally relevant values. The changes only affect new objects that are created in your scenario. Any existing objects that are loaded as part of a saved scenario will continue to have the same values as before. Users with scripts controlling ODTK should review their scripts to see if the script was relying on the previous default values. If so, you should update your script to either explicitly set the properties to the desired value or confirm that the new values have no impact.

On the satellite object:

	ForceModel.Gravity.ThirdBodies.UseInVariationalEquations = true
	ForceModel.Drag.UseInVariationalEquations = true
	ForceModel.SolarPressure.SunPosMethod = Apparent
	ForceModel.SolarPressure.UseInVariationalEquations = true
	PropagatorControls.IntegrationMethod = RKF 7(8)
	PropagatorControls.StepSize.StepControlMethod = Relative Error

These changes provide a better default force model and integrator configuration.

On the Filter and Smoother objects:

	Output.DataArchive.SaveCrossCorrelations = false

These changes reduce the size of the files contained in the filrun and smtrun folders produced by the filter and smoother.

On the Smoother object:

	ProcessControl.StateTransitionMode = Linear

This change defaults the fixed interval smoother to use the Linear transition mode (vs. the Nonlinear). Testing at AGI has shown the Linear mode to produce slightly more accurate results in the period immediately preceding a tracking data pass.

Version Changes in Tracking Data Interface

The following table shows changes in the tracking data interface between ODTK 5 and the current version:

ODTK 5  ODTK 6 
ODTK.Application ODTK.Application
ODTK5.Application ODTK6.Application
   
AgAttrAutomation5.AgAttrBuilder AgAttrAutomation6.AgAttrBuilder
   
AgMach10_5.AgODObsSet AgMach10_6.AgODObsSet
AgMach10_5.AgODObsSetCollection AgMach10_6.AgODObsSetCollection
AgMach10_5.AgODTrackingIDList AgMach10_6.AgODTrackingIDList
AgMach10_5.AgODRealList AgMach10_6.AgODRealList
AgMach10_5.OLEDBDataSource AgMach10_6.OLEDBDataSource
   
AgOdtkPlugin5.AgOdtkPluginSite AgOdtkPlugin6.AgOdtkPluginSite
   
IAgODProvideTrackingData5.AgODGenericObs IAgODProvideTrackingData6.AgODGenericObs
IAgODProvideTrackingData5.AgODProvideB3TrackingData IAgODProvideTrackingData6.AgODProvideB3TrackingData
IAgODProvideTrackingData5.AgODProvideCobTrackingData IAgODProvideTrackingData6.AgODProvideCobTrackingData
  IAgODProvideTrackingData6.AgODProvideDSNTrackingData
  IAgODProvideTrackingData6.AgODProvideEphemerisTrackingData
IAgODProvideTrackingData5.AgODProvideGenericTrackingData IAgODProvideTrackingData6.AgODProvideGenericTrackingData
IAgODProvideTrackingData5.AgODProvideGeoLocTrackingData IAgODProvideTrackingData6.AgODProvideGeoLocTrackingData
IAgODProvideTrackingData5.AgODProvideGeoscTrackingData IAgODProvideTrackingData6.AgODProvideGeoscTrackingData
IAgODProvideTrackingData5.AgODProvideGPSNavTrackingData IAgODProvideTrackingData6.AgODProvideGPSNavTrackingData
IAgODProvideTrackingData5.AgODProvideILRSTrackingData IAgODProvideTrackingData6.AgODProvideILRSTrackingData
IAgODProvideTrackingData5.AgODProvideLanceTrackingData IAgODProvideTrackingData6.AgODProvideLanceTrackingData
  IAgODProvideTrackingData6.AgODProvideMDPTrackingData
  IAgODProvideTrackingData6.AgODProvideOASYSTrackingData
IAgODProvideTrackingData5.AgODProvideRAWPRTrackingData IAgODProvideTrackingData6.AgODProvideRAWPRTrackingData
IAgODProvideTrackingData5.AgODProvideRINEXTrackingData IAgODProvideTrackingData6.AgODProvideRINEXTrackingData
IAgODProvideTrackingData5.AgODProvideUTDFTrackingData IAgODProvideTrackingData6.AgODProvideUTDFTrackingData
   
AgHtmlServer.AgHtmlServerInitOD50 AgHTMLServerODTK6.HTMLServer
   
HTML Utilities that are run inside ODTK and use HTML Server should instantiate it with:
   window.external.CreateObject("AGI HTML Server")

Capabilities Added and Issues Resolved From the Prior Release

The following table identifies limitations and issues that have been resolved in the current release, as well as new capabilities and improvements that have been added:

For convenience, this table includes all enhancements and resolved issues believed to be significant, including some that are discussed in more detail above.

New Capabilities and Resolved Issues in ODTK 6.2.0
Tracking No. Description
38093 The satellite properties page will now update (if displayed) when the user is using the Initial State HTML utility and they transfer a state into the satellite.
48392 The method of computing transitional partials for force model parameters has been updated to follow the satellite setting, OrbitErrorTransitionMethod. The options for this setting are Variational Equations and Numerical. In prior versions of ODTK, the transitional partials for force model parameters were always computed using an Encke technique. The transitional partials are used in the construction of the state error transition matrix. This change will result in slightly different numerical results from estimation processes, though qualitative behavior should not be affected. An environment varaible, "AGI_USE_OLD_FM_TRANS_PARTIALS", has been provided to restore the prior behavior for the purpose of regression testing.
53269 The capability to specify independent setting for the numerical integration method used for ephemeris computations during prediction phases has been added. The main benefit comes through the addition of the computationally efficient Gauss-Jackson integrator to the list of available options for ephemeris prediction.
59542 The capability has been added to difference two ephemeris (.e and/or .oem) files using the CreateDifference scenario function or State Difference utility. The capability has also been added to load an ephemeris file into the SPB to dispaly report/graphs using the SatelliteState table.
60336 Added the ability to read and write the AGI binary ephemeris file format (*.be) anywhere that ODTK currently supports ephemeris files (*.e).
60910 The ability to use apriori covariance during least squares estimation has been added. This feature allows apriori knowledge to be used to better constrain the least squares solution which is helpful in cases where few measurements exist.

The ability to combine measurement white noise and measurement bias uncertainty together for the purpose of least squares estimation has been added.

And the ability to transfer position/velocity covariance from a least squares solution to the satellite object has been added.
63440 The option to output the VLS ephemeris on a uniform grid has been removed since it does not apply to the VLS. The VLS will output its ephemeris on the VLS grid.
63804 A problem was fixed where the filter might crash while running if there was no Earth Orientation Parameters (EOP) file.
63844 Gooding IOD has been modified to account for the tracker optical reference frame when computing the (ICRF) inertial pointing vector from RA & Dec measurements.
63995 An issue was fixed where invalid data in the RINEX Observation file Epoch Record could cause ODTK to abort when reporting on that file.
64217 The scripting interface now supports an ItemExists method that allows users to test if an object exists before attempting to access it.
66391 The latest GRACE Gravity Model, GGM03C, has been added to ODTK.
67050

Symbology for the solar radiation pressure coefficient has been changed from Cp to Cr.

The estimation of corrections to the spherical solar pressure and spherical drag model parameters has been standardized to allow three options for estimation solve-fors. Estimation processes may now solve for delta Cx, delta CxA/M or (delta CxA/M) / CxA/M.

Elements in the ODTK data provider tables have been added to match the selection's available estimation parameters. Historical names are still available so that existing export and graph styles will still function properly. Existing report styles that use affected database tables will work properly after the Verify Database operation is performed.

67647 The ODTK filter, smoother, and least squares ephemeris ScenarioEpoch time is now on an integer second. For processes not starting on an integer second this results in the first ephemeris entry having a non-zero entry. Subsequent time tags will be on a whole second boundary.
69190 A fix was made to the Nav Solution IOD so that it no longer requires a GPS Constellation object to be present in the scenario.
69332 The Load and Import buttons were removed from the CustomDataEditing.Schedule dialog box as they were not used.
69519 A new attribute has been added to expose the ODTK version.
69547 The capability to simulate "Eph Pos" and "Eph Vel" measurements and output them to a .gobs file has been added to ODTK.
69646 Under certain circumstances the Gooding IOD method would try to write to a non-existent file and pop up an error dialog and subsequently not complete the IOD. This has been corrected.
70151 An issue that would cause the user to get a bogus "zero thrust magnitude sigma error" when estimating thrust magnitude for a finitie maneuver was fixed.
70292 An option has been added for the Filter and Simulator to detect and use updated object settings for estimated stochastic parameters in restart mode. This new option provides an alternative to using the StochasticModelUpdates lists on the Filter or Simulator object to specify updates to stochastic model settings or nominal parameter values.
70323 All HTML utilities shipped with ODTK now set locale to "English - United States" so that floating point numbers are compatible with ODTK and STK automation interfaces.

If ODTK users write custom scripts on the computer with default encoding other than "en-us" they should follow this template:

...
  SetLocale(1033)
  ...
  set fac = ODTK.Scenario(0).TrackingSystem("TrackingSystem1").Facility("Facility1")
  set Lat = fac.GeodeticLocation.Latitude.GetIn("deg")
  MsgBox "Lat = " + cstr(Lat)
...
70346 The GPSCatalog.txt file was updated for the new GPS satellite launched in Oct 2012.
70365 The option to compute corrections to the Jacchia 1970 and Jacchia-Bowman 2008 atmospheric density models has been added. Updates may be computed via three formulations:
  • as corrections to the nighttime minimum exospheric temperature, Tc , and the inflection point temperature at 125 km altitude, Tx
  • as correction to the global exospheric temperature T infinity
  • or as direct relative corrections to the density, delta Rho / Rho.
Computed corrections can also be applied during OD for satellites not used during the determination of the temperature corrections.
70466 An issue wherein the Append option for .simrun did not provide the correct file start time was fixed.
70467 Corrections were made in displaying and applying the Simulator.Restart.StochasticModelUpdates.VasicekList.
70612 The GEO IOD using Least Squares capability has been updated to provide improved initial guesses when angle data is available.
70695 An error in the use of custom propagator settings associated with finite maneuvers has been corrected. The error affected the selection of integration time steps when the PropagatorControls for a finite maneuver were enabled and the propagator StepControlMethod was set to Fixed. Under these conditions, the EccentricityThreshold and TrueAnomaly step size from the satellite propagator controls were used during integration across the finite maneuver instead of the related settings from the finite maneuver definition. This could result in improper step size selection during integration across the maneuver if the satellite propagator controls and maneuver propagator controls had different settings.
70720 New options have been added to the Interval File to support Simulator CustomTrackingIntervals. These include options for specifying the tracker via a tracking strand and adding a tracking granularity delta time.
70819 An error in the deep space light time delay compuation was corrected to avoid the double application of the TT to TDB transformation during the access to planetary ephemeris in one side of the two way light time delay computation. This change affects the DSN Seq Rng, DSN TCP and DSN 3W TCP measurement models. The main effect on the range models is a correction in the computed range values that can vary between several meters for a lunar orbiter to about a kilometer for spacecraft in orbit about Mercury. Since the error affected the time used to request the location of the planet about which the spacecraft is orbiting, the error was proportional to the velocity of the planet projected onto the direction between the tracking station and the planet. This change also reduced the noise in the LTD computation due to improved handling of time which reduced the computational noise in TCP measurements.
70848 An issue was fixed to allow the Smoother to generate a predicted ephemeris without also requiring the "during process" ephemeris generation.
70926 A correction was made to LS to not always output drag plugin parameters in the LS States report.
70953 ODTK no longer requires the user to have admin rights on Windows 7 in order to launch the Data Update Utility from the Utilities menu. Users running under Windows Vista will still need admin rights.
71145 The ILRS tracking systems have been updated to reflect the latest list of active and inactive stations from the ILRS.
71146 An application crash during the transfer of LS results to a satellite has been fixed. The crash was limited to the case where a scenario has been reloaded and an LS transfer to satellite operation is attempted without running LS and the LS transfer is configured to include covariance information. In this case, the LS covariance matrix is not available since it is not saved and loaded with the scenario. A warning is now issued to inform the user that covariance has not been transfered and that LS needs to be rerun in order to allow for covariance transfer.
71332 The TEME of Jan 0 and TEME of UTC 00:00 reference frames have been added as options for the processing of optical observations.
71510 A fix was made to the GPS constellation object to prevent ODTK from applying ionospheric corrections to GPS measurements when the IonosphereModel is set to "None".
71634 A fix was made to correct GPS Reciever bias processing. In addition the ability to estimate GPS receiver biases was added. The default setting is to not estimate.
71746 An issue was fixed to produce histogram data for GroundTDOA/GroundFDOA observation types.
71769 A minor error in the way spherical solar pressure state corrections were applied during orbit propagation has been corrected. The error was limited to the case where the diffuse reflection model had been selected. This correction results in small numerical differences with the prior version.
71791 The option to add offsets in the SINEX {North, East, Up] convention to GPS ground based receivers was added for antennas attached to GPS ground based receivers.
71993 The Jacchia-Bowman 2008 atmospheric density model has been added as an option for use in modeling the effect of drag on Earth orbiting space objects. The Jacchia-Bowman 2008 atmospheric density model requires additional solar and geomagnetic activity indices which are available at http://sol.spacenvironment.net/~JB2008/indices.html.
72011 A fix was made to correctly add into the measurement model a transponder or retroflector a constant bias, with the error occuring when the bias was non-zero, the EstimateBias property was set to false, and the stochastic model type was to set to either Vasicek or RandomWalk.
72097 An error in the use of atmospheric pressure from the Consolidated Laser Ranging Data Format (CRD) has been corrected. The atmospheric pressure, specified in CRD format in units of mBar, was not properly converted to Pascals prior to use in ODTK. The result of the error was that the computed tropospheric delay was too small.
72306 A difference in the tolerance used in time comparisons between the filter and the smoother which could result in mis-ordered smoother ephemeris output in the case where a maneuver start or stop time coincided with a measurement time and the common epoch was at a non-integer second has been corrected.
72431 An issue was to fixed to allow the GPS NavSolution IOD to run using a YUMA or SEM ephemeris.
72746 The State File to the SP3 utility was modified to handle PRNs > 32 up to 99. A similar change was made to other SP3 related utilites. The GPS Catalog was modified to handle PRNs up to 99.
72868 An error was fixed to correctly update the time and correctly solve for the first clock state parameter when the state included just clock parameters (or a clock phase state was the first state parameter).
72943 An error in state comparisons involving the stochastic definition of finite maneuvers performed during smoothing over multiple (.rough) files has been corrected. The error, which could occur when a state immediately preceeding the finite maneuver state in state space was either dropped or added resulted in ODTK crashing during the smoothing process.

Transition issues

This section presents transition issues of importance to the user, including operational tips and caveats to help smooth the path to successful use of ODTK, as well as a list of limitations and unresolved issues of which the user should be made aware.

Transition matters

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.2.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.2.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 Guide 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.
26002 It is not possible to Export the HTML generated by the ViewScenario.htm utility to Microsoft Excel, even though the option is offered.
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 can not 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 runfiles from ODTK to avoid disk space issues.
38689 When attempting to integrate an orbit in low altitudes, such as < 90 km, the integrator may perform poorly and hang. This problem may be overcome by changing the integration method or integrator settings.
42045 The SB range measurements ignore the optional tracker vector information. If you have a B3 file with type 8 or 9 measurements that are supplying the tracker position then you will get bad answers if you have your tracker satellite set up with its ephemeris source set to " Meas File Embedded Trajectory ".
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

Online Help resources

The current version of ODTK is shipped with the following online help resources:

The ODTK Help system

The ODTK Help system appears in the Microsoft HTML Help Viewer, which uses components of the Microsoft Internet Explorer to display help topics and navigational tools. The latter are accessible from the following tabs:

  • Contents - Click on the book and page icons to find the topic of interest.
  • Index - Scroll down the list or begin typing the name of the index item in the text box. When the item you are seeking appears in the list, double-click it or highlight it and click the Display button. If the item is found on more than one help page, a window listing the applicable pages will display.
  • Search - Type in the word or phrase for which you wish to search. To specify an exact phrase, enclose it in double quotes; otherwise, any page containing all of the words in the phrase (not necessarily contiguous) will be listed. After typing in the search term, either press the Enter key or click the List Topics button.
  • Favorites - This tab lets you bookmark help topics to which you might want to refer to frequently. Clicking the Add button places the name of the currently displayed help topic in the list. To delete a topic from the list, select it and click the Remove button.

Context-sensitive Help

F1 Help for OD Attributes

To display context-sensitive help for a property of an OD object, select it in the Object Properties window for the object and click the F1 key.

Help Buttons for Report and Graph Windows

Help buttons are available for the Static Product Builder, the Dynamic Product Selector, the Graph Designer and the Report Designer. Click these buttons for context sensitive help on the functionality in question.

Printable (PDF) Documents

Several printable (PDF) documents accompany this version of ODTK, including a set of tutorials (Getting Started with ODTK), a scripting guide, and documents explaining the mathematical and scientific background of ODTK. To access these documents, go to the manuals page.