Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Track algorithm
open-in-new
<h2 id="history">History</h2> <p>The original tracking algorithms were built into custom hardware that became common during World War II. This includes <a href="/facts/Storage_tube/42gU6bXG">storage tubes</a> used with planned position indicator displays, range height indicator displays, and pen-plotting boards used for civilian air traffic control and waterway management. It also includes custom analog computers, like the <a href="/facts/Mark_I_Fire_Control_Computer/B7s7BHyM">Mark I Fire Control Computer</a> used with radar data to aim guns, missiles, and torpedoes associated with military air traffic control and waterway management. </p><p>Track algorithms were migrated from analog equipment to digital computers from the 1950s through the 1980s. This was necessary to eliminate limitations that include mid-air collisions and other problems linked with obsolete equipment that was socialized by <a href="/facts/Professional_Air_Traffic_Controllers_Organization_(1968)/B0DFrd8c">PATCO</a> and <a href="/facts/United_States_Department_of_Defense/dWAvf7e3">United States Department of Defense</a>. Similar migration trends occurred in other countries throughout the world for similar reasons. </p><p>Modern civilian air traffic and military combat systems depend upon a custom track algorithms used with <a href="/facts/Real-time_computing/p9HxgL4L">real-time computing</a> slaved to displays and peripherals. </p><p>Limitation for modern digital computing systems are processing speed, input-output throughput rate, the number of input-output devices, and software compatibility with upgrade parts. </p> <h2 id="terminology">Terminology</h2> <p>Tracking algorithms operate with a <a href="/facts/Cartesian_coordinate_system/lkTqvMmB">cartesian coordinate system</a>. This is often called a rectangular coordinates, and is based on north–south, east–west, and altitude. Sensors operate using a <a href="/facts/Polar_coordinate_system/HBko4YoN">polar coordinate system</a>. This is often called spherical coordinates based on elevation, bearing, and range. Some common terminology is as follows. </p> <table><tbody><tr><th>Term</th><th>Meaning</th></tr><tr><td>Azimuth</td><td>Angle along the earth horizon</td></tr><tr><td>Bearing</td><td>Angle along the artificial horizon (deck)</td></tr><tr><td>Elevation</td><td>Angle above or below the horizon</td></tr><tr><td>Range</td><td>Distance along the plane established by the horizon</td></tr><tr><td>Slant Range</td><td>Distance along the true line of sight</td></tr><tr><td>True</td><td>Angle in earth coordinates with true north as the reference</td></tr><tr><td>Relative</td><td>Angle in deck-plane coordinates using vehicle heading as the reference</td></tr><tr><td>Rectangular</td><td>Cartesian coordinates typically known as X, Y, and Z</td></tr><tr><td>Spherical</td><td>Polar coordinates typically known as range, bearing, and elevation</td></tr></tbody></table> <h2 id="human-interface">Human interface</h2> <p>Users are generally presented with several displays that show information from track data and raw detected signals. </p> <ul><li><a href="/facts/Radar_display/Sy0j9NFI">Plan position indicator</a></li> <li>Scrolling notifications for new tracks, split tracks, and join tracks</li> <li><a href="/facts/Radar_display/Sy0j9NFI">Range amplitude display</a></li> <li><a href="/facts/Radar_display/Sy0j9NFI">Range height indicator</a></li> <li><a href="/facts/Radar_display/Sy0j9NFI">Angle error display</a></li> <li>Audible alerts (buzzer or voice)</li></ul> <p>The audible alert draws attention to the scrolling notification. This will present the track number for things like separation violation (impending collision) and lost track not located near a landing facility. </p><p>The scrolling notifications and audible alerts require no user action. Other displays activate to show additional information only when a track is selected by the user. The primary human interface for the tracking algorithm is a planned position indicator display. This typically puts up four pieces of information. </p> <table><tbody><tr><th>Term</th><th>Meaning</th></tr><tr><td>Raw video</td><td>Analog detection pulses from radar and sonar systems</td></tr><tr><td>Track</td><td>A symbol and number allowing operators to unambiguously identify the vehicle</td></tr><tr><td>Leader</td><td>A line showing where the vehicle will be in the future.</td></tr><tr><td>IFF</td><td>Transponder data showing identity. This may include speed, altitude, and heading in commercial aircraft.</td></tr></tbody></table> <p>The track algorithm produces symbology that is displayed on the Plan Position Indicator. </p><p>Users have a pointing device with several buttons that provides access to the track file through the Plan Position Indicator. The typical pointing device is a track ball, which operates as follows. </p> <table><tbody><tr><th>Term</th><th>Meaning</th></tr><tr><td>Activate Button</td><td>Bring a cursor to the center of the display.</td></tr><tr><td>Rolling Ball</td><td>Used to scroll the cursor near a track symbol or raw sensor video.</td></tr><tr><td>Hook Button</td><td>Select the track once the cursor is in the desired location.</td></tr><tr><td>Drop Button</td><td>Return the display to its normal operating condition (not associated with dropping tracks).</td></tr></tbody></table> <p>Hook action turns off the cursor and displays additional information from the track algorithm. The user can perform actions while the hook is active, such as communicate with the vehicle or notify other users regarding the vehicle associated with the track. </p> <h2 id="operation">Operation</h2> <p>The nearest neighbor track algorithm is described here for simplicity. </p><p>Each new detection reported from incoming sensor data is fed into the track algorithm, which is used to drive displays.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> </p><p>Track algorithm operation depends upon a track file, which contains historical track data, and a computer program that periodically updates the track file.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> </p><p>Sensors information (radar, sonar, and transponder data) is provided to the track algorithm using a <a href="/facts/Polar_coordinate_system/HBko4YoN">polar coordinate system</a>, and this is converted to <a href="/facts/Cartesian_coordinate_system/lkTqvMmB">cartesian coordinate system</a> for the track algorithm. The polar to Cartesian conversion uses navigation data for sensors mounted on vehicles, which eliminates sensor position changes caused by ship and aircraft motion that would otherwise corrupt track data. </p><p>Track mode begins when a sensor produces a sustained detection in a specific volume of space. </p><p>The track algorithm takes one of four actions when this new sensor data arrives. </p> <table><tbody><tr><th>Action</th><th>Explanation</th></tr><tr><td>Store</td><td>Sensor data is stored temporarily for capture and track evaluation</td></tr><tr><td>Drop</td><td>Stored sensor data failed to fall within track volume or capture volume within the time limit (discarded)</td></tr><tr><td>Capture</td><td>Sensor data falls near previous sensor data not associated with a track and a new track is developed</td></tr><tr><td>Track</td><td>Sensor data falls within the volume of an existing track and is added to track history for that track</td></tr></tbody></table> <p>Each separate object has its own independent track information. This is called track history. This could be as much as an hour for airborne objects. Track history for underwater objects can extend back several weeks. </p><p>Each different kind of sensor produces different kinds of track data. A 2D radar with a fan beam produces no altitude information. A 4D radar with a pencil beam will produce radial Doppler velocity in addition to bearing, elevation, and slant range. </p> <h2 id="store">Store</h2> <p>New sensor data is stored for a limited period of time. This occurs before track, capture and drop processing. </p><p>Stored data needs to be held for a limited time to allow time for comparison with existing tracks. Stored data must also be held long enough to complete processing required to develop new tracks. </p> <h2 id="drop">Drop</h2> <p>Data quickly loses any purpose for sensor systems that use an M out of N detection strategy. Stored data is often dropped after N scans have expired with fewer than M detections within a specific volume. </p><p>Drop processing takes place only after track and capture processing takes place. Drop data may sometimes be extracted from main memory and recorded onto storage media along with the track file for offsite analysis. </p> <h2 id="capture">Capture</h2> <p>The capture strategy depends upon the kind of sensor. </p><p>Capture processing takes place only after stored sensor data has been compared with all existing tracks. </p> <h3>Non-Doppler</h3> <p>Each sensor detection is surrounded by a capture volume. This is shaped like a box. The size of the capture volume is approximately the distance the fastest vehicle can travel between successive scans of that same volume of space. </p><p>Sensors (radar) scan a volume of space periodically. </p><p>As an example, a capture distance of 10 miles require periodic scans no more than 15 seconds apart in order to detect vehicles traveling at mach 3. This is a performance limitation for non-Doppler systems. </p><p>Transition to track begins when the capture volume for two detections overlap. </p> Capture (3D) { | X ( new ) − X ( s ) | < Separation | Y ( new ) − Y ( s ) | < Separation | Z ( new ) − Z ( s ) | < Separation {\displaystyle {\text{Capture (3D)}}\;{\begin{cases}\left\vert X({\text{new}})-X(s)\right\vert <{\text{Separation}}\\\left\vert Y({\text{new}})-Y(s)\right\vert <{\text{Separation}}\\\left\vert Z({\text{new}})-Z(s)\right\vert <{\text{Separation}}\end{cases}}} Capture (2D) { | X ( new ) − X ( s ) | < Separation | Y ( new ) − Y ( s ) | < Separation {\displaystyle {\text{Capture (2D)}}\;{\begin{cases}\left\vert X({\text{new}})-X(s)\right\vert <{\text{Separation}}\\\left\vert Y({\text{new}})-Y(s)\right\vert <{\text{Separation}}\end{cases}}} <p>Each new detection not paired with a track is compared with every other detection not yet be paired with a track (cross correlation with all stored data). </p><p>Transition to track typically involves an M out of N strategy, such as at least 3 detections out of a maximum of 5 scans. </p><p>This strategy produces a large number of false tracks due to clutter near the horizon and in the viscidity of weather phenomenon and biologicals. Birds, insects, trees, waves, and storms generate enough sensor data to slow down the track algorithm. </p><p>Excessive false tracks degrade performance because the track algorithm loading will cause it to fail to update all of the information in the track file before sensors begin the next scan begins. <a href="/facts/Chaff_(countermeasure)/V8TAMysf">Chaff</a> is intended to deny detection by exploiting this weakness. </p><p><a href="/facts/Moving_target_indication/EUo8tCMd">Moving target indication</a> (MTI) is typically used to reduce false clutter tracks to avoid overwhelming the track algorithm. Systems that lack MTI must reduce receiver sensitivity or prevent transition to track in heavy clutter regions. </p> <h3>Doppler</h3> <p>Lock and radial velocity are unique requirement for Doppler sensors that add additional layers of complexity to the track algorithm. </p><p>The radial velocity of the reflector is determined directly in Doppler systems by measuring the frequency of the reflector over the short span of time associated with detection. This frequency is converted to radial velocity. </p><p>The radial velocity of the reflector is also determined by comparing the distance for successive scans. </p><p>The two are subtracted, and the difference is averaged briefly. </p> Lock criteria { | ( Δ R Δ T ) − ( C × Doppler Frequency 2 × Transmit Frequency ) | < Threshold {\displaystyle {\text{Lock criteria}}\;{\begin{cases}\mathrm {\left\vert \left({\frac {\Delta R}{\Delta T}}\right)-\left({\frac {C\times {\text{Doppler Frequency}}}{2\times {\text{Transmit Frequency}}}}\right)\right\vert <{\text{Threshold}}} \end{cases}}} <p>If the average difference falls below a threshold, then the signal is a lock. </p><p>Lock means that the signal obeys <a href="/facts/Classical_mechanics/ykG8upsN">Newtonian mechanics</a>. Valid reflectors produce a lock. Invalid signals do not. Invalid reflections include things like helicopter blades, where Doppler does not correspond with the velocity that the vehicle is moving through the air. Invalid signals include microwaves made by sources separate from the transmitter, such as <a href="/facts/Radar_jamming_and_deception/sGoEJ6Bv">radar jamming and deception</a>. </p><p>Reflectors that do not produce a lock signal cannot be tracked using the conventional technique. This means the feedback loop must be opened for objects like helicopters because the main body of the vehicle can be below the rejection velocity (only the blades are visible). </p><p>Transition to track is automatic for detections that produce a lock. This is essential for <a href="/facts/Semi-active_radar_homing/zHGSAe2V">semi-active radar homing</a> that requires velocity information obtained by the launch platform radar. </p><p>Transition to track is manual for non-Newtonian signal sources, but additional signal processing can be used to automate the process. Doppler velocity feedback must be disabled in the vicinity of reflectors like helicopters, where Doppler velocity measurement does not match radial velocity of the vehicle. </p><p>Pulse-Doppler sensor data includes object area, radial velocity, and lock state, which are part of the decision logic involving join tracks and split tracks. </p> <h3>Passive</h3> <p>Passive sensor information includes only angle data or time. Passive listening is used when the tracking system is not emitting any energy, such as with underwater systems, with electronic counter countermeasures, and with projectile sensors. </p><p>The three strategies are bi-static, synthetic aperture, and <a href="/facts/Time_of_arrival/4UIdVk4Q">time of arrival</a>. </p><p>Bistatic measurements involves comparing data from multiple sensors that can produce only angular data. Distance is identified using <a href="/facts/Parallax/Gu8W21LP">parallax</a>. </p><p>Synthetic aperture involves taking multiple angular measurements while the emitter maneuvers. The process is similar to <a href="/facts/Celestial_mechanics/FA3uR78J">celestial mechanics</a> where orbit is found from line of site data. The distance to a vehicle traveling at constant velocity will fall at discrete points along a straight line transecting the line of site. The <a href="/facts/Coriolis_effect/SqCyUY6d">coriolis effect</a> can be used to determine the distance to this line when the object maintains constant speed during a turn. This strategy is normally used with <a href="/facts/Semi-active_radar_homing/zHGSAe2V">semi-active radar homing</a> and with underwater systems. </p><p>Time measurements are used to identify signals from impulse sources, such as from projectiles and bombs. Bombs produce a single impulse, and the location can be identified by comparing the time of arrival as the shock wave passes over 3 or more sensors. Projectiles produce an initial impulse from the muzzle blast with a shock wave traveling radially outward perpendicular to the path of the supersonic projectile. The shock wave from the projectile arrives before the muzzle blast for inbound fire, so both signals must be paired by the tracking algorithm. Subsonic projectiles emit a shock wave that arrives after the muzzle blast. </p><p>The signal emission signature must be used to match up angular data to accomplish track capture when multiple signal sources arrive at the sensor simultaneously. </p> <h2 id="track">Track</h2> <p>All new sensor data is compared with existing tracks first before capture or drop processing takes place. </p><p>Track position and velocity information establishes a track volume at a future position. New sensor data that falls inside that track box is appended to the track history for that track and deleted from temporary storage. </p> Append { Size > | X s − ( X o + V x ⋅ Δ T ) | Size > | Y s − ( Y o + V y ⋅ Δ T ) | Size > | Z s − ( Z o + V z ⋅ Δ T ) | {\displaystyle {\text{Append}}\;{\begin{cases}{\text{Size}}>\left\vert X_{s}-(X_{o}+V_{x}\cdot \Delta T)\right\vert \\{\text{Size}}>\left\vert Y_{s}-(Y_{o}+V_{y}\cdot \Delta T)\right\vert \\{\text{Size}}>\left\vert Z_{s}-(Z_{o}+V_{z}\cdot \Delta T)\right\vert \end{cases}}} <p>During operation, XYZ sensor measurements for each vehicle are appended to the track file associated with that vehicle. This is the track history that is used to keep track of position and velocity. XYZ velocity is determined by subtracting successive values and dividing by the time difference between the two scans. </p> Velocity { V x = ( X 1 − X 0 ) / Δ T V y = ( Y 1 − Y 0 ) / Δ T V z = ( Z 1 − Z 0 ) / Δ T {\displaystyle {\text{Velocity}}\;{\begin{cases}Vx=(X_{1}-X_{0})/\Delta T\\Vy=(Y_{1}-Y_{0})/\Delta T\\Vz=(Z_{1}-Z_{0})/\Delta T\end{cases}}} <p>Tracks where the vehicle continues to produces a detection are called active tracks. The track volume is much smaller than the capture volume. </p><p>The track is continued briefly in the absence of any detections. Tracks with no detections become coasted tracks. The velocity information is used to move the track volume through space briefly as the track volume is expanded. </p><p>New tracks that fall within the capture volume of a coasted track are cross correlated with the track history of the nearby coasted track. If position and speed are compatible, then the coasted track history is combined with the new track. This is called a join track. </p><p>A new track that begins in or near the capture volume of an active track is called a split track. </p><p>Coasted track, joined track, and split track trigger an operator alert. For example, a track coast can result from an aircraft collision, so the cause needs to be determined otherwise supervisory personnel need to be notified. </p><p>Civilian air traffic control personnel use leaders produced by the track algorithm to alert pilots when the future position of two tracks violate the <a href="/facts/Separation_(air_traffic_control)/5kHa4Wh5">separation limit</a>. </p><p>Track data is usually recorded in the event that an investigation is required to establish the root cause for an aircraft loss. </p><p>This is a special case of the <a href="/facts/Kalman_filter/wNK7rnbk">Kalman filter</a>. </p> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>"Fundamentals of Radar Tracking". Applied Technology Institute. Archived from the original on 2011-08-24. Retrieved 2012-08-14. <a href="https://web.archive.org/web/20110824221707/http://www.aticourses.com/fundamentals_radar_tracking.htm" target="_blank">https://web.archive.org/web/20110824221707/http://www.aticourses.com/fundamentals_radar_tracking.htm</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>"Local Tracking". Radar Tutorial Dot EU. Archived from the original on 2012-07-08. Retrieved 2012-08-14. <a href="http://www.radartutorial.eu/10.processing/sp20.en.html" target="_blank">http://www.radartutorial.eu/10.processing/sp20.en.html</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>"Performance Comparison of Tracking Algorithms for a Ground Based Radar" (PDF). Ankara University. Archived (PDF) from the original on 2023-06-03. Retrieved 2024-12-28. <a href="https://dspace.ankara.edu.tr/xmlui/bitstream/handle/20.500.12575/61502/15636.pdf" target="_blank">https://dspace.ankara.edu.tr/xmlui/bitstream/handle/20.500.12575/61502/15636.pdf</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> </ol>