Revision history [back]

This warning is related to your problem (I'll probably get rid of the warning in the future). The sipp and interval environments assume that waiting is allowed as a prefix to every motion primitive therefore any "wait" action specified in the motion primitive file is ignored because the planner is going to use waits wherever it needs to.

While I can't say for sure without looking at it, the likely reason (especially if your epsilon is 1, optimal) for the behavior you are seeing is that it is at least as fast if not faster to get to the goal, by waiting for the obstacles to "disappear". When the dynamic obstacle trajectories end, it is as if they disappear. If you want to make sure the planner "deals with" the dynamic obstacles instead of waiting until they disappear you have to make sure the trajectories are long enough for it to be cheaper for the robot to do what you expect than waiting for trajectories to end.

Hope that helps!