Data Archive Options

When running the smoother, variable lag smoother, filter, and simulator, you can make large amounts of data available for reporting and graphing by saving them to an output file. ODTK lets you determine what data to save during each run. The data files can become quite large, and the less data that needs to be saved to disk, the faster the application will run.

In the following table, asterisks are used to indicate limits on availability of an item:

Data Archive Options
Property Description
Filename Name of the process run file, such as Scenario1.filrun. The extensions are assigned automatically (.filrun, .simrun and .smtrun for filter, simulator and smoother respectively). These files are used when reporting or graphing static data.
FileUpdateMethod* Allows data accrued during a restart or autorestart run to be included with a previous run file. Setting to Overwrite will cause the output run files to be overwritten with the new data (default). Setting to Append will cause the new data to be added into the existing run files. The Append setting will be ignored in the following conditions: running in Initial mode, if the run filename changes between successive runs, or if the filter or simulator object name does not match the one used to create the existing run file. In each case, the behavior will revert to Overwrite.
OutputStateHistory Flag that indicates whether to save satellite state and covariance. This information can be output at every process time (AllTimes), or only at measurement times (MeasTimes).
EveryNSteps Allows thinning of output data. A value of 1 will save at every possible output time; a value of 2 will save at every second possible time, etc.
SaveCrossCorrelations**** Opt whether to store the block diagonals for covariance data in runfiles or to save full covariances. The blocks are defined as in the filter, so that orbit is in same block with SRP and drag coefficient, clocks are separate, biases are separate, etc.
SaveOnlyLastMeasPerStep*** If there are multiple measurements at a given time, you can save state and covariance records after each individual measurement has been processed. Alternatively, if you set this flag to true, you can reduce the reported data by saving the state and covariance only after the last of a set of measurements is processed at a given measurement time.
OutputMeasHistory* Flag that indicates whether to save information relating to measurement processing, such as residuals, sigmas, edit flags, etc.
OutputManeuvers If set to true, ODTK saves pre- and post-maneuver data to files for reporting.
OutputSummary* Saves off the final state configurations for satellite and tracker summary reports.
OutputDataFiles When true, the process writes a file containing a summary of the environmental data files used for EOP, flux and planetary ephemeris. This information can be viewed using the Data File Summary report.
OutputEmpiricalForces If true, saves empirical forces model data for reporting.
OutputHistograms* As the filter or simulator runs, it can accumulate residual or noise statistics and save them for reporting or graphing. If this property is set to true, the user can set the histogram range and bin size.
HistogramSize* Specify the maximum number of sigmas that comprise the histogram. The default is 3 sigmas, which translates to +/- 3 sigmas.
NumberHistogramBins* The granularity of the histogram is determined by the number of bins in the histogram.
OutputPerturbations** For the simulator, the initial perturbations made to state parameters can be saved to disk.
OutputGPSSVMeasInfo* Flag to output to the Measurement History file GPS SV data (e.g. orbit, clock error, group delay) used in the modeling of GPS pseudorange measurements. If output this data can be displayed by the GPS SV Data Report. Data is intended to be more of a validation tool than an operational tool so is optionally output for space and run time considerations.

ODTK 6.5