TE_AssociatedObject
Import an Associated Object data file for a known ownship
Syntax
TE_AssociatedObject <ScenarioPath> Add {<Parameters>}
TE_AssociatedObject <ScenarioPath> Delete|Reload Ownship "<OwnshipName>" SourcePath "<FilePath>"
Related commands
Description
The TETK Plugin must be installed in order to use this command.
The TE_AssociatedObject command will import an Associated Object data file for a known ownship.
A vehicle of the specified type, default of aircraft, will be created in STK. This vehicle will be the "target" for the specified ownship. The Associated Object does not appear in the TETK Flight analysis tool (FAT). If you already have a vehicle created and configured in STK, then you can use the keyword AttachTo to have the TE_AssociatedObject command apply the data file to that vehicle.
Parameters can be entered in any order.
Use the following format to import an Associated Object data file.
TE_AssociatedObject <ScenarioPath> Add File "<FileName>" Name "<DisplayName>" Ownship "<OwnshipName>" [ObjectType "<ObjectTypeName>"] [Model "<ModelPath>"]
The following table describes the parameters for this TE_AssociatedObject command.
| Parameter | Description |
|---|---|
| File "<FilePath>" | Enter a file path to an object track file. Supported file formats are csv, ctdf, amcat, qview, h5td, and .tedb. |
| Name "<DisplayName>" | The display name of the object. Note that if the TSPI mapping contains AircraftId, then you cannot manually define the object name. If you wish to define the object name, the TSPI mapping cannot contain AircraftId. |
| Model "<ModelPath>" | Enter the file path to a model file to represent the object. This parameter is optional. |
| ObjectType "<ObjectTypeName>" | Enter the object type for the loaded TSPI data. Valid object types: Aircraft, Ground Vehicle, Launch Vehicle, Missile, Satellite, and Ship. The default object type is Aircraft. This parameter is optional. |
| Ownship "<OwnshipName>" | The name of the Ownship that this object will be associated with. |
| TSPIMapping "<MappingName>" | Enter the name of the TSPI data mapping for the data. This parameter, while recommended, is optional. |
| TimeColumn "<Name>" | Enter the name of the time column. A time data mapping for this file type must contain a time column of this name. This parameter, while recommended, is optional. |
| UnitsFile "<FilePath>" | Enter the full path to the units definition file. This parameter is optional. |
| TimeEpoch "<DateTimeString>" | Enter the relative start time for the data.
This must be defined if you use the TimeUnits parameter. A daysecond or HMS TimeUnit requires a timeEpoch of midnight. |
| TimeUnits "<Value>" | Enter the time units. Valid options are Day, hour, minute, second, millisecond, microsecond, nanosecond, daysecond, and HMS. Second is the default.
This parameter is optional; if used, the TimeEpoch parameter is required. |
| CloseDialog "<Yes | No>" | Set the CloseDialog parameter to Yes or No. The default value is Yes. This parameter enables you to close the DataImport dialog when issuing connect commands. |
Use the following format to apply the data file to an existing STK object.
TE_AssociatedObject <ScenarioPath> Add AttachTo "<STKObject>" Ownship "<OwnshipName>" File "<FileName>"
The following table describes the parameters for the TE_AnalysisObject command.
| Parameter | Description |
|---|---|
| AttachTo "<STKObject>" | Enter the name of an STK object. |
| Ownship "<OwnshipName>" | The name of the Ownship that this object will be associated with. |
| File "<FilePath>" | Enter a file path to a track file. Supported file formats are csv, ctdf, amcat, qview, and h5td. |
The following table describes the parameters for the Delete and Reload commands.
| Parameter | Description |
|---|---|
| Ownship "<OwnshipName>" | Enter the name of the loaded Ownship. |
| SourcePath "<FilePath>" | Enter the source path of the ownship. |
| File "<File>" | Enter the name of the file you wish to reload. |
Examples
To import an Associated Object into STK and TETK:
To import a detailed Associated Object into STK and TETK:
To attach to an Associated Object:
To delete an Ownship track file:
To reload an Ownship track file:
To import an Associated Object with object type and model into STK and TETK:
Return message
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
12