Skip to content
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

Add point_cloud_viewer color requirement note in asset writer doc #1424

Merged
merged 1 commit into from Oct 21, 2020

Conversation

erikreed
Copy link
Contributor

I was running through these docs and having trouble 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.

@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

ℹ️ Googlers: Go here for more info.

@erikreed
Copy link
Contributor Author

@googlebot I signed it!

@googlebot
Copy link

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@MichaelGrupp MichaelGrupp self-requested a review August 27, 2020 16:57
@MichaelGrupp
Copy link
Contributor

MichaelGrupp commented Aug 27, 2020

Thanks! Please rebase your branch to the latest master and sign off your commits. The project has switched from the Google CLA to a DCO recently

git rebase master --signoff should do the trick. See the details of the "DCO" check, it explains what you need to do.

@MichaelGrupp
Copy link
Contributor

@erikreed friendly ping

Would be nice to get this merged.

@@ -126,6 +126,7 @@ An example of such a pipeline is in `assets_writer_backpack_2d.lua`_.
.. _assets_writer_backpack_2d.lua: https://github.com/googlecartographer/cartographer_ros/blob/44459e18102305745c56f92549b87d8e91f434fe/cartographer_ros/configuration_files/assets_writer_backpack_2d.lua

Once you have the ``.ply``, follow the README of `point_cloud_viewer`_ to generate an on-disk octree data structure which can be viewed by one of the viewers (SDL or web based) in the same repo.
Note that color is required for `point_cloud_viewer` to function.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you want inline code highlighting, you need to use double backticks in RST. It's different to Markdown.

Signed-off-by: Erik Reed <ereed.uw@gmail.com>
@erikreed
Copy link
Contributor Author

Thanks for the ping -- I rebased and fixed the backticks 🍻

@MichaelGrupp MichaelGrupp merged commit 7ac49a9 into cartographer-project:master Oct 21, 2020
WLwind pushed a commit to WLwind/cartographer_ros that referenced this pull request Jan 5, 2021
…ct#1424)

I was running through these docs and having [trouble](cartographer-project/point_cloud_viewer#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>
doisyg pushed a commit to wyca-robotics/cartographer_ros that referenced this pull request Nov 18, 2021
…ct#1424)

I was running through these docs and having [trouble](cartographer-project/point_cloud_viewer#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>
Signed-off-by: Guillaume Doisy <guillaume.doisy@wyca.fr>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants