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

ODTK 5 Release Notes

Including Changes through ODTK 5.0.3

These release notes contain information on system and disk space requirements for installing and running ODTK; information on new capabilities and features - including but not limited to GPS Satellite Orbit and Clock Estimation - 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 5. Changes introduced in ODTK 5.0.1, ODTK 5.0.2 and ODTK 5.0.3 are described in a separate section.

General information

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

System and disk space requirements

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

ODTK 5 System Requirements
	Memory	Disk Space	Processor
Minimum	256 MB	1 GB	800 MHz
Recommended	512 MB	4 GB	2.0 GHz

An ODTK 5 installation requires 200-300 MB of disk space. Running a typical scenario, such as the Sapphire demo scenario that accompanies ODTK 5 (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 5 is slightly over 110Mb.

Background

ODTK 5 is built upon the same verified astrodynamics functions and coordinate conversions as STK and its modules. ODTK 5 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 5 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 4.0 are satisfied, that ODTK 4 scenarios will load and run in ODTK 5, and that ODTK 4 restart files will initialize in ODTK 5.

What's New in ODTK 5?

The sections below describe the following new features and capabilities of ODTK:

• GPS Satellite Orbit and Clock Estimation
• Force Model Features
• SV Antenna Location Modeling and Estimation
• TDOA & FDOA Orbit Determination
• Trackers vs. Facilities
• Restructured Filter Restart File
• Restartable Simulator
• Runtime & Storage Efficiency
• Reports & Graphs
• Scripting Support
• LaunchPad
• New Utilities

GPS Satellite Orbit and Clock Estimation

ODTK has been updated to perform orbit and clock estimation of GPS satellites through processing of pseudo-range and carrier phase measurements from ground GPS receivers. A summary of features associated with this capability is given below. See ODTK 5 Applied to GPS Satellite Orbits and Clocks for a more detailed description of this capability, including how ODTK has been specifically designed to support GPS satellite operations.

GPS Satellite State Estimation

ODTK can now estimate GPS satellite orbit, clock and solar pressure states. Optional modes of estimating GPS states are also available to allow the user to estimate clocks while using reference orbits, or to estimate orbits while using reference clocks.

Ground GPS Receiver Observation Data

The capability to process pseudo-range and carrier phase measurements from a ground GPS receiver has been added. This includes the ability to process (for both pseudo-range and phase) single frequency measurements, dual frequency measurements, single differenced measurements (for either single frequency or dual frequency), and double difference measurements (for either single frequency or dual frequency).

Two and Three-State Clock Modeling

An optional three-state clock model had been added to the filter to solve for time-varying estimates of clock phase, frequency, and frequency drift. The option to use the ODTK 4 two-state clock model has been preserved. These models support both the GPS satellite clock and the GPS receiver clock.

Two-State Solar Pressure Models

Two-state solar pressure models have been added for GPS Satellites. These include the JPL models for Block IIA, and IIR, and the Legacy models for II, IIA, and IIR.

GYM95 Yaw Model

The GYM 95 yaw model for Block IIA satellites during eclipse has been added.

Troposphere Modeling and State Estimation

Troposphere modeling has been upgraded to support processing of the ground GPS measurements from the GPS Monitor Stations. This includes the addition of the Saastamoinen hydrostatic model with the Niell mapping function. This model can be used when meterological data (via RINEX MET files) is available. Troposphere modeling also includes the new capability to estimate the tropospheric zenith scale factor for any of the ODTK tropospheric models.

Mutiple Facility Antennas

Support for multiple GPS antennas per facility has been added.

Single Partition Solution

The ODTK filter and smoother have been designed to allow all states to "fit" and run within a single partition solution.

Separate Partition for Offline Satellite

Occasionally, notice is given that one or more of the GPS constellation satellites must go offline due to technical difficulties with those satellites. ODTK can now take a GPS constellation satellite offline by not allowing its reduced measurements to affect other estimated components of the GPS network, such as monitoring station location and their clock offsets. This is done by creating a separate filter partition that maintains the orbit for the offline satellite(s). This partition relies on monitor-station-clock and troposphere estimates based on the other online GPS constellation satellites.

Composite Clock Model

A Composite Clock model can be used to define GPS Time. The user can select which clocks to include in the Composite Clock.

Clock Steering

A clock steering algorithm using a damped bang-bang controller has been implemented to steer GPS Time so as to maintain a constant offset to UTC Time.

Clock Resets

A capability has been added to recover from clock events that trigger a reset to any combination of the clock {phase, frequency, aging}. This allows the user to reset at a restart time the estimates and covariance sigmas of the affected clock and continue with the filter without having to reinitialize it entirely.

Units for Clock Reports & Graphs

All of the reports and graphs for Clock behavior have been changed so that reported values are in the same units as the corresponding GUI attributes. This change eliminates some user-friendly units, like microseconds per day, but eliminates the need for offline unit conversions to construct inputs from outputs.

Inputs and Outputs in GPS Time

Options have been added to specify all inputs and outputs in GPS Time or in UTC Time or in any combination.

Buffers to Allow Extrapolation in SP3 Files

The GPSConstellation object now provides BufferBeforeFileStart and BufferAfterFileStop attributes that allow you to define buffers at either end of an SP3 file for extrapolation. See the help page on the GPSConstellation object for further details.

Force Model features

Lunar eclipsing of the satellite has been added. This provides the option to calculate when the satellite is in the lunar shadow, and to account for the change in solar pressure if it is in the lunar shadow.

SV antenna location modeling and estimation

Given a GPS receiver on a satellite, a GPS antenna on the body, and an attitude model or file, ODTK can now estimate the location of the antenna in body axes. The antenna model includes the location of the center of mass and of the antenna in body axes.

TDOA & FDOA orbit determination

The capability has been added to simulate and process time difference of arrival (TDOA) and frequency difference of arrival (FDOA) data types from a single emission source. Data types include TDOA and FDOA, single-differenced TDOA and FDOA, and Space Based TDOA and FDOA. To support this capability, a new Emitter subobject can be attached to a Facility object. In addition, Satellite objects have been modified to allow multiple band-specific relay transponders.

Trackers versus Facilities

This release distinguishes trackers and facilities for the first time. This should be kept in mind when data delimiting for reports and graphs (and may impact user scripts that delimit graphs and reports). For traditional radars, ground-based optical systems and SGLS-type systems, the correct delimiter is the tracker. A tracker will generate tracking data; thus, a GPS receiver attached to a facility is the tracker. However if the facility location or tropospheric scale is estimated, these are states assigned to the facility.

Restructured Filter Restart file

The Restart file is completely redesigned to improve reliability. This design includes a separate file for each record, with a directory of pointers to the files. A Restart folder appears as a subfolder to a scenario home folder. Backward compatibility code to convert ODTK 4 restart files to ODTK 5 form has been added.

Restartable Simulator

The simulator now has a Restart capability similar to that of the filter, which allows for a continuation of the simulation that is compatible with the final state of the previous simulation. The simulator Restart uses the same (new) Restart file structure as the filter.

Runtime and storage efficiency

Several changes have been made to speed up processing and reduce data storage requirements. These include:

• There is a new filter measurement update option to process multiple simultaneous measurements in a single "Simultaneous" update.
• There is a new filter option to omit satellite-to-satellite cross-correlations from the runfile.
• All matrix processing is performed in vector arrays on a chip using Intel’s MKL library.
• There is a general speedup in reports and graphs.

Reports and graphs

Several improvements have been made to static reports and graphs. These include:

• Global control that allows all report and graph time scales to be generated either in UTCG or in GPSG.
• New reports and graphs for new state parameters (clocks, solar pressure, and tropospheric zenith scale) as well as URE (User Range Error).
• New histograms:
• Histogram Summary - accumulates all data into one histogram.
• Histogram Descriptive - provides tool tip descriptions for multiple histograms on one graph.
• Finite maneuver graphs and reports in units of thrust.
• The AGI logo now optional in the graph style editor.
• General speedup.
• Added internal checks to make reports and graphs more robust.

Scripting support

A number of changes have been made to provide better support for scripting with ODTK.

Improved Attribute Path

Right-click the mouse over an attribute name in the Object Properties window, and select the Copy Attribute Path option to obtain a "fool-proof" attribute path to use in scripting, including the enclosure of object names in quotes. This is the recommended syntax for scripting ODTK objects, since it uniquely identifies an object and is independent of syntax rules of various scripting languages. See the help page for more details.

List Manipulation

InsertByName and EraseByName have been added to simplify manipulation of objects in lists.

LaunchPad

The Start and Welcome pages have been replaced by the ODTK Launch Pad, which is a single HTML-based window that displays within ODTK and is used for organizing and accessing information and files in the ODTK environment.

New Utilities

Several new utilities have been added. These include:

• Generate double differenced GPS measurements.
• Generate a simrun file from a SP3 file, where SP3 refers to a standard NGS GPS orbital (and clock) file format.
• Generate an SP3 file from filrun, smtrun, etc.
• Generate NAVSOL measurements from an STK *.e file.
• Clear all graphs in the Static Product Builder.
• Clear all reports and graphs in the Static Product Builder.

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
Tracking No.	Description
05801	Histogram information from multiple filter runs can now be concatenated through the normal procedure of specifying multiple filter output files as inputs in the static product builder.
07098	The observation partials for two way range and Doppler have been improved for deep space applications to include the effects of orbit transition over the light time delay interval.
07122	GPS Dynamic Reports now include Single Differenced (SD) measurements.
11118	Data limiting in support of reports and graphs for singly differenced GPS tracking data will work if the default naming convention for GPS satellites is followed, e.g. PRNxx. If the naming convention is not followed then data limiting will not work.
11467	TDRSS observations are now deweighted based on the covariance associated with the TDRSS satellite ephemeris for cases where the TDRSS satellites are not estimated simultaneously with the user satellites . The covariance information may be specified as time varying in the ephemeris file or as a constant uncertainty in radial, in-track and cross-track coordinates.
12253	A new troposphere model has been added consisting of the the Saastamoinen a priori hydrostatic model combined with the Neil NMF mapping function. The Neil NMF mapping function introduces a tropospheric state parameter to solve for the zenith delay, which is then mapped to lower elevations.
12441	Previously ODTK would ignore the covariance in a Reference Ephemeris during the Filter Measurement Update process if the data type was TDRS. Beginning with version 5.0, all measurement types will use the covariance information in a Reference Ephemeris file to provide additional measurement deweighting, including TDRS, SB tracking data, and various TDOA & FDOA measurement types.
12442	The option to specify a constant uncertainty in RIC coordinates for satellites using reference ephemerides without covariance information has been added.
12593	The capability to update the satellite mass in the restart file has been added.
13423	The minimum grazing altitude constraint associated with TDRSS relay satellites is now considered during the simulation and processing of 4 Legged Range, 5 Legged Doppler and 3 Legged Doppler measurements. Previously, a hard coded value of 64 km was used.
13492	The simulator now has a restart capability.
14323	An option was added to ODTK Static Graphs to turn the AGI logo on or off.
15446	The OnScenarioSaved attribute is not necessary and has been removed.
15888	Start and stop times for flux file are now displayed in the object properties window. The stop times reflect the end of observed data.
15894	The Simulated Tracker Initial State report style has been revised with the addition of a column for bias units.
16147	If a user specifies a measurement file type that does not support all data types, the Simulator will create additional measurement files in formats that do support the additional data types. In previous versions of ODTK the new simulated measurement files would appear in a different directory than the user specified file. Beginning with this release all simulated measurement files will appear in the same directory.
16178	New operators have been exposed to simplify arithmetic operations when scripting time. The operations exposed allow AddTime, SubtractTime, SubtractDate, Equals, GreaterThan, LessThan, Inequality, GreaterThanOrEqual, and LessThanOrEqual. The operators allow such operations as:    sim.StopTime = sim.StartTime.AddTime( ODTK.NewQuantity(5,"sec") )    set duration = sim.StopTime.SubtractDate( sim.StartTime )    alert "Duration in seconds: " & duration.GetIn("sec")    if sim.StartTime.Equals(sim.StopTime)       then alert "Oops..."    end if
16427	An error in the tropospheric refraction model was corrected. The user may notice changes in residuals for low elevation data measurements.
17200	The capability for the user to turn on a debug switch in the filter and smoother to dump covariance eigenvalues has been added.
17207	These reports (Finite Maneuver History and Finite Maneuver Summary) now present maneuver information in chronological order, sorted on ignition times for each finite maneuver. The estimated maneuver data in these reports were also changed from floating point to scientific notation to increase precision when modeling small thrusters.
17244	A new optional state estimate has been added for a correction to the a priori zenith tropospheric delay.
17245	GPS Satellite objects can now be added under the GPS Constellation object. This allows GPS SV orbit and clock parameters to be estimated by the filter. It also allows for individual setting of all parameters in the GPS Satellite object. If the GPS SV orbit and clock come from a reference source file, then the GPS Satellite objects do not need to be added to the GPS Constellation object per the ODTK 4, 4.1, and 4.1.2 architecture.
17250	Ground-based GPS receivers have been added as subobjects to a Facility. They support ground based GPS pseudo-range and phase tracking of the GPS satellites in the GPS Constellation.
17728	A checkbox lets you hide the X-axis labels in a graph, but the X-axis title cannot be hidden in this way. Instead, you must delete the title.
17973	Velocity ("V") records are now included in the concatenated SP3 file by the ConcatenateSp3Files utility if they are included in the original files to be concatenated.
17976	If using the Ephemeris Extraction tool to get ephemeris from a simulator run file, there will now be double points at maneuver times.
18118	The Initial State tool was reworked to be more intuitive to the user.
18311	Tracking data provider documentation was updated with detailed descriptions and examples for setting parameters in the observation sets.
18368	If you load a data products list and then save the scenario and close it, the data products list will be reloaded automatically when you re-open the scenario if (1) the .dpl file has the same name as the scenario (i.e. *.dpl) , (2) the .dpl file is in the \Styles directory, and (3) the Static Product Builder is open. The latter condition means that if you exit ODTK and re-start it, the default workbook must display the Static Product Builder in order for the data product list to reload automatically when you open the scenario.
18388	A new capability to scale the residuals in a dynamic graph is now available. A new keyword has been added called YAxisMultiplier, which can be used to change the YAxis scale (e.g. from degrees to arcsec). For example, change   <Scale Recalc="False" Min="-0.20" Max="0.20" Step="0.05"></Scale> to   <Scale Recalc="False" Min="-20" Max="20" Step="5" YAxisMultiplier="3600"></Scale>
18395	The simulator can now generate predicted ephemeris at the end of the run.
18513	ODTK script writers may now insert an object directly into the tracker list: ODTK.Scenario1.Filter1.TrackerList.insert(ODTK.Scenario1.TrackingSystem1.Facility1) or ODTK.Scenario1.Filter1.TrackerList.insert(ODTK.Scenario1.TrackingSystem1.Facility("Facility1") )
18541	Usability enhancement: The ODTK Oject Browser now supports Ctrl+C and Ctrl+V shortcuts when renaming an object.
18544	A new tool to extract and construct SP3 from the State History file is available. Note that the SP3 grid must intersect the StateFile Time Grid. Thus, to guarentee output on the nominal 15 min SP3 grid, the user should select a process noise time grid of 1 minute (instead of of the nominal 2 minute grid).
19113	The use of the Intel® Math Kernel Library (MKL) has improved ODTK performance. The improvement is obvious for a large scenario. Using MKL ODTK is almost twice as fast for a scenario with a large state space (> 300 states, which is typical for scenarios containing a GPS contellation).
19283	The user can now copy values from the Object Properties window even when read-only.
19719	The conversion routine between Ap and Kp geomagnetic flux values has been updated to better preserve the known table of equivalences. See Vallado, David A. and T.S. Kelso, "Using EOP and Solar Weather Data for Real-time Operations," AAS 05-406 (1985), available in PDF format from AGI's Center for Space Standards and Innovation (CSSI).
20604	New satellite attributes, FilterEvents.TrackingStrand and FilterEvents.MeasurementType, are available in scripts.
20956	Changes were made to speed up the filter start following state size changes.
21028 23232	The State Transfer Tool Wizard has been eliminated in this release, since capability was superceded by the Flexible State Space options defined for ODTK 4.0.
21342	A problem in which units were displayed in "hours" instead of "minutes" in Plugin Point scripts and the Message Viewer has been corrected.
22005	New residual edit codes have been added.
22221	Numerically invalid values such as -1#J or 1#IND or 1#INF are no longer shown on dynamic reports. If the value is invalid, the field is now blank.
22911	The summary report for finite and instant manuevers now respects data limiting based on satellite names.
22965	Resolved issue where the simulator would abort if the HPOP integrator threw an exception for the satellite being below perigee limit or atmosphere cutoff.
23062	All of the reports and graphs for Clock behavior have been changed so that reported values are in the same units as the corresponding GUI attributes. This change eliminates some user-friendly units, such as microseconds per day, but eliminates the need for offline units conversions to construct inputs from outputs.
23067	In earlier versions of ODTK when there were multiple histograms per plot, then it was difficult to tell the relationship between the graphs, the satellites, the trackers, and the number of samples. A new HistogramDescriptive graph style has been added to provide that correlation. A small triangle will appear to the right of each histogram. Hovering the cursor over the triangle will activate a tool tip that specifies satellite, tracker, and sample size on the first line. The remaining tool tip data are the coordinates of the triangle and therefore extraneous for analysis purposes.
23087	It is now possible to integrate trajectories below the 90 km cutoff. The required settings are (a) to use either MSIS atmospheric density model, (b) to use Burlish Stoer or RK7(8) integrators, and (c) to select RelativeError for StepSize.StepControlMethod. The integrator will process the trajectory to 10 km altitude, and will terminate with an error message.
23235	The TroposphereData attribute scope has been renamed, while retaining backwards compatibility for scripting.
23239 23817	ODTK now provides one scenario selection to control the display of GPS or UTC Time.
23296	Several problems with the Transmit B3 obs script were fixed. Saving (B3 obs) measurements should now function properly.
23357	The correct smoother start time is now calculated when the smoother StartTime and TimeSpan modes are selected.
23388	Smoother instant maneuver names in the instant maneuver summary report have been corrected.
23458	Formerly, the Smoother would abort if the Smoother Rough File List were set to empty after the intial smoother run. Now, instead, an error message is displayed.
23503	New warning messages have been added to the filter, triggered when EOP or flux data is out of date. New attributes have been added to the Scenario object to allow the user to control the time span that triggers these messages.
23516	The capability has been added to provide scaling of orbit/clock covariances for individual PRNs when using a space based GPS receiver and SP3 file as a reference.
23600	The measurement update method used in ODTK 5 allows for simultaneous correction by any number of measurements that all occur at the same time. The matrix formulation changes the order of multiplication and addition over ODTK 4.1 in the measurement update process. The user may ocassionally notice some small differences in smoother covariances. The overall behavior is the same compared to 4.1 baseline.
23657	An error in the diurnal aberration computation for ground based right ascension and declination measurements has been corrected.
23658	Aberration computations have been added to the ground based Az/El measurement models. The facility aberration setting will be honored by the measurement model when the use light time delay flag on the measurement statistics is set to true.
23711	STK and ODTK are released asynchronously. If a user maintains an older version of ODTK but updates to newer versions of STK, it is possible that ODTK will reject the version stamp for newer attitude and ephemeris files generated with STK. Currently ODTK 5 recognizes STK ephemeris and attitude files through version 8.1.
23827	A new Units tab has been added to Tools->Options, which allows the user to specify the default units for time to be used in any new scenario created in ODTK. The options are GPSG and UTCG. This setting does not change the units in an existing scenario. To change the default units in an existing scenario (options are UTCG and GPSG), the attribute under Scenario.Units.DateFormat should be changed.
23989	Improved checks have been added for valid reference ephemeris file spans when filtering.
24323	Clock phase graphs were changed to give phase to 0.01 ns precision.
24519	A 3rd clock parameter, Aging, has been added.
24742	The capability to generate double differenced dual frequency pseudo-range and carrier phase observations from input undifferenced pseudo-range and carrier phase, and the capability to process double differenced dual frequency pseudo-range and carrier phase observations, have been added.
24753	The Filter STK Ephemeris Uniform grid option is now implemented.
24931	The ability to simulate and process ground based Time Difference Of Arrival (TDOA), Frequency Difference Of Arrival (FDOA), the rate of TDOA (TDOA Dot) and single differenced forms of TDOA and FDOA has been added. The ground based measurement signal path begins with transmission from a static ground based emitter. The signal is then transponded by two relay satellites to a common ground antenna. The ability to simulate and process space based TDOA, FDOA and TDOA Dot has been added. The space based measurement signal path begins with transmission from a static ground based emitter and end at signal reception by two space based receivers.
25251	The default for the Filter.SaveOnlyLastMeasPerStep attribute has been changed to 'true'.
25615	ODTK now can output ACTRAC (or Lance) tracking data into a file.
25667	In the Tracking Data Provider description field, "Lance File" was changed to "ACTRAC File" to clarify that ODTK supports ACTRAC tracking data files.
25674	Attributes have been added to the GPSConstellation object that let the user create buffers at both ends of an SP3 file for extrapolation.
26030	An issue has been resolved where simulation of GPS receivers on multiple satellites failed. Now multiple satellites with GPS receivers will be simulated correctly.
26416	A measurement provider has been added to read Air Force Space Command 2nd Space Operation Squadron RAW GPS ground receiver tracking data.
26420	A new date format, GPSZ, has been added.
26424	Multiselect functionality has been added to the IOD, Filter, and Simulation List Boxes.
26842	DOP computations performed by the GPS Satellite Selection Plugin now work correctly.
26979	The Concatenate SP3 tool can now mutiselect multiple input files.
26980	A new residual edit code has been added.
27009	When a transponder is not explicitly defined, a zero bias is assumed. The bias is not added to the state.
27160	Data limiting for reports and graphs displaying measurement residuals has been changed in a way that could affect the data returned from the database. The most important change is related to limiting by the Facility Name which will now only limit data for cases where a facility other than the tracking facility is involved in the measurement strand. An example of such a facility is the BRTS station involved in a BRTS range measurement. A complete description of how data limiting works for measurement residuals is now included in the ODTK help.
27274	A new option provides a speed-up for reports and graphs for the user who may not want to report or graph cross correlations. The Filter and Smoother both provide an opportunity to SaveCrossCorrelations in the respective runfile. Setting this to "true" saves all cross correlations exactly as was done in previous versions of ODTK. Setting this to "false" will reduce the size of the runfile and thereby speed up reports and graphs. The runtime savings are most dramatic for large state space scenarios.
27474	The attributes displayed for a GPS constellation change based on its configuration, including the presence or absence of GPSSatellite objects.
27829	The default Satellite Solar Pressure Parameter is now set to 1 (it was 0.75 before). This is to make ODTK consistent with STK, and to be consistent with a default Reflectivity model of "Sphere with perfect absorption".
27891	An error in the measurement partials for Doppler measurements for deep space satellites has been corrected. This error only affected satellites orbiting at distances greater than 10 Earth Radii, which is well beyond the geostationary belt.
28244	Right-click options for displaying and copying attribute information have been improved. See help page for details.
28334	ODTK has been updated to honor the interpolation method specified in reference ephemeris files of the *.e format. However if segmented *.e files are input to ODTK, the output files will not be segmented nor will they have doubled points at segment boundaries. This is true even if the user runs the Simulator with no deviates; the output Truth epehemeris will not be segmented. ODTK assumes that output ephemerides are continuous, if not smooth.
28575	The ConcatenateSP3Files utilities can be used to concatenate several contiguous SP3 files together. By design, if an SV is active in one SP2 file but not in another, the SV is added to the SP3 header, but Pos/Vel records over the inactive period contains "null" data. ODTK 5 only supports one active SV period on the SP3 file. If an SV is active, then dropped, then reenabled, data during the reenabled period is ignored.
28621	The default Initial GPS Receiver Clock Phase Sigma has been changed from 1 millisec to 100 nanosec. The default Initial GPS Receiver Clock Freq Sigma has been changed from 8.2e-10 s/s to 1e-12 s/s.
29385	It is possible to set the Y-axis to display numbers in scientific notation. First right-click on the graph to bring up Chart FX Properties. Then click on Axes -> Y Axis (via drop-down choices) -> Details -> Format = Scientific notation. However, usually the automatic tick marks in scientific notation are not on an even grid. To display these tick marks in a presentable format, click on the "General" tab in Y Axis Properties and change Major unit from "Auto" to a number, 1000 for example. in the process of changing the Y Axis setting above, the secondary Y axis may pop up unexpectedly. If this is the case then the secondary Y axis can be turned off by going to Axes -> Secondary Y Axis (via drop-down choices), then unchecking the box "Visible" to remove it.
29465	A new tracking data provider has been added to simplify the use of geolocation observations. The GEOLOC format allows input of TDOA, FDOA and TDOA Dot measurements tagged at either ground or satellite time of receipt. The GEOLOC format additionally allows input of single differenced TDOA and FDOA measurements tagged at ground time of receipt.
29552	The state units on Facility Latitude & Longitude state estimate parameters have been changed from radians to degrees. To see this change in effect, create a filter debug output file.
29639	Regarding GPSConstellation1.SVReference.Source.OverrideSourceFileTimes: In ODTK 4.1 the override time was used to initialize the PRNList. This caused a quandary if a PRN was enabled at the override time but disabled in the file (or vice versa). In ODTK 5 the original file times are used to intialize the PRNList.
29906	The x-axis label for all graphs from "Minutes past Midnight" to "Minutes since" has been changed. This coincides with the introduction of GPS Time (GPSG) as an optional x-axis time system and the fact that "Midnight" is either a local time notion or a Universal Time notion, but is not a GPS Time notion.
29909	A memory leak was fixed in HPOP plugin calls that returned data through the use of an array.
29975	The GPS Constellation object only displays the necessary attributes for its configuration in the Object Properties window.
30339	The default ODTK Epoch has been changed to "1 Jul 2006 12:00:00" to be consistent with STK 8.
30514	The utility GenerateSiteSolution.htm provides the capability to set initial position and clock phase and drift biases for a Monitor Station. It is important to properly set the SP3 reference point (Ref Pt) to reflect whether the SP3 is Center of Mass or Antenna Phase Center.
30566	The Transmit B3 obs reader now writes out the correct obs format.
30829	A problem with processing simulated TDRS 4 way range when the observations were saved to the generic obs format (.gobs) and the EditOnDoppler attribute of the 4 way range measurement statistic was turned on has been corrected. In prior versions, the 4 way range measurements would have been rejected citing invalid Doppler measurements.
30886	The option to compute orbit state transition matrices using an analytical two body approximation has been removed. Old scenarios with this setting will be converted to use variational equations upon loading of the scenario.
31066	The B3 Type 9 obs has been restricted to exclude range as a measurement type. Since Type 9 is SB RA/SB DEC, it is intended for passive optical data against a star background and will not naturally include range. Type 8 B3 obs do support satellite-to-satellite ranging, providing SB range, SB Az, and SB El, consistent with an active ranging instrument.
31240	A correction for a relativistic effect on the GPS satellite clock offsets has been added to the computation of navigation solutions. This modification should improve the accuracy of generated navigation solutions.
31315	Measurement Statistics attributes now implement an 'InsertByName' property to facilitate changes via scripting.
31560	The Astrodynamics Consistency document was updated to include consistency between ODTK and STK/Astrogator as well as the HPOP propagator. It also includes updates to reflect improvements in both HPOP and Astrogator.
31568	The ephemeris generation function of satellite objects has been modified to always use the initial state of the satellite as the initial conditions for ephemeris generation. Prior versions would simply interpolate the specified reference trajectory if the EstimateOrbit flag on the satellite was set to false. The behavior of the satellite ephemeris generation function has not changed the case where the EstimateOrbit flag is set to true.
31569	An error in the application of finite maneuvers that span the filter stop time for the case where ephemeris prediction is requested as part of the filter run has been corrected. In prior versions, the finite maneuver was not continued after the end of the filter span into the prediction interval. Note that this problem only affected the ephemeris prediction for the run that ended during the finite maneuver. Subsequent filter runs starting from restart records correctly applied the remainder of the finite maneuver.
31618	A Tracking System for Universal Space Network has been added.
31684	The 4.1.2 and 5.0 installation GPSCatalog.txt file represents the GPS Constellation status as of 12/01/2006.
31700	Loading data product lists from earlier versions of ODTK will result in error messages being issued in the message viewer. These messages indicate a problem with loading older versions of report and graph styles. If the referenced report and graph styles were part of the installation of the prior version of ODTK, the new version of the styles will be located and the data product list will be updated inside ODTK. If you then save the data product list, the saved version will point to the version 5 styles and will not generate error messages the next time it is loaded.
31702	Data limiting for report and graph generation has been improved to use fully qualified names of objects in the ODTK scenario. This change may require updates to existing data product lists that use data limiting based on tracking strands or to report/graph covariance cross correllation data. If requested data limiting for a data product list from a prior version cannot be resolved upon loading of its data product list, error messages will be generated to the message viewer, which should enable the manual reconfiguration of the data product list. Saving the updated data product list will eliminate the need to manually resolve the data limiting selection the next time the data product list is loaded.
31738	The PRNList Enabled attribute flag has been moved to the EnabledPRNs list; scripting support is provided in ODTK 5 and will be discontinued in ODTK 6. Please update your scripts accordingly.
31740	Only SP3 GPS ephemeris sources were supported in ODTK 4.1.2. SEM and YUMA support is provided in ODTK 5.
31770	The source file's effective start time is now used when reading the catalog file, which determines the SVN assigned to a PRN at a given time. However, the catalog file is not automatically reloaded when the source file is changed or the Override Source Times flag is toggled, so the PRNList is not dynamically updated. This may or may not be desired behavior; if you have entered unique values in the PRNList, you may not want them updated, and if the catalog file is reloaded, those values will be overwritten. To force a reload of the catalog file via scripting, reset the GPS constellation's SVReference.Catalog.Filename. Via the Object Properties, you will need to select a Catalog file with a different name or in a different directory. For this you can simply make a copy of the original file, select it, apply the change, and then reselect the original file.
31863	A data con utility has been added to the ODTK install, which converts STK ephemeris files (*.e) to GPS NAVSOL format. The utility is called STK2NAVSOL and is included in install directory. This utility can be used to allow ODTK to refit to an ECF external ephemeris in the STK standard format. The NAVSOL file created by this utility can be input as a measurements file, provided that a GPS Receiver is attached to the satellite, NAVSOL data statisitics are specified in the receiver, and the tracking ID entered in the tool matches the Tracking ID specified in the GPS Receiver. One use for this utililty is to refit GPS ephemerides and solve for the solar pressure model coefficient, which are not generally available from open sources.
31938	The LeastSquares object now has an EmitterList attribute, just as on the Filter and Simulator, to allow a unique selection of emitters to be used in a Least Squares solution. The emitter list will be shown in the Data Limiting section in the Static Product Builder; however it will not be used to actually limit the display of Least Squares residual data.
32884	A Simulator infinite loop problem that occurred when using multiple high precision interval specifications has been fixed.

Transition matters and unresolved 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:

Attribute Changes

Scripting access to a number of object attributes has changed during the development of ODTK 5. Please refer to the accompanying guide for more information.

Effects of Geopotential Errors

Currently the simulator does not simulate the effects of geopotential errors, but the filter error covariance does account for geopotential errors. This problem does not affect the processing of real data. If one looks carefully at the filter response to processing simulated data, the error magnitudes of filter orbit errors are smaller than is indicated by associated orbit error root variances.

Sigmas for Simulated Data

As currently defined, the Atmospheric Density Estimate, Solar Radiation Pressure Estimate, Transponder Bias and Ballistic Coefficient graph styles do not generate sigmas for simulated data. However, if you generate one of these types of graphs with a simulation file as input, the legend will contain references to sigmas, and a straight line purporting to represent sigma values will appear in the graph. These should be ignored, since there is no sigma data in the input file. To remove the spurious references and the line from the graph, right-click on the graph, select Properties, select the Series tab, select the series to hide and uncheck the 'visible' box.

Report Viewer

Help on the ODTK Report Viewer is not available directly from that interface. However, help is provided via the ODTK Help system. In the Contents tab, navigate to Reports & Graphs -> Reports -> Static Reports -> Report Viewing Options.

Number of Tables in Reports and Graphs

For optimal performance, only single-table reports should be generated. Graph styles support a single table only.

Troposphere Range Refraction

Troposphere range refraction error is currently modeled in the filter, but deviates are not applied by the simulator. Consequently, filter range residual ratio histograms derived from simulated range data will be somewhat peaked, when compared to the Gaussian density function. However, troposphere range refraction is modeled in both the filter and the simulator.

Limitations on Control of GPS Measurement Types

The control of GPS measurement types in the current release is subject to certain limitations. The selection of measurement types must be made in the satellite attribute MeasTypes. The filter can model GPS measurements exactly as simulated, which is the simplest case. However, the filter can process these measurements in different ways, as single differencing (SD), and/or as dual-frequency (DF) corrected measurements. The filter gives precedence to the most derived measurement types; the simulator will only generate the basic measurement types regardless of whether or not more derived types are specified in the MeasTypes list. See the online Help page on Measurement Processing for tables of measurement precedence.

Saving Scenarios Loaded from Prior Versions

If you load a scenario saved with ODTK 4 or a prior version, and then save it, it will be saved as an ODTK 5 scenario and cannot be loaded back into prior versions.

EarthDefinition Files

As part of transitioning ODTK scenarios from one version to the next, you should pay special attention to files being used for EOP, solar flux and ionosphere modeling. These files are specified in the EarthDefinition section of the scenario attributes. If you load a scenario created in ODTK 4 or a prior version into ODTK 5, the files specified in the older version will be found and will continue to be used. While this is desirable for some cases, such as performing regression tests, you will probably want to update these file locations to point to files associated with ODTK 5. These newer files are the ones which will be updated by the Update Data Files tool in ODTK 5.

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 reports styles created by the user. Before attempting to use a report style generated with a ODTK 4 or a prior version with ODTK 5, 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.

ODTK_Style_Update40To50 Tool

Since ODTK 4 graph styles are not compatible with ODTK 5, a tool has been provided to convert your ODTK 4 custom graph styles to ODTK 5 graph styles. The tool is called ODTK_Style_Update40To50.pl, and is found in your install area under AppData\Scripts. This tool will convert all graph styles in the designated directory and store them to a new directory. It is recommended that you use a different folder for output, so that your ODTK 4 graph styles are not overwritten.

Large File Limitations in Graphing

Due to an addressing limitation in WIN32, graphs can fail when any data file size exceeds 2 GB. This limitation applies to any file, including the input database or the intermediate file constructed by ChartFX from the database. If the intermediate file is too large, the suggested recourse is to use data limiting or reduce the time period on the inputs tab of the Static Product Builder.

GPS Selection Plugins

During simulation of GPS measurements, if a GPS selection plugin is being used, but fails, the simulator will continue with a default selection which simply picks the first 4 satellites. When using a GPS selection plugin to simulate measurements, check the message viewer carefully for plugin failure messages.

Changes in Gauss Markov Parameters

If you change the Gauss Markov parameters or the Constant value of a state variable in the GaussMarkovList during Restart, then the corresponding object properties (e.g. tracker MeasurementStatistics, satellite ForceModel parameters, transponder bias) are also changed to match the Restart state values. You must save the scenario to preserve the object properties settings and restart file settings; failure to do so will result in modeling errors in subsequent filter runs.

Version Changes in Tracking Data Interface

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

Users that have custom scripts can either update them with new ProgIDs or use the *.wsc examples under AppData/Scripts to change their code to dynamically read ProgIDs from ODTK\AppData\Scripts\MeasProviders\WindowsScriptComponents\CreatODDBObjects.txt, which we update with the latest ProgIDs for every release.

AutoOD Updates

AutoOD is updated to run with ODTK 5 and STK 8.0.1., but note the following:

1. Existing scripts may contain statements such as the following:

   Set app = CreateObject("ODTK4.Application") ' VBScript start OD4.0 AgUiApplication

   or

   $app = Win32::OLE->new("ODTK4.Application"); # Perl Script start OD4.0 AgUiApplication

   For these scripts to work in ODTK 5, "ODTK4.Application" will need to be changed to "ODTK5.Application" or "ODTK.Application"

   Similarly if your scripts run both ODTK and STK, they probably contain statements such as:

   Set stkApp = CreateObject("STK6.Application")

   For the script to work with STK 8.0.1, change it to:

   Set stkApp = CreateObject("STK8.Application")

   or

   Set stkApp = CreateObject("STK.Application")

2. Similarly, existing VBScript files may contain a statement such as:

   set odwin = odApp.Windows.Add ("AgUiDllHtmlViewer6.AgUiPiHtmlViewer", _
   "C:\Program Files\AGI\ODTK 4\ODTK\AppData\HtmlInterface\Start\Start.htm")

   The string "AgUiDllHtmlViewer6" will need to be changed to "AgUiDllHtmlViewer5" for these scripts to work in ODTK 5. Also note that ODTK 5 does not include the utilities "<INSTALL DIR> \ODTK\AppData\HtmlInterface\Start\Start.htm" or "<INSTALL DIR> \ODTK\AppData\HtmlInterface\Welcome\Welcome.htm". In ODTK 5 these HTML pages are part of "<INSTALL DIR>\Data\LaunchPad\launch_Pad.htm"

3. In ODTK 4 the following VBScript statement outputs to Epoch the date and time without time system, e.g. "20 Feb 2004 13:00:00.000":

   Epoch = od.Scenario(0).Filter(0).ProcessControl.AutoSelectedRestartTime

   In ODTK 5.0 the above statement outputs to Epoch the date and time with the time system, e.g. "20 Feb 2004 13:00:00.000 UTCG". The time system information in the Epoch string causes the STK connect command SetEpoch to fail. Therefore, the string "UTCG" has to be removed before calling SetEpoch. For example this code used to work in ODTK 4:

   Epoch = od.Scenario(0).Filter(0).ProcessControl.AutoSelectedRestartTime
   ...
   ...
   cmdText = "SetEpoch Scenario/" & scenName & " " & chr(34) & Epoch & chr(34)
   stk.ExecuteCommand(cmdText)
   ...

   To make it work in ODTK 5, replace the SetEpoch statement above with the following:

   Epoch = od.Scenario(0).Filter(0).ProcessControl.AutoSelectedRestartTime
   ...
   ...
   Dim Epoch_OD40
   ' filtering out the string UTCG because STK doesn't like it Epoch_OD40 = Replace(Epoch,"UTCG"," ") cmdText = "SetEpoch Scenario/" & scenName & " " & chr(34) & Epoch_OD40 & chr(34)
   stk.ExecuteCommand(cmdText)

4. Finally existing scripts may contain hardcoded paths such as:

   "C:\Program Files\AGI\ODTK 4\ODTK\AppData"

   These paths will need to be changed to

   "C:\Program Files\AGI\ODTK 5\ODTK\AppData"

It is easier to install STK 8.x before ODTK 5 if the option exists.

Version 3 and 4 Restart Files

ODTK 5 does not support ODTK 3 restart files; it does support ODTK 4 restart files.

Suppose you have an ODTK 4 scenario where the filter is in restart mode but the restart file has been deleted. If you open that scenario in ODTK 5 and run the filter without opening the Object Properties for the filter, no restart file will be written. An error message will state that the restart file cannot be opened, but the filter will still run, and, until you close the scenario and begin again, a restart file will not be created.

If you open the same scenario and open Object Properties for the filter, the Start Mode will change from Restart to Initial, and it will function correctly if you run the filter.

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
00239	The filter cannot be single-stepped from the very beginning of the run. If you begin the run and then pause, you can single-step from that point. At the beginning of the run, however, the step forward button on the toolbar is grayed out.
04880	The X-axis labels on the histogram graph are not displayed symmetrically if the number of bins changes.
06610	When you have a SaveAs dialog open in ODTK, the part of the window that shows the contents of the current folder does not update. When you click the Create New button, it creates a folder but does not show it.
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.
07402	Print preview of graphs does not function correctly.
07630	Setting the Display Product option to false on a graph data product is ignored when an Export option is chosen.
22691	ODTK 5 script writers may now directly insert objects into the Filter TrackerList attribute, for example:    ODTK.Scenario1.Filter1.TrackerList.insert(ODTK.Scenario1.TrackingSystem1.Facility1) However names with hyphens, for example:     set unused = ODTK.WizardScenario1.Filter1.TrackerList.insert(ODTK.WizardScenario1.Baseline.GUAM-A) will not work due to scripting limitations.
23475	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.
26002	It is not possible to Export the HTML generated by the ViewScenario.htm utility to Microsoft Excel, even though the option is offered. This export feature is installed with the latest versions of Microsoft Office and appears on all web pages in IE.
26653	Due to a limitation with VBScript, an object with a name beginning with a digit should by accessed by an index or string lookup instead of directly. For instance, ODTK.Scenario(0).23DegIncSat will fail, while ODTK.Scenario(0).Satellite("23DegIncSat") will work.
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 will drive the filter covariance negative. This issue is being addressed.
31636	If you add finite or instant maneuvers to the script or HTML page, or delete them, you must re-click the Satellite object. Otherwise the maneuver list dialog will display stale data.
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.
31917	The Static Product Builder does not update the Data Product List filename when it is loaded from a script. The workaround is to close and reopen the Static Product Builder or browse to the correct directory manually.
32139	State File To SP3 utility limits output to GPSSatellites named PRN01, PRN02, etc. This issue will be corrected in the next ODTK release.
32194	There are undocumented functional attributes called NewPositionVector and LambertSolution, which are reserved for future features.

Changes introduced in ODTK 5.0.1

The following information applies to ODTK 5.0.1.

Capabilities added and issues resolved in ODTK 5.0.1

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:

New Capabilities and Resolved Issues in ODTK 5.0.1
Tracking No.	Description
33143	An issue has been fixed where the smoother would abort if a particular combination of events were encountered: (1) when smoothing across multiple rough files, (2) with state space changes during that time, (3) using an acceleration history file for a maneuver, and (4) the smoother performed a prediction.

Changes introduced in ODTK 5.0.2

The following information applies to ODTK 5.0.2.

Capabilities added and issues resolved in ODTK 5.0.2

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:

New Capabilities and Resolved Issues in ODTK 5.0.2
Tracking No.	Description
33269	Previously, if a GEOSC file contained a partially truncated line, then values from the previous line were used for the missing columns, resulting in a less than fully valid measurement. Now zero values are returned for the missing items.
33499	The use of frequency-based transponder selection for 1W Bistatic Range has been added. Prior versions of ODTK did not use the transmitted frequency as specified in the properties of the transmitting ground station or via the tracking data interface to select the correct relay transponder. The use of explicit transponder IDs specified through the tracking data interface for 1W Bistatic Range has been added.
33663	A MathPlayer upgrade (version 2.1) caused equations in compiled help systems using the Microsoft HTML Help Viewer, such as the STK Help System, not to display properly. Attempting to open a page containing MathML-encoded equations caused the help system to terminate abnormally. Design Science has cured this deficiency in MathPlayer version 2.1a, which is installed automatically with ODTK 5.0.2 (replacing whatever version of MathPlayer is on the system).
34063	The gravity process noise model has been changed to automatically turn off for eccentricity > 1. The algorithm is not valid in these cases and formerly resulted in the computation of an indeterminate covariance deweighting matrix.
34800	ODTK reads SP3 files in the format now referred to as SP3-a. The IGS community now use SP3-c. A script "sp3c_2_sp3a.pl" is provided at the ODTK install location \ODTK\AppData\Scripts to convert SP3-c files to SP3-a for input to ODTK. A future release of ODTK will integrate the SP3-c format into ODTK.
35629	An issue has been fixed for the special case where the filter and smoother run with a single block of states for one satellite's orbit parameters. An application abort during reporting and graphing has been corrected.
35642	An issue related to simulator restart has been resolved. Before this fix simulated biases would jump in a statistically incorrect manner at the restart time.

Changes introduced in ODTK 5.0.3

The following information applies to ODTK 5.0.3.

Capabilities added and issues resolved in ODTK 5.0.3

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:

New Capabilities and Resolved Issues in ODTK 5.0.3
Tracking No.	Description
36513	A problem in the IRI 2001 ionospheric model that could have resulted in the application crashing or the computation of incorrect total electron counts for cases where the analysis time period was beyond the span of the data file ig_rz.dat has been corrected.
36558	An issue has been resolved for the case where the filter generates a prediction from a restart point while under scripting control and generates a different ephemeris than when under manual control. This correction improved accuracy and reliability for several restart conditions. The user may notice that a restarted filter will now more closely duplicate a longer running filter (without restart).
36656	The IRI2001 FORTRAN library was updated to fix a runtime error due to an array index out of bounds problem.

Online Help Resources

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

• ODTK Help System
• Context Sensitive (F1) Help
• Printable (PDF) Tutorials and Technical Documents

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 textbox. 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 recur 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.