Description | Example | Return message | Group

TE_TrackComparisonCalculator_RM

Return information for a Track comparison

Syntax

TE_TrackComparisonCalculator_RM <ScenarioPath> Name <TrackName> [{Filters}]

Related commands

Description

The T&E Tool Kit Plugin must be installed in order to use this command.

The TE_TrackComparisonCalculator_RM command is used to retrieve the calculated results of a Track comparison.

This command returns list of strings, with each containing: MOP_Name, Minimum, Maximum, Average, Standard Deviation and RMS.

Name <TrackName> is the name of the track comparison.

The following table describes the optional {Filters}.

{Filters}Description
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.

Examples

To return results from a T&E Track comparison:

TE_TrackComparisonCalculator_RM * Name "TrackCompare"

To return filtered results from a T&E Track comparison:

TE_TrackComparisonCalculator_RM * Name "TrackCompare" AzimuthFilterFrom "5.0" AzimuthFilterTo "6" AzimuthFilterUnit "rad" ElevationFilterFrom "-0.03" ElevationFilterTo "-0.002" ElevationFilterUnit "rad" SlantRangeFilterFrom "40" SlantRangeFilterTo "50" SlantRangeFilterUnit "km"

Return message

MOP Name:TC_Track_MissAngle,Minimum:0.1,Maximum:0.2,Average:0.15,StandardDeviation:0.113,RMS:0.16 MOP Name:TC_Track_RangeDifference,Minimum:0.1,Maximum:0.2,Average:0.15,StandardDeviation:0.113,RMS:0.16 MOP Name:TC_Track_AbsoluteRangeDifference,Minimum:0.1,Maximum:0.2,Average:0.15,StandardDeviation:0.113,RMS:0.16 MOP Name:TC_Track_ElevationDifference,Minimum:0.1,Maximum:0.2,Average:0.15,StandardDeviation:0.113,RMS:0.16 MOP Name:TC_Track_AzimuthDifference,Minimum:0.1,Maximum:0.2,Average:0.15,StandardDeviation:0.113,RMS:0.16

Group membership

This command belongs to the following group(s):

T & E Toolkit

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.3