TE_Spec
Load a *.csv or xml file with a Specification profile into T&E.
Syntax
TE_Spec * {Import|Execute} {File "<FilePath>"|Spec "<WorkflowName>"} [ActiveSpecs "<SpecElementName> [| <ReaderName>]"]
Related commands
Description
The T&E Tool Kit Plugin must be installed in order to use this command.
The TE_Spec command will parse the Specification file to create a Specification Workflow and add it to the current scenario. The "<FilePath>" must be a full path to a T&E specification file.
The following table describes the parameters for the Import parameters.
| <Parameters> | Description |
|---|---|
| File "<FilePath>" | The path to an xml or csv file that defines one of more specifcations. A specifcation workflow is created for each Spec. |
| ActiveSpecs "<SpecElementName> [| <ReaderName>]" | Optional field to set the active elements and optionally, the reader name to be used when executing the Spec. If the xml does not specify a spec element is active, and it is not set as active by this command, the spec element is considered inactive and will not be used at execution. If a spec element reader name is not set, the first valid data reader that contains the element name will be used. The specified ReaderName must be the name of a reader in the current scenario or the command will fail. The specified SpecElementName must be presnent in the spec file or the command will fail. |
The following table describes the parameters for the Execute parameters.
| <Parameters> | Description |
|---|---|
| Spec "<WorkflowName>" | The name of the Specifcation workflow you will be executing. The Workflow's name was set by the imported specifcation. |
Examples
Examples
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
13.0