Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong time output in error message #387

Open
roncapat opened this issue Jan 21, 2025 · 0 comments
Open

Wrong time output in error message #387

roncapat opened this issue Jan 21, 2025 · 0 comments

Comments

@roncapat
Copy link

Bug. Affected lines:

ROS_DEBUG_STREAM("The current lag expiration time is " << lag_expiration << ". The queued transaction with "
"timestamp " << element.stamp() << " from sensor " << element.sensor_name << " has a minimum "
"involved timestamp of " << min_stamp << ", which is " << (lag_expiration - min_stamp) <<
" seconds too old. Ignoring this transaction.");

In my setup, I got:

The current lag expiration time is 1737452656123703516. The queued transaction with timestamp 1737452655904978711 from sensor visual_odometry has a minimum involved timestamp of 1737452655904978711, which is 218724805 seconds too old. Ignoring this transaction.

Assuming timestamps in nanoseconds, we have:

1737452656123703516
Assuming that this timestamp is in nanoseconds (1 billionth of a second):
GMT: Tuesday 21 January 2025 09:44:16.123
1737452655904978711
Assuming that this timestamp is in nanoseconds (1 billionth of a second):
GMT: Tuesday 21 January 2025 09:44:15.904

so the difference of 218724805 seconds shall be instead 0.218724805 seconds.

I can submit a PR that fixes this time scale problem when printing the time difference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant