Including Tracking Data in an Estimation Process
|Top Previous Next|
You can define tracking data sources to be used in an estimation process through the object editors or through FreeFlyer script. The process is the same, regardless of the type of estimator being used.
Including Tracking Data through the Object Editors
When working with a BatchLeastSquaresOD, KalmanFilterOD, SquareRootInformationFilterOD, or UnscentedKalmanFilterOD object that has been created in the Object Browser, you can use its object editor to define the tracking data files that will be included in the estimation process. Edit the OD object by double-clicking it, and then proceed to the Observation Sources page (shown in the image below). From this page, you can add any of the file types supported natively by FreeFlyer. Each file type has different configuration options; the yellow text box on the right side of the screen will tell you whether your current configuration is valid.
Observation Sources page of the UnscentedKalmanFilterOD Object Editor
Configuration options for each file include:
If multiple GroundStations are provided as observers, FreeFlyer will automatically assign appropriate receiving and transmitting antennas from the list provided based on their ID when processing data from a tracking data file, allowing for processing of "2-way" or "3-way" observations. See Simulating 3-way Observations for more information.
Including Tracking Data through FreeFlyer Script
When working with a BatchLeastSquaresOD, KalmanFilterOD, SquareRootInformationFilterOD, or UnscentedKalmanFilterOD object that has been created in FreeFlyer script, you will need to create additional objects in script representing the tracking data files that will be used. For each of these files, you will need to set the source and target objects, as well as the data and corrections to use. Once the file objects have been created, you can include them in an estimation process using the RegisterTrackingDataFile method.
Each file type has different configuration options, including some optional settings. The example below shows how to specify an observed Transponder or Transponder/Sensor pair in addition to setting the observed Spacecraft. If a Sensor is specified, the Sensor's X, Y, and Z position properties will be used to model an offset from the origin of the Spacecraft body coordinate system (BCS) when modeling measurements. This is particularly relevant for Spacecraft with rapidly changing attitudes, such as spinning Spacecraft.