The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Everything works fine, although its data topics are publishing with completely wrong timestamps (they're huge).
header:
seq: 175517
stamp:
secs: 1453724932
nsecs: 329340743
The stamp looks fine to me.
Remember that it actually represents seconds since epoch (from docs.ros.org/std_msgs/Header):
Two-integer timestamp that is expressed as:
- stamp.sec: seconds (stamp_secs) since epoch (in Python the variable is called 'secs')
- stamp.nsec: nanoseconds since stamp_secs (in Python the variable is called 'nsecs')
time-handling sugar is provided by the client library
So in your case, 1453724932 is actually Mon, 25 Jan 2016 12:28:52 GMT and some nanoseconds (converted using epochconverter.com).
| | 2 | No.2 Revision |
Everything works fine, although its data topics are publishing with completely wrong timestamps (they're huge).
header:
seq: 175517
stamp:
secs: 1453724932
nsecs: 329340743
The stamp looks fine to me.
Remember that it actually represents seconds since epoch (from docs.ros.org/std_msgs/Header):
Two-integer timestamp that is expressed as:
- stamp.sec: seconds (stamp_secs) since epoch (in Python the variable is called 'secs')
- stamp.nsec: nanoseconds since stamp_secs (in Python the variable is called 'nsecs')
time-handling sugar is provided by the client library
So in your case, 1453724932 is actually Mon, 25 Jan 2016 12:28:52 GMT and some nanoseconds (converted using epochconverter.com).
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.