TE_AnalysisObject
Import an Ownship data file.
Syntax
TE_AnalysisObject <ScenarioPath> Add {<Parameters>}
TE_AnalysisObject <ScenarioPath> Delete Ownship "<OwnshipName>" SourcePath "<FilePath>"
Related commands
Description
The TETK Tool Kit Plugin must be installed in order to use this command.
The TE_AnalysisObject command will import an Ownship track file.
A vehicle of the specified type, default of aircraft, will be created in STK. An ownship will be created in 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_AnalysisObject command apply the data file to that vehicle. If you would like to use attributes of the STK object within TETK (values not in the data file) then you can use the keyword FromSTK and list the attributes to make known to TETK
Parameters can be entered in any order.
Use the following format to specify a data file.
TE_AnalysisObject <ScenarioPath> Add File "<FilePath>" Name "<DisplayName>" [Model "<ModelPath>"]
The following table describes the parameters for this format.
| 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 vehicle. |
| Model "<ModelPath>" | Enter the file path to a model file to represent the vehicle. This parameter is optional. |
| 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. |
| Set | Sets the analysis time period of an analysis object that has been imported. |
| SetAnalysisPeriod | Sets the scenario start and stop time to be the ephemeris time of the new ownship. |
| SetAllAnalysisPeriod | Sets the scenario start and stop time to be the overall start and stop time of all analysis objects. |
| ReaderName "<Name>" | Enter a custom reader name. |
Use the following format to apply the data file to an existing STK object.
TE_AnalysisObject <ScenarioPath> Add AttachTo "STKObject" File "<FilePath>"
The following table describes the parameters for this format.
| Parameter | Description |
|---|---|
| AttachTo "<STKObject>" | Enter the name of an STK object. |
| File "<FilePath>" | Enter a data file path. Supported file formats are csv, ctdf, amcat, qview, and h5td. |
Use the following format to use attributes of an STK object within TETK (values not in the data file) listing the attributes to make known to TETK.
TE_AnalysisObject <ScenarioPath> Add FromSTK [TimeStep "<seconds>"] Scalars "<Parameter>" Name "<DisplayName>" [ObjectType "<ObjectType>"]
The following table describes the parameters for this format.
| Parameter | Description |
|---|---|
| FromSTK [TimeStep "<Seconds>"| Access "<Value>"] Scalars "<ScalarParam>" | For TimeStep, enter the time in seconds. This parameter is optional. For Access, enter the full name of the access using this naming convention: "*/Access/<FromClassName>-<FromInstanceName>_To_<ToClassName>-<ToInstanceName>". These names display in the combo box when on the STK Data Selector page in the data importer. "<ScalarParam>" is "<objecttype>:<scalarname>[\\<subscalarname>]" where \\<subscalarname> is optional and multiple <scalarname>[\\<subscalarname>] can be entered, separated by commas. For example: "aircraft:Heading,LLA State" "missile:LLR State\\TrueOfDate" "ship:Heading,Vectors\\Position" "launchvehicle:Classical Elements\\ICRF"If using the Access parameter, the scalar list of names must contain the access data element names. No group names are allowed in the list for access. |
| Name "<DisplayName>" | The display name of the vehicle. |
| ObjectType "<ObjectType>" | Enter the type of object. Valid values are aircraft, missile, ship, satellite, and ground vehicle. This parameter is optional. |
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
Import an Ownship track file into STK and TETK:
Import a detailed Ownship track file into STK and TETK:
Set the analysis time period of an analysis object that has been imported:
Set the scenario start and stop time to be the overall start and stop time of all analysis objects:
FromSTK example:
AttachTo example:
Delete an Ownship track file:
Reload an Ownship track file:
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