This makes much more sense than 1.0.0, which is counter-intuitive.
If someone is building from source they usually do it to build the
latest bleeding-edge version.
Signed-off-by: Michael Grupp <grupp@magazino.eu>
I was running through these docs and having [trouble](https://github.com/googlecartographer/point_cloud_viewer/issues/389)
with map visualization via `point_cloud_viewer`.
Notably, color is required for plys ingested by `point_cloud_viewer` (in contrast to Meshlab).
This PR adds a note to make this clear.
Signed-off-by: Erik Reed <ereed.uw@gmail.com>
If the output of cartographer should be used as an input to an additional sensor fusion method,
using the published TF transform is inconvenient or in our specific use case even harmful
because we don't want to add the raw cartographer output to our TF tree.
With this change it becomes optional to broadcast to /tf.
Morever there is an option to publish the tracked frame pose as a PoseStamped message.
We add two new optional parameters:
- `publish_to_tf` if false no tf transform is broadcasted
- `publish_tracked_pose` If set `true` a PoseStamped representing the position of the
tracked pose w.r.t. map frame is published.
If default launchers and settings are used this PR causes no change in the behavior.
Fixes broken links, code blocks and other things that
`sphinx-build docs/source docs/out -E` complained about.
Signed-off-by: Michael Grupp <grupp@magazino.eu>
* Fix build status on front page.
Changes "googlecartographer" to "cartographer-project"
for references to CI and GitHub.
Following cartographer-project/cartographer#1693.
Signed-off-by: Wolfgang Hess <whess@lyft.com>
* Remove Indigo and Lunar Dockerfiles.
I have added a few lines to the doc to alert users to remove ros abseil-cpp and also to change the rosinstall file if they wish to checkout a different version of cartographer. As discussed in #1208
This restructures the doc as a tutorial leading newcomers to becoming experimented users.
It adds pages on:
- how to get started with Cartographer on a new .bag
- how Cartographer works and can be tuned step-by-step
- how to use "extra" features of Cartographer
- how to contribute to Cartographer
It also provides some cosmethic changes with: new titles, non-indented code blocks, various illustrations, reworked paragraphs for clarity...
Other changes:
- Moved the 'Verification' paragraph in the tuning guide up,
as it fits better after the particular issue discussed before 'Special Cases'.
- Fixed 'WARNING: Title underline too short.' messages.