-
Notifications
You must be signed in to change notification settings - Fork 1
'working' nav2 for physical robot #7
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
base: main
Are you sure you want to change the base?
Conversation
|
Doesn't need to be merged right away, maybe we need to change some launch file names |
|
@ArendJan I totally missed this PR, sorry. |
|
It's okay to merge, but according to @SuperJappie08 it's not great, some things like local/global planner |
|
it needs some improvements for it to be good, but I'm not knowledgeable in nav2 enough for that |
|
This is the diff between the param file in this repo and the param file from the 'best' MDP team with the modifications from @SuperJappie08 @fghzamani @EGAlberts It seems that the main differences are the laser range max/min values, the robot_model_type (diff -> omni), some changes to the critics, the addition of an obstacle_layer plugin to the local_costmap, an increase in the min velocity, and a decrease in the max velocity. Thoughts anyone? |
minor change .. Edit: all the topic name updates that introduce a |
|
This is the diff between the file in this PR and the one from https://github.com/SuperJappie08/mirte-demo-ensurance/blob/development/mirte_navigation/params/mirte_nav2_params.yaml |
No description provided.