The connectingPoses
function and the
KeyPoses
and NumSegments
properties of
the driving.Path
object are not recommended. Instead, use the interpolate
function, which returns key poses, connecting poses,
transition poses, and direction changes. The KeyPoses
and
NumSegments
properties are no longer relevant.
KeyPoses
, NumSegments
, and
connectingPoses
will be removed in a future release.
In R2018a, connectingPoses
enabled you to obtain intermediate
poses either along the entire path or along the path segments that are between key
poses (as specified by KeyPoses
). Using the
interpolate
function, you can now obtain intermediate poses
at any specified point along the path. The interpolate
function
also provides transition poses at which changes in direction occur.
Update CodeRemove all instances of KeyPoses
and
NumSegments
and replace all instances of
connectingPoses
with interpolate
.
The table shows typical usages of connectingPoses
and how
to update your code to use interpolate
instead. Here,
path
is a driving.Path
object returned
by pathPlannerRRT
.
Discouraged Usage | Recommended Replacement |
---|
|
|
| interpolate does not have a direct
syntax for obtaining segment poses. However, you can sample
poses of a segment using a specified step time. For
example:
|