Is a reference path always the shortest route?

No. It may prioritize clearance, coverage, smoothness, visibility, or another objective rather than minimum distance.

Can several trajectories share one path?

Yes. They can follow the same geometric curve with different timing, including different speeds and pauses.

Does staying near the path guarantee collision avoidance?

No. The planned clearance, full robot geometry, tracking tolerance, and current obstacle information all matter. A line alone is insufficient evidence.

AI Glossary / Graphs and symbolic AI / Intermediate

Reference path

Definition

A reference path is a specified geometric route that a moving system is intended to follow. In robotics, it can describe desired positions or configurations along a curve. A controller uses this path as a target for motion. A path does not necessarily specify when each location should be reached; adding a time schedule produces a reference trajectory.

What it means

The reference is the intended motion, not a record of what actually happened. A robot's measured route can depart from it because of disturbances, imperfect control, estimation errors, or deliberate replanning.

It is useful to separate three questions: where should the robot go, how quickly should it move along that route, and which commands will make it do so? A reference path mainly answers the first. The distinction helps teams identify whether a problem lies in geometric planning, timing, or tracking. Here the term uses its robotics meaning, rather than a file-system path or a citation link.

How it works

A planner can represent the path as waypoints, connected segments, or a continuous curve q(s), where s indicates progress. In a common convention, s runs from zero at the start to one at the finish. The components of q might be joint angles or spatial coordinates, depending on the task.

A timing rule s(t) turns the path into q(s(t)), a desired configuration at each time. Different timing rules can follow the same geometric route while demanding different velocities and accelerations.

The controller compares the desired motion with the estimated actual motion and generates commands. Path generation must therefore consider collision clearance, robot geometry, and movement constraints. A curve that looks harmless on a map may still require an impossible turn or exceed a joint limit.

Three practical examples

Mobile inspection: a robot follows a planned route beside equipment while its controller corrects departures from that route.
Robot-arm simulation: a path specifies a sequence of joint configurations between an initial and a target pose.
Camera motion: a system plans a smooth spatial route for a camera, then chooses timing appropriate to the desired shot.

Think of it this way

Think of a hiking route drawn on a map. The line says where the walk should go, but it does not tell you whether each point is reached at noon or an hour later. A timetable adds that information. The analogy is limited because robot paths may live in configuration space, where a point represents several joint angles rather than one visible location on the ground.

Worked example

Consider a planar point moving along q(s) = (4s, 3s) meters for 0 ≤ s ≤ 1. The route runs from (0,0) to (4,3). Its length is five meters because the straight-line displacement has length √(4²+3²).

With timing s(t)=t/10 for a ten-second traversal, the reference at t=4 seconds is q(0.4)=(1.6,1.2). Velocity is constant at (0.4,0.3) meters per second, with speed 0.5 meters per second. Traversing the same path in five seconds doubles that speed to one meter per second.

Suppose at t=4 in the ten-second schedule the actual point is (1.2,0.9). It lies exactly on the geometric path, at s=0.3. Its perpendicular distance from the path is zero, yet it is 0.5 meters behind the scheduled reference along the line.

Thus perfect geometric path following does not imply perfect trajectory tracking. The constant-speed examples also assume the point can already be moving at the required speed. A physical system starting and ending at rest needs an appropriate acceleration and deceleration profile; an abrupt speed jump is not supplied by the geometric path itself.

Illustrative case study

Fictional case: Birch Camera Lab designs a simulated camera move along a straight reference path. The first preview reaches the intended endpoint, but it arrives too early for the planned scene transition.

The team leaves the geometric route unchanged and modifies the timing profile. It then checks the resulting velocity and acceleration demands and compares the actual simulated motion with the time-indexed reference. In a separate run, a new obstacle requires changing the route itself rather than merely slowing the old schedule.

This fictional case distinguishes path, timing, and execution. It does not establish that a real camera rig can follow the example without hardware-specific validation.

Common misconceptions and mistakes

A waypoint list does not fully specify every intermediate movement unless an interpolation rule is defined. Different curves through the same waypoints can have different clearance and curvature.

A straight path for an end effector does not necessarily mean each robot joint moves linearly, and a straight line in joint coordinates need not produce a straight end-effector route.

Another mistake is judging tracking only by endpoint arrival. A system can reach the endpoint after large intermediate deviations. Conversely, it can remain on the path while being behind schedule, as the worked example shows. Report geometric and timing errors separately when both matter.

Business use

Reference paths help make intended robotic or automated motion explicit and reviewable. They allow designers to discuss coverage, clearance, and task sequence before choosing detailed control commands.

Specify coordinate frames, units, starting conditions, interpolation, and acceptable deviations. Decide whether timing is fixed or can change during execution. Check that the path remains meaningful if the environment changes, and define when replanning is required. For shared results, preserve the reference alongside the measured trace so reviewers can distinguish a planning mistake from an execution or estimation problem.

Check your understanding

In the worked example, why can the actual point have zero path error but nonzero trajectory error?

Answer: It lies on the same line at an earlier progress value. It follows the geometric route but has not reached the position required by the current time schedule.

Related terms

Learn next

draw one route and design two timing profiles for it. Compare the required speeds and accelerations, then identify which changes alter only timing and which require a different geometric path.

Sources

Primary sources: Lynch and Park explain paths and time scaling: https://modernrobotics.northwestern.edu/nu-gm-book-resource/9-1-and-9-2-point-to-point-trajectories-part-1-of-2/ . Their continuation discusses profiles for starting and stopping: https://modernrobotics.northwestern.edu/nu-gm-book-resource/9-1-and-9-2-point-to-point-trajectories-part-2-of-2/ . AIMA's author index places the term in robotics: https://aima.cs.berkeley.edu/aima-index.html . The coordinate example and fictional case are original.

Previous: Reference metadata Next: Reference point