--
You received this message because you are subscribed to the Google Groups "google-cartographer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cartographer+unsub...@googlegroups.com.
To post to this group, send email to google-cartographer@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cartographer/ce7beaf2-854e-4d2f-9cef-e1c18ec29683%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Thanks for all the work. I am currently unsure about the general output of the 3D mapping framework?The core output is a trajectory in form of a protobuf. Since we throw most sensor data away at SLAM time, this is not really a suitable time to generate assets (like your octomap). Instead, once you have the trajectory, you can replay the sensor data again and pose it precisely using the trajectory in a streaming fashion.In summary:I would use cartographer_ros to build your map, save the trajectory using rosservice call /finish_trajectory foo and then run it through the assets_writer_main to get to the 3D points. There is no PointsProcessor that generates octomaps, but that should be simple to add.> For navigation purposes I want to build up an octomap, at the moment I use the topic ("/scan_matched_points2") to build up my octomap. Is there any other way, I can build up the octomap? It appears to produce a good representation of the environment.The scan_matched_points2 is the strongly downsampled points cartographer is actually using for scan matching. It is a coarse representation of your environment and might be sufficient for your octomap. Loop closing might make your map inconsistent though (since parts of the map jump). The approach above should be superior then.
On Thu, Feb 2, 2017 at 3:59 PM, Jochem Verboom <jlve...@gmail.com> wrote:
Hi,
Thanks for all the work. I am currently unsure about the general output of the 3D mapping framework? For navigation purposes I want to build up an octomap, at the moment I use the topic ("/scan_matched_points2") to build up my octomap. Is there any other way, I can build up the octomap? It appears to produce a good representation of the environment.
Kind regards,
Jochem
--
You received this message because you are subscribed to the Google Groups "google-cartographer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cartographer+unsub...@googlegroups.com.
To post to this group, send email to google-ca...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cartographer/ce7beaf2-854e-4d2f-9cef-e1c18ec29683%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi,
I managed to create the 3D point cloud file, however I can't get the point_cloud_viewer running to view it. I've filed an issue here:
https://github.com/googlecartographer/point_cloud_viewer/issues/18
Regards,
Bo
On Tuesday, March 14, 2017 at 3:59:44 PM UTC+1, Bo wrote:Hi,
First of all, great software and thanks for making it!
I'm currently simulating my robot in Gazebo. It has an IMU and a VPL-16 Puck. Like Jochem, I'm also subscribing to the "/scan_matched_points2" to generate an Octomap using the octomap_server_node.
I don't really understand your recommendation on how to do it in a better way:"I would use cartographer_ros to build your map, save the trajectory using rosservice call /finish_trajectory foo and then run it through the assets_writer_main to get to the 3D points. There is no PointsProcessor that generates octomaps, but that should be simple to add."
- What is the "assets_writer_main" and how do I use it?
- Where and How do I add the PointsProcessor?
Thanks a lot for your help!
Regards,
Bo
On Thursday, February 2, 2017 at 4:05:57 PM UTC+1, Holger Rapp wrote:
> Thanks for all the work. I am currently unsure about the general output of the 3D mapping framework?The core output is a trajectory in form of a protobuf. Since we throw most sensor data away at SLAM time, this is not really a suitable time to generate assets (like your octomap). Instead, once you have the trajectory, you can replay the sensor data again and pose it precisely using the trajectory in a streaming fashion.In summary:I would use cartographer_ros to build your map, save the trajectory using rosservice call /finish_trajectory foo and then run it through the assets_writer_main to get to the 3D points. There is no PointsProcessor that generates octomaps, but that should be simple to add.> For navigation purposes I want to build up an octomap, at the moment I use the topic ("/scan_matched_points2") to build up my octomap. Is there any other way, I can build up the octomap? It appears to produce a good representation of the environment.The scan_matched_points2 is the strongly downsampled points cartographer is actually using for scan matching. It is a coarse representation of your environment and might be sufficient for your octomap. Loop closing might make your map inconsistent though (since parts of the map jump). The approach above should be superior then.
On Thu, Feb 2, 2017 at 3:59 PM, Jochem Verboom <jlve...@gmail.com> wrote:
Hi,
Thanks for all the work. I am currently unsure about the general output of the 3D mapping framework? For navigation purposes I want to build up an octomap, at the moment I use the topic ("/scan_matched_points2") to build up my octomap. Is there any other way, I can build up the octomap? It appears to produce a good representation of the environment.
Kind regards,
Jochem
--
You received this message because you are subscribed to the Google Groups "google-cartographer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cartographer+unsubscribe...@googlegroups.com.
To post to this group, send email to google-ca...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cartographer/ce7beaf2-854e-4d2f-9cef-e1c18ec29683%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Google Germany GmbHErika-Mann-Straße 3380331 MünchenRegistergericht und -nummer: Hamburg, HRB 86891Sitz der Gesellschaft: HamburgGeschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle
--
You received this message because you are subscribed to the Google Groups "google-cartographer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cartographer+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cartographer/b64fc8c2-e7df-4341-80e1-8bacea730360%40googlegroups.com.To post to this group, send email to google-cartographer@googlegroups.com.