target_assignment.point: Target assignment (point method) - DO NOT DIRECTLY CALL THIS...

View source: R/target_assignment_point.R

target_assignment.pointR Documentation

Target assignment (point method) - DO NOT DIRECTLY CALL THIS FUNCTION

Description

This function IS NOT intended to be called by the user. The user is supposed to call target_assignment(method = "point") to access this function.

This function assigns every sensor point to a single target using the point method, which treats every point individually and assigns it to the closest target. The input is grouped by pointIndex and then only the closest target (minimum of locationError) is kept while the rest are discarded.

A target is then determined to be a false track (isFalseTrack = TRUE) if one of several possible cutoffs is exceeded. See get_isFalseTrack for details.

This function is not intended to be used as a stand-alone function, but rather as a part of the call to target_assignment. This function is called by target_assignment() when the user specifies method = "point".

Usage

target_assignment.point(targetTrackDistance, cutoff)

Arguments

targetTrackDistance

the output of target_track_distance()

cutoff

numeric vector of length 1, 2, or 3 specifying the conditions under which a point is determined to be a false track. The different lengths imply different cutoff conditions:

  • One number (vector length 1): points are false tracks if the location error (difference between sensor point and closest target) is greater than this value in meters

  • Two numbers (vector length 2): first number is cutoff in meters of the 2D error (sqrt(locationError^2 - altError^2)). Second number is cutoff in meters of the absolute value of the altitude error (sensor altitude reading - true target altitude)

  • Three numbers (vector length 3): first number is range error in meters, second number is bearing error in degrees, third number is altitude error in meters

Value

A data frame with the same number of observations as the sensor data that was originally passed to target_track_distance(). Each sensor point in the original data set has been assigned to a target using the method specified by the user, and the output data provides the following summary statistics:

  • lonError: difference in longitude between the sensor point and assigned target at the time of the sensor point

  • latError: difference in latitude between the sensor point and assigned target at the time of the sensor point

  • altError: difference in altitude between the sensor point and assigned target at the time of the sensor point

  • bearingToTarget: bearing (azimuth) to target from ownship at the time of the sensor point

  • trackNum: the track number associated with this sensor data point

  • tgtAssigned: the ID of the target assigned to this sensor point

  • locationError: distance between sensor point and target at the given time

  • pointIndex: index referring to which of the original sensor data points this target-track pair refers. Necessary for comparisons in target_assignment()

  • time: the time that this sensor point was recorded

  • bearingError: difference in bearing between the sensor point and target at the time of the sensor point

  • downrangeError: difference in range to ownship between the sensor point and target

  • lon: longitude of the sensor point

  • lat: latitude of the sensor point

  • alt: altitude of the sensor point

  • rangeToShip: range from target to ownship at the time of the sensor data point

  • targetAspect: target aspect (as seen from ownship) at the time of the sensor data point

  • meanLocationError: (only in square and gauss window methods) mean distance between sensor point and target for all of the points included in the window

  • isFalseTrack: boolean indicating whether a point is outside the cutoff and therefore considered a false track

  • tgtXtrack: factor expressing the truthID.trackNum interaction

  • segmentNumber: an integer counting the number of times during which a single track is assigned to a particular target


battleVerse/nautilus documentation built on July 16, 2024, 4:20 a.m.