failed to read motion file error not resolved even after changing global costmap resolution

ros-planning / navigation_experimental

Experimental navigation techniques for ROS robots.

306 stars 140 forks source link

failed to read motion file error not resolved even after changing global costmap resolution #38

Closed sudo-panda closed 5 years ago

sudo-panda commented 5 years ago

I am getting the ERROR: failed to read motion primitive file even though I changed the global costmap resolution to 0.025 (taken from the mprim file). I have read the previous issue that pointed out the error but I do not get what other parameters in the file and my configuration of my bot are conflicting. Could you please help.

mintar commented 5 years ago

Can you upload the mprim file somewhere? Also, can you do a rosparam dump params.yaml and upload that file as well?

sudo-panda commented 5 years ago

params.yaml pr3.mprim

sudo-panda commented 5 years ago

I am no longer using this planner for my bot hence closing this issue. Thanks for helping.

trickarcher commented 5 years ago

I am facing this problem on my car-like robot. I have already used SBPL Lattice Planner with Teb Local Planner on my holonomic bot and it worked perfectly fine. But I can't seem to get past this error now. Is there any different mprim file for car-like robots?

trickarcher commented 5 years ago

It was actually my fault. I had missed the delta parameter in the gmapping param file which was essentially the resolution of the map. Matching the map resolution with the mprim resolution worked perfectly. Thanks!