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

Wierd trajectory output #15

Open
OxDuke opened this issue May 12, 2019 · 2 comments
Open

Wierd trajectory output #15

OxDuke opened this issue May 12, 2019 · 2 comments

Comments

@OxDuke
Copy link

OxDuke commented May 12, 2019

Hi Sikang, Thank you for sharing your code. I am playing around with different parameters in the file: mpl_ros/mpl_test_node/launch/map_planner_node/test.launch. Specifically, changing start/goal positions and dt. However, sometimes rviz gives wierd trajectories:
E.g. with the following setup:

 <!-- Set start and goal -->
 <param name="goal_x" value="3.0"/>
 <param name="goal_y" value="17.0"/>
 <param name="goal_z" value="0.05"/>
 <param name="start_vx" value="0.0"/>
 <param name="start_vy" value="2.0"/>
 <param name="start_vz" value="0.0"/>
 <param name="start_x" value="12.0"/>
 <param name="start_y" value="1.5"/>
 <param name="start_z" value="0.05"/>
 <!-- Set dynamic constraints -->
 <param name="v_max" value="2.0"/>
 <param name="a_max" value="1.0"/>
 <param name="yaw_max" value="0.5"/>
 <param name="u" value="1.0"/>
 <param name="u_yaw" value="0.5"/>
 <param name="dt" value="0.25"/>
 <param name="use_3d" value="true"/>
 <param name="use_yaw" value="false"/>

Rviz gives:
Screenshot from 2019-05-11 20-22-22
My questions are:

  • Why would the trajectory not reaching the goal (I suppose the goal is the red circle)?
  • Why would there be a line segment in the middle of the trajectory?
  • Why does the line segment not having any velocity indication?
    It seems like if I use dt=1.0, the trajectory would look normal.

Thank you for your time,
Weidong

@sikang
Copy link
Owner

sikang commented May 16, 2019

Let me take a look, this bug should have been fixed long time ago....

@OxDuke
Copy link
Author

OxDuke commented Jun 8, 2019

Hi Sikang,
May I ask if the bug has been solved?

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

No branches or pull requests

2 participants