Contenuto principale

Aero.trajectory.tracklineTrajectory

R2026b

Generate reference signals for trackline search trajectory

Since R2026a

Description

refSignals = Aero.trajectory.tracklineTrajectory(Name=Value) generates reference signals for trackline search patterns. Use name-value arguments to define the trackline trajectory. For more information, see Algorithms.

example

Examples

collapse all

This example shows how to generate reference signals for a trackline trajectory.

refTrackline = Aero.trajectory.tracklineTrajectory(InitialPosition = [0,0], ...
Speed = 100,TrackLineType = "Trackline Search, Return (TSR)", ...
TrackPoint1 = [10,10],TrackPoint2 = [20,20], ...
TrackSpacing = 1000,Altitude = 5000, ...
OutputFormat = "timetable")
refTrackline = 5×7 timetable
         timestamps         WaypointIndex    xNorth(m)    yEast(m)    Speed(m/s)    Altitude(m)    Heading(rad)    FlightPathAngle(rad)
    ____________________    _____________    _________    ________    __________    ___________    ____________    ____________________

    06-Jul-2026 10:58:02          1                 0           0        100              0           5.5109               0.01        
    06-Jul-2026 10:58:52          2             716.4     -697.81        100           5000           0.7854               0.01        
    06-Jul-2026 10:58:53          3            727.81      -686.4        100           5000           2.3562               0.01        
    06-Jul-2026 10:59:13          4            -686.4      727.81        100           5000            3.927               0.01        
    06-Jul-2026 10:59:13          5           -697.81       716.4        100           5000            3.927               0.01        

	Get insights using Copilot

This example shows how to add reference signals for a trackline trajectory, refTrackline, to existing reference signals for another trajectory, refSector.

Create reference signals for a sector search trajectory.

sectorSignals = Aero.trajectory.sectorTrajectory(Altitude = 20, ...
Bearing = pi/2,DatumPoint = [-8,0], ...
InitialAltitude = 0,Radius = 5, ...
OutputFormat = "timetable",InitialHeading = 0)
sectorSignals = 9×7 timetable
         timestamps         WaypointIndex    xNorth(m)    yEast(m)    Speed(m/s)    Altitude(m)    Heading(rad)    FlightPathAngle(rad)
    ____________________    _____________    _________    ________    __________    ___________    ____________    ____________________

    06-Jul-2026 10:59:39          1                 0          0          90             0            3.1416             0.011111      
    06-Jul-2026 10:59:39          2                -8          0          90            20            1.5708             0.011111      
    06-Jul-2026 10:59:39          3                -8          5          90            20            5.7596             0.011111      
    06-Jul-2026 10:59:39          4           -3.6699        2.5          90            20            3.6652             0.011111      
    06-Jul-2026 10:59:39          5            -12.33       -2.5          90            20            1.5708             0.011111      
    06-Jul-2026 10:59:39          6            -12.33        2.5          90            20            5.7596             0.011111      
    06-Jul-2026 10:59:40          7           -3.6699       -2.5          90            20            3.6652             0.011111      
    06-Jul-2026 10:59:40          8                -8         -5          90            20            1.5708             0.011111      
    06-Jul-2026 10:59:40          9                -8          0          90            20            1.5708             0.011111      

	Get insights using Copilot

Add reference signals for a trackline trajectory, tracklineSignals, to sectorSignals.

tracklineSignals = Aero.trajectory.tracklineTrajectory(PriorTrajectory = sectorSignals, ...
TrackLineType = "Trackline Search, Return (TSR)", ...
TrackPoint1 = [10,10],TrackPoint2 = [20,20], ...
TrackSpacing = 1000,Altitude = 5000)
tracklineSignals = 13×7 timetable
         timestamps         WaypointIndex    xNorth(m)    yEast(m)    Speed(m/s)    Altitude(m)    Heading(rad)    FlightPathAngle(rad)
    ____________________    _____________    _________    ________    __________    ___________    ____________    ____________________

    06-Jul-2026 10:59:39          1                 0           0         90              0           3.1416             0.011111      
    06-Jul-2026 10:59:39          2                -8           0         90             20           1.5708             0.011111      
    06-Jul-2026 10:59:39          3                -8           5         90             20           5.7596             0.011111      
    06-Jul-2026 10:59:39          4           -3.6699         2.5         90             20           3.6652             0.011111      
    06-Jul-2026 10:59:39          5            -12.33        -2.5         90             20           1.5708             0.011111      
    06-Jul-2026 10:59:39          6            -12.33         2.5         90             20           5.7596             0.011111      
    06-Jul-2026 10:59:40          7           -3.6699        -2.5         90             20           3.6652             0.011111      
    06-Jul-2026 10:59:40          8                -8          -5         90             20           1.5708             0.011111      
    06-Jul-2026 10:59:40          9                -8           0         90             20           5.5165             0.011111      
    06-Jul-2026 11:00:36         10             716.4     -697.81         90           5000           0.7854             0.011111      
    06-Jul-2026 11:00:36         11            727.81      -686.4         90           5000           2.3562             0.011111      
    06-Jul-2026 11:00:59         12            -686.4      727.81         90           5000            3.927             0.011111      
    06-Jul-2026 11:00:59         13           -697.81       716.4         90           5000            3.927             0.011111      

	Get insights using Copilot

Name-Value Arguments

collapse all

Specify optional pairs of arguments as Name1=Value1,...,NameN=ValueN, where Name is the argument name and Value is the corresponding value. Name-value arguments must appear after other arguments, but the order of the pairs does not matter.

Example: InitialPosition = [0,0]

Initial position of trajectory, specified as a 1-by-2 or 2-by-1 vector in the units specified in Units.

Example: InitialPosition = [0,0]

Data Types: double

Speed of trajectory, specified as a finite real double scalar in the units specified in Units.

Example: Speed = 10

Data Types: double

Altitude of the vehicle trajectory, specified as a finite real scalar double in the units specified in Units. This value is constant throughout the vehicle path.

Example: Altitude = 10

Data Types: double

Initial heading of trajectory, specified as a finite real double scalar between 0 and 2*pi, in radians. Specify one each of InitialHeading and FinalHeading.

Example: InitialHeading = pi

Data Types: double

Output format of reference signals data, specified as a timeseries or timetable object.

Example: OutputFormat = timeseries

Input and output units, specified as one of these values.

Units

Position

Altitude

Speed

Metric (MKS)

Meters

Meters

Meters per second

English (Velocity in ft/s)

Feet

Feet

Feet per second

English (Velocity in kts)

Nautical miles

Feet

Knots

Example: Units = 'Metric (MKS)'

Initial time of trajectory operation, specified as a datetime object.

Example: StartTime = datetime('now')

Initial altitude of trajectory, specified as a scalar in the units specified in Units.

Example: InitialAltitude = 10

Data Types: double

Prior trajectory tracking data, specified as a timeseries or timetable object. These objects must contain the fields:

  • Altitude(m)

  • Heading(rad)

  • Speed(m/s)

  • WaypointIndex

  • xNorth(m)

  • yEast(m)

Dependencies

When specifying this name-value argument, also specify Trackspacing, TrackPoint1, and, TrackPoint2. Do not specify the name-value arguments InitialPosition, InitialHeading, or InitialAltitude.

Trackline search type, specified as Trackline Search, No return (TSN) or Trackline Search, Return (TSR).

Example: TrackLineType = Trackline Search, No return (TSN)

Data Types: char | string

First track point, specified as a 1-by-2 vector in the units specified in Units.

Example: TrackPoint1 = [10,10]

Data Types: double

Second track point, specified as a 1-by-2 or 2-by-1 vector as finite real doubles in the units specified in Units.

Example: TrackPoint2 = [2,10]

Data Types: double

Spacing between tracks, specified as a scalar.

Example: TrackSpacing = 10

Data Types: double

Vertical velocity component of vehicle during ascent, specified as a finite real double scalar less than the vehicle speed in the units specified in Units.

Example: ClimbRate = 10

Data Types: double

Vertical velocity component of vehicle during ascent, specified as a finite real double scalar less than the vehicle speed in the units specified in Units.

Example: DescentRate = 10

Data Types: double

Coordinates that define vertices of polygonal no-fly zone, specified as a N-by-2 numeric array, where N is equal to or greater than 3. Each row of the array contains an [x, y] boundary point. The function computes a closed polygon from the supplied points and uses it to detect and avoid restricted airspace.

Example: DescentRate = 10

Data Types: double

Maximum altitude of the no-fly zone, specified as a scalar numeric. You use this value with the NFZ boundary to determine whether obstacle avoidance is required. If the aircraft altitude is above the specified no-fly-zone altitude bound, the aircraft is permitted to pass through the NFZ without rerouting.

Example: DescentRate = 10

Data Types: double

Output Arguments

collapse all

Trajectory reference signals, returned as a timeseries struct or timetable object.

Algorithms

Use Aero.trajectory.tracklineTrajectory to define the parameters of a trackline trajectory.

Use Aero.trajectory.tracklineTrajectory with no return.

Version History

Introduced in R2026a

expand all