-
Notifications
You must be signed in to change notification settings - Fork 162
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
Homologation of ouster client for ROS / ROS 2 support #8
Comments
After, it would be good to have |
You mean making the timestamp mode configurable? If I understand the changes in the ROS2 repo correctly, we've already added that functionality here: The only part that's missing is the "fake" mode that sets timestamps based on the host clock. Happy to add that here if it's necessary. Re: splitting out ouster_client: is that really necessary if it's possible to build just the client binaries from this repo? |
Yes, but I think we added a couple of new options including using ROS time. If you've added the different modes, awesome! Just need to have all the options Tom added.
For versioning, probably it would be good software practice? For making the client code releasable for both the ROS 1 and ROS 2 drivers, yes. I can't have the ROS 2 drivers build on the build farm without it being released itself already on |
Can you use cmake FetchContent or git submodules instead of copy/paste? |
No, they do not work for the ros build farm to release binaries |
How can we combine the changes that we've made in ROS2 to enable different time sources into the ouster_client so that we can make migration between firmware version easier
The text was updated successfully, but these errors were encountered: