You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use ros::Time ros::Duration values in pr2_etherCAT instead of doubles or {{{struct timespec}}}.
The problem with floating point values is they will loose precision as the seconds values returned by clock_getime increases.
Even though {{{struct timespec}}} stores sec and nsec values link ros::Time Using timespec values encourages poorly written implementation of durations :
{{{
(before.tv_sec + before.tv_nsec/NSEC_PER_SECOND) - (tick.tv_sec + tick.tv_nsec/NSEC_PER_SECOND)
}}}
Use ros::Time ros::Duration values in pr2_etherCAT instead of doubles or {{{struct timespec}}}.
The problem with floating point values is they will loose precision as the seconds values returned by clock_getime increases.
Even though {{{struct timespec}}} stores sec and nsec values link ros::Time Using timespec values encourages poorly written implementation of durations :
{{{
(before.tv_sec + before.tv_nsec/NSEC_PER_SECOND) - (tick.tv_sec + tick.tv_nsec/NSEC_PER_SECOND)
}}}
trac data:
The text was updated successfully, but these errors were encountered: