TE_TrackComparison
Generate a Track comparison
Syntax
TE_TrackComparison <ScenarioPath> {Add | Export} <Parameters>
Related Commands
Description
The T&E Toolkit Plugin must be installed in order to use this command.
The TE_TrackComparison command is used to generate a Track comparison
The following table describes the parameters for the Add option.
| <Parameters> | Description |
|---|---|
| Name "<TrackName>" | The display name of the track. |
| AnalysisObject "<AnalysisObjectName>" | The name of the Ownship that contains the data to the track. |
| Track "<TrackName>" | The name of the track. |
| TruthObject "<ObjectPath>" | Specify the STK object that represents the actual path flown by the test object. |
| TruthPointing "{TruthPointing}" | The vector creation method from the truth object that will be used when creating the track comparison. Valid values are: SensorBoresight, StkVector, StkObject, and None. The default is StkObject. |
| MeasuredObject "<ObjectPath>" | Specify the STK object that represents the sensor detected path flown by the test object. |
| MeasuredPointing "{MeasuredPointing}" | The vector creation method from the measured object that will be used when creating the track comparison. Valid values are: SensorBoresight, StkVector, StkObject, and None. The default is StkObject. |
| ReferenceSystem "<ReferenceSystem>" | Enter the specification of a VGT System component. |
| TimePath "<TimeInterval>" | Optional. Enter the specification of a Time Interval component that the track should be limited to. |
For specification of "<ReferenceSystem>" or "<TimeInterval>" see Component Specification.
The following table describes the parameters for the Export option. The Filter parameters are optional.
| <Parameters> | Description |
|---|---|
| Name "<TrackName>" | The display name of the track. |
| File "<FilePath>" | |
| AzimuthFilterFrom <Value> | The minimum value of an azimuth filter.
The AzimuthFilterTo filter must be entered with this filter. |
| AzimuthFilterTo <Value> | The maximum value of an azimuth filter.
The AzimuthFilterFrom filter must be entered with this filter. |
| AzimuthFilterUnit <unitAbbrev> | The abbreviation of the units that the azimuth values are entered in. The default is radians. |
| ElevationFilterFrom <Value> | The minimum value of an elevation filter.
The ElevationFilterTo filter must be entered with this filter. |
| ElevationFilterTo <Value> | The maximum value of an elevation filter.
The ElevationFilterFrom filter must be entered with this filter. |
| ElevationFilterUnit <unitAbbrev> | The abbreviation of the units that the elevation values are entered in. The default is radians. |
| SlantRangeFilterFrom <Value> | The minimum value of a range filter.
The SlantRangeFilterTo filter must be entered with this filter. |
| SlantRangeFilterTo <Value> | The maximum value of a range filter.
The SlantRangeFilterFrom filter must be entered with this filter. |
| SlantRangeFilterUnit <unitAbbrev> | The abbreviation of the units that the range values are entered in. The default is meters. |
Example
To set up a T&E Track comparison:
TE_TrackComparison * Add Name "TrackCompare" AnalysisObject "AF3_0385" Track "MyTrack" TruthObject "Aircraft/Drone" TruthPointing "StkObject" MeasuredObject "Aircraft/MyTrack_Measured" ReferenceSystem "Aircraft/AF3_0385 NorthWestUp System" TimePath "Aircraft/AF3_0385 AvailabilityTimeSpan Interval"
To export a T&E Track comparison:
TE_TrackComparison * Export Name "TrackComp1" File "\\\agi\common\dev\TnE_toolkit\data\RegressionTests\Tests\TrackComparison\Output\TrackCompare2.csv" AzimuthFilterFrom "-70" AzimuthFilterTo "70" AzimuthFilterUnit "deg" ElevationFilterFrom "-70" ElevationFilterTo "70" ElevationFilterUnit "deg" SlantRangeFilterFrom "5" SlantRangeFilterTo "20" SlantRangeFilterUnit "km"
ReturnMessage
Group Membership
This command belongs to the following group(s):
You can use TETK Connect commands in TETK scenarios for pre-flight planning, post-flight analysis, and to support analysis workflows.
You should not use TETK Connect commands when real-time propagators are creating STK vehicles and using STK features instantaneously. The use of Connect commands in a real-time application requires more computational power than STK can support.
TETK functionality that is commonly referred to as "real-time" is actually an offline analysis mode. In this mode, an STK/TETK scenario is prepared with data that is streamed to a particular time in a mission. The post-flight analysis can be prepared again on demand throughout the mission for the data for each time of request. You can use TETK Connect commands in these scenarios.
Version
11.5