David V. Lu!!

$MOVE_BASE_NAMESPACE/DWAPlannerROS/cheat_factor 2 On Wed, Dec 4, 2013 at 4:21 PM, Hendrik Wiese [email protected]: > Ah, no, I didn't. That might be the cause. What would be a reasonable > value...

Ok. As implied by the name, cheat_factor isn't a real fix. Is your code using this fix? https://github.com/ros-planning/navigation/pull/154 On Thu, Dec 5, 2013 at 6:05 AM, Hendrik Wiese [email protected]: >...

Hey all, I spent the weekend looking at this. Can you try this branch please? https://github.com/DLu/navigation/tree/hydro_end_path_fix -DL!! On Fri, Dec 6, 2013 at 1:28 PM, Hendrik Wiese [email protected]: > Yeah,...

Dear David, Please test-compile your code before making other people try it. -David!! Seriously though, try it again after you pull the latest version. And don't worry, it juuuuuuust happens...

Dang it. Okay, try one more thing (that I really should have mentioned the first time): Same branch but set DWAPlannerROS/scaled_path_factor to 0.75. On Tue, Dec 10, 2013 at 5:41...

Ok. Sorry to hear of your troubles. You should get some sleep, and then tell me the approximate shapes of the paths you're testing, including goal orientation. Or possibly even...

I took an initial look while trying to visualize the paths in Rviz, but that wasn't working for some reason. Are the models you're using proprietary, or can you share...

Actually, I think I figured out the bag. Can you add TF and the goals to the bag? On Sun, Dec 15, 2013 at 2:47 AM, Hendrik Wiese [email protected]: >...

Were you recording the trajectory cloud as well when you made this bag? On Tue, Dec 17, 2013 at 1:14 PM, Hendrik Wiese [email protected]: > Don't mean to rush you......

Hey Hendrik, Can you email me directly at davidvlu@gmail so we can try to debug this offline? -David!! On Tue, Dec 17, 2013 at 3:00 PM, Hendrik Wiese [email protected]: >...