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 enables you to model sensors that track other objects and set a sensor to target other objects in a scenario.
Prior to manipulating any target, you must first add the target to the Sensor using 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 an ASCII text file containing a list of truncated object paths. STK adds the objects specified in the file as targets to the sensor. If the file contains duplicate or invalid target names, STK skips those targets and only adds valid targets. 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}]] ["<ConstraintVector>"[<ClockAngleOffset>]] | Define the sensor as tracking the specified target.
Valid values for {AboutBoresight} are Hold, Rotate, Level, and UpVector. If you do not enter a value for {AboutBoresight}, it will default to Rotate. Valid values for {TrackMode} are Transpond, Transmit, and Receive. You can only enter {TrackMode} on the command if you enter {AboutBoresight}. You can only enter "<ConstraintVector>” and <ClockAngleOffset> in the command if you enter {AboutBoresight} and set it to UpVector; in this case, “<ConstraintVector>” is mandatory and <ClockAngleOffset> is optional. When specifying "<ConstraintVector>", include the truncated path of the object followed by a space and the name of the vector, all in quotes. Two examples are "Satellite/attSat Position" and "CentralBody/Earth Sun". Enter the <ClockAngleOffset> in degrees, between -360.0 and 360.0. The default value is 0.0 degrees. |
| Fixed | <TruncObjectPath> {OrientMethod} <MethodData> | Define the sensor with a Fixed Boresight. Descriptions of {OrientMethod} and <MethodData> are in the Point Fixed command. |
| Times | {TimeOption} <Parameters> | For a description of individual {TimeOptions}, refer to the {TimeOptions} table below. |
| ComputeOptions | {ComputeOption} | Set user controls for the Access computations. For a description of individual {ComputeOption}, refer to the {ComputeOption} table below. |
| SaveAccesses | {On | Off} | If you enter On, then when STK saves the sensor, it will also save the target accesses in the sensor file. This prevents recomputing the accesses when loading the sensor. 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 you did not set the sensor to Targeted, STK will set the sensor to Targeted: Tracking by default.
If {OrientMethod} is Times, {TimeOption} and <Parameters> can be:
| {TimeOption} | <Parameters> | Description |
|---|---|---|
| UseAccess | {On | Off} | If you enter On, targeting schedule is based on accesses between the sensor and the targeted object. If Off, STK will apply a user-defined targeting schedule. |
| Add | <TruncObjectPath> "<StartTime>" "<StopTime>" | Adds a new interval to the targeting schedule. |
| Remove | Removes an interval from the targeting schedule. | |
| Change | <TruncObjectPath> "<ExistingStartTime>" "<ExistingStopTime>" "<NewStartTime>" "<NewStopTime>" | Changes 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>" | Loads 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 you do not include this parameter, 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. Enter <Value> in Connect time units, between 1.0e-9 and 0.1 seconds |
| AberrationType {Total | Annual | None} | Set the model of aberration to be used in access computations. |
| MinTimeStep <Value> | Enter <Value> in Connect time units, between 1.0e-5 and 315576000.0 seconds |
| MaxTimeStep <Value> | Enter <Value> in Connect time units, between 1.0e-5 and 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. Enter <Value> in Connect time units, between 1.0e-9 and 315576000.0 seconds |
| RelValueConvergence <Value> | <Value> should be between 0.0 and 1.0 |
| AbsValueConvergence <Value> | <Value> should be between 1.0e-30 and 1.0e30 |
| EventsBasedOnSamples {On | Off} | Set EventsBasedOnSamples to On to determine access intervals based on the samples without doing any extra subsampling. |
| FixedSampleStep {Off | (<FixedStep> <TimeBound>) } | Enter values to control the step size used in Access sampling. Enter either Off or both <FixedStep> and <TimeBound>.
Enter <FixedStep> in Connect time units, between 1.0e-5 and 315576000.0 seconds. Enter <TimeBound> in Connect time units, between 0.0 and 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 a 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:
To target Sensor1 at Sat1 using a tracking boresight with Facility’s east vector as the constraint vector and an offset of 30.7 degrees:
Return message
Group membership
This command belongs to the following group(s):
Version
11.6