Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Identifying valid fields in JointTrajectoryPoint message

asked 2016-01-18 13:46:56 -0500

cdsteinkuehler
3 ●1 ●1 ●2

When interpreting the JointTrajectoryPoint[] array provided by a JointTrajectory message, what mechanism is used to determine if optional fields (like velocities and accelerations) are valid and should be used when interpolating the path or are invalid and should be ignored?

Is it required that any unused fields are set to zero?

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2016-01-22 09:17:04 -0500

sedwards
1601 ●28 ●43 ●61 http://rosindustrial.swri.edu/

The JointTrajectoryPoint contains individual arrays for position, velocity, accelerations, and effort. Array types under CPP are vector types (see here). If any of these arrays are empty (i.e. vector.empty()), then they can be considered invalid.

edit flag offensive delete link

Comments

Thanks! I missed the fact the variable length message arrays include a length prefix.

cdsteinkuehler ( 2016-01-22 09:33:01 -0500 )edit

add a comment

Question Tools

1 follower

Stats

Asked: 2016-01-18 13:46:56 -0500

Seen: 201 times

Last updated: Jan 22 '16

Identifying valid fields in JointTrajectoryPoint message edit

1 Answer

Comments

Question Tools

Stats

Related questions

Identifying valid fields in JointTrajectoryPoint message