Point Targeted
Point sensors to track or target other objects in a scenario
Syntax
Point <SensorObjectPath> Targeted {OrientMethod} <MethodData>
Related commands
- Point 3DModel
- Point AlongVector
- Point External
- Point Fixed
- Point FixedInRef
- Point GrazingAlt
- Point Schedule
- Point Spinning
Description
The Point Targeted command allows you to model sensors that track other objects and set a sensor to target other objects in a scenario.
Prior to manipulating any Target, the Target must first be Added to the Sensor, using the Add or File {OrientMethod}.
<MethodData> for Targeted sensor pointing is dependent on the {OrientMethod} used. Valid values for {OrientMethod} and their associated <MethodData> are as follows:
| {OrientMethod} | <MethodData> | Description |
|---|---|---|
| Add | <TruncObjectPath> | Add or remove the specified target. |
| Remove | ||
| File | "<Filepath\Filename.txt>" | "<Filepath\Filename.txt>" is a ASCII text file containing a list of truncated object paths. The objects specified in the file are added as targets to the Sensor. If the file contains duplicate or invalid target names, those targets are skipped, and only valid targets will be added. The command will not NACK in this case.
"<Filepath\Filename.txt>" can be the path to a file on your local drive or the path to a file on an SDF server. See Specifying Paths for "<SDFFilePath>" syntax information. |
| Tracking | <TruncObjectPath> [{AboutBoresight} [{TrackMode}]] | Define the sensor as Tracking the specified Target.
Valid values for {AboutBoresight} are Hold, Rotate, and Level. If {AboutBoresight} is not entered the default is Rotate. Valid values for {TrackMode} are Transpond, Transmit, and Receive. {TrackMode} can only be entered on the command if {AboutBoresight} has been entered. |
| Fixed | <TruncObjectPath> {OrientMethod} <MethodData> | Define the sensor with a Fixed Boresight. A description of the {OrientMethod} and <MethodData> can be found in the Point Fixed command. |
| Times | {TimeOption} <Parameters> | For a description of individual {TimeOptions} refer to the Table following. |
| ComputeOptions | {ComputeOption} | Set user controls for the Access computations. For a description of individual {ComputeOption} refer to the Table following. |
| SaveAccesses | {On | Off} | If On is entered, then when the sensor is saved, the target accesses will also be saved in the sensor file. This prevents the accesses being recomputed when the sensor is loaded. The default is Off. |
A target object file, used by the File {OrientMethod}, might look something like the following:
# comment line Facility/aosFac Target/Target1 Target/Target2/Receiver/rc1 Target/BadName Target/Target3 #
If {OrientMethod} is File, and the sensor has not been set as Targeted, it will be set to Targeted: Tracking by default.
If {OrientMethod} is Times, {TimeOption} and <Parameters> can be:
| {TimeOption} | <Parameters> | Description |
|---|---|---|
| UseAccess | {On | Off} | If On, targeting schedule is based on accesses between the sensor and the targeted object. If Off, a user-defined targeting schedule is used. |
| Add | <TruncObjectPath> "<StartTime>" "<StopTime>" | Add a new interval to the targeting schedule. |
| Remove | Remove an interval from the targeting schedule. | |
| Change | <TruncObjectPath> "<ExistingStartTime>" "<ExistingStopTime>" "<NewStartTime>" "<NewStopTime>" | Change a given interval in the targeting schedule. |
| Replace | <TruncObjectPath> <NumIntervalPairs> "<IntervalStart>" "<IntervalStop>" ["<IntervalStart2>" "<IntervalStop2>"...] | Replaces the entire targeting schedule for the specified object with the schedule specified. |
| Load | [{Replace | Add}] "<IntervalFile>" | Load time intervals from an STK interval file. For help on creating the STK interval file, see Create & Import External Files - Interval List in STK Help.
Specify Replace to replace the existing interval list. Specify Add to add the intervals to the existing interval list. If this parameter is not included then the intervals in the interval file will be ADDed to the existing interval list. |
| AutoDeconflict | N/A | Resolves any conflicts that exist between targets and times. |
<TruncObjectPath> is a truncated object path to a facility, place, target, planet, star or any type of vehicle. "<TruncObjectPath>" can be the path to a file on your local drive or the path to a file on an SDF server. See Specifying Paths for "<SDFFilePath>" syntax information.
If {OrientMethod} is ComputeOptions, {ComputeOption} can be:
| {ComputeOptions} | Description |
|---|---|
| LightTimeDelayConvergence <Value> | This option sets the tolerance used when iterating to determine the light time delay. <Value> is entered in Connect time units, and should be between 1.0e-9 to 0.1 seconds |
| AberrationType {Total | Annual | None} | Set the model of aberration to be used in access computations. |
| MinTimeStep <Value> | <Value> is entered in Connect time units, and should be between 1.0e-5 to 315576000.0 seconds |
| MaxTimeStep <Value> | <Value> is entered in Connect time units, and should be between 1.0e-5 to 315576000.0 seconds |
| TimeConvergence <Value> | This option sets the time tolerance that is used by the access algorithms to determine the start times and stop times of access intervals. <Value> is entered in Connect time units, and should be between 1.0e-9 to 315576000.0 seconds |
| RelValueConvergence <Value> | <Value> should be between 0.0 to 1.0 |
| AbsValueConvergence <Value> | <Value> should be between 1.0e-30 to 1.0e30 |
| EventsBasedOnSamples {On | Off} | Set EventsBasedOnSamples On to determine access intervals based on the samples without doing any extra sub-sampling. |
| FixedSampleStep {Off | (<FixedStep> <TimeBound>) } | Enter values to control the step size used in Access sampling. Enter either Off or both <FixedStep> and <TimeBound>.
<FixedStep> is entered in Connect time units, and should be between 1.0e-5 to 315576000.0 seconds. <TimeBound> is entered in Connect time units, and should be between 0.0 to 86400.0 seconds. |
Examples
To point Sensor1 to track testFac1 while holding about the boresight:
Set the flag to have the target accesses for Sensor1 saved with the sensor file:
To target Sensor1 at Fac1 using a fixed azimuth and elevation while holding about the boresight:
To set-up the sensor to use a list of targets from file:
Add a time interval for the Target1 object:
Set access compute options for Sensor1:
Replace the existing intervals for Sensor1 with the intervals in the file:
Return message
Group membership
This command belongs to the following group(s):
Version
11.6