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

set initial pose for amcl #8

Merged
merged 1 commit into from
Mar 18, 2016

Conversation

k-okada
Copy link
Contributor

@k-okada k-okada commented Jan 5, 2016

No description provided.

@wjwwood wjwwood merged commit aa851ed into ros-planning:indigo-devel Mar 18, 2016
@wjwwood
Copy link
Contributor

wjwwood commented Mar 18, 2016

@k-okada thanks for the pr. I don't think the initial position was correct though, so I updated it when I merged. Please have a look at the indigo-devel branch if you have a chance to see if you agree.

@k-okada k-okada deleted the set_initial_pose branch March 23, 2016 05:40
k-okada added a commit to k-okada/navigation_tutorials that referenced this pull request Mar 23, 2016
@k-okada
Copy link
Contributor Author

k-okada commented Mar 23, 2016

Thanks, I should have more detail description in this pr, I'm testing this with navigation_stage move_base_amcl_2.5cm.launch and maybe you're using roslaunch navigation_stage move_base_amcl_10cm.launch, they have different initial robot position.

I have looked at both cases and turned out that initial pose of 10cm is a little bit tough, there are many obstacles and the robot can not get out of them. So I choose initial pose for 2.5cm.

In #10, I have updated as follows;

  • set same stage initial pose for 2.5cm, 5cm, 10cm
  • set appropriate amcl inital pose for them

2.5cm stage with this PR
screenshot from 2016-03-23 14 57 30

Close look of 10cm stage
screenshot from 2016-03-23 15 09 19

@k-okada k-okada mentioned this pull request Mar 23, 2016
@wjwwood
Copy link
Contributor

wjwwood commented Mar 24, 2016

You're right, I was using the 10cm version. I'll have a look at #10, thanks!

wjwwood added a commit that referenced this pull request Mar 24, 2016
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.

2 participants