Since colorized meshes are published directly in the voxblox rviz message format, which requires further computation in the voxblox rviz plugin, there is currently no way to save the meshes that are produced by the map-visualisation nodes, e.g. colorized by class, instance, or uncertainty.
This node is independent of the rest of the code. It simply listens to the message that is send to the rviz plugin, processes it with the same code as the plugin, and saves it as ply. Every time the visualisation parameters are changes (e.g. through service calls), the saved mesh gets updated. Once it looks good in rviz, a user can simply copy or rename the current output file to save the mesh of the current state.
Since colorized meshes are published directly in the voxblox rviz message format, which requires further computation in the voxblox rviz plugin, there is currently no way to save the meshes that are produced by the map-visualisation nodes, e.g. colorized by class, instance, or uncertainty.
This node is independent of the rest of the code. It simply listens to the message that is send to the rviz plugin, processes it with the same code as the plugin, and saves it as ply. Every time the visualisation parameters are changes (e.g. through service calls), the saved mesh gets updated. Once it looks good in rviz, a user can simply copy or rename the current output file to save the mesh of the current state.