docs: comparing slam algorithms

[yvzksgl]

Description

Comparing SLAM algorithms listed in https://autowarefoundation.github.io/autoware-documentation/main/how-to-guides/creating-maps-for-autoware/open-source-slam/ in terms of their positional and orientational errors. For more information you can check autowarefoundation/autoware#3213

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

• I've confirmed the contribution guidelines.
• The PR follows the pull request guidelines.

In-review checklist for the PR reviewers

The Reviewers must check the checkboxes below before approval.

• The PR follows the pull request guidelines.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

• There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

[github-actions]

Documentation URL: https://autowarefoundation.github.io/autoware-documentation/pr-366/
Modified URLs:

• https://autowarefoundation.github.io/autoware-documentation/pr-366/how-to-guides/creating-maps-for-autoware/open-source-slam/compare-slam-algorithms/

[mitsudome-r]

@yvzksgl Thanks for the PR.
I think the content of the document is okay, but could you explain a bit more detail about the purpose of this document? Do you want to encourage users to use the SLAM algorithms. with best performance? Or Do you just want to share the instruction about how to compare the SLAM algorithms?

I would like to have How-To-Guides to be the documentation to explain "how people can use Autoware", and if this page is only to instruct "how to compare SLAM algorithms", then we might want to place it in different place (e.g., Autoware Blog, Papers, or a PDF in Mapping WG Google Drive). We can still put the link to it from the documentation as a reference, but I would like to have the detailed page somewhere else.

[yvzksgl]

Thanks for your response. I want to develop a tool for using while deciding which slam algorithm is the best with people's their datas.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity.