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

all paths start from the same origin in rviz #4

Closed
BamsaAhmed opened this issue May 1, 2023 · 5 comments
Closed

all paths start from the same origin in rviz #4

BamsaAhmed opened this issue May 1, 2023 · 5 comments

Comments

@BamsaAhmed
Copy link

when apply them in rivz all paths start from the same point, how should run them and keeping each robot from it's own start point?

@yunzc
Copy link
Member

yunzc commented May 1, 2023

Hi. Are you visualizing the trajectory of Kimera-VIO or Kimera-Multi?

@BamsaAhmed
Copy link
Author

BamsaAhmed commented May 9, 2023 via email

@yunzc
Copy link
Member

yunzc commented May 9, 2023

You can align the trajectories with the ground truth trajectories given and use the resulting transform to transform your constructed map.

@BamsaAhmed
Copy link
Author

BamsaAhmed commented May 10, 2023 via email

@yunzc
Copy link
Member

yunzc commented May 10, 2023

Apologies, I just re-read your question:

Hi I used kimera_multi dataset to implement MR-SLAM, but i don't know the starting coordinates to start running the dataset so i start all at origin coordinate (0,0,0) at rviz, this problem causes no overlap area between the trajectories or many wrong overlapped area. The final constructed map is not matched with the groundtruth map, so how can i resolve this problem? ‫

I think this is more of a fundamental problem with the MR-SLAM algorithm. I would recommend you to check out our multi-robot SLAM system, Kimera-Multi. We are able to deal with scenarios without initial calibrations on locations.
https://github.com/MIT-SPARK/Kimera-Multi

Closing this thread now because the issue is irrelevant to the datasets.

@yunzc yunzc closed this as completed May 10, 2023
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

No branches or pull requests

2 participants