-
Notifications
You must be signed in to change notification settings - Fork 22
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
Time stamp on simulated lidar #31
Comments
@olofmat nice find! Could you open a PR with this change? Also, could you update the time here:
publish_scan ?
|
Somewhat related, it might also be a good idea to publish the sim time from e.g.
after https://github.com/KTH-SML/svea/blob/main/src/svea_core/src/svea/simulators/sim_SVEA.py#L228 or to have the tf messages use current time in |
Both options sound good to me. Could you and @olofmat do a joint PR for this? |
I realized that my first approach isn't compatible with the simulated lidar fix.
since The only way I to get both of these to work together is to use the second approach where both the laser time and the transform time uses |
In
src/svea_core/src/svea/simulators/sim_lidar.py
rospy.Time.now()
is only called once in initialization. For me this lead to issues with tf transforms with the/scan
topic (as all messages had the same, and wrong, timestamp).I added
self._scan_msg.header.stamp = rospy.Time.now()
to thepublish_scan
function which made it work for me. Not sure if that is a good fix or not.@kaarmu and @frankjjiang is that a good fix or will that affect other parts of the script?
The text was updated successfully, but these errors were encountered: