Skip to content
This repository has been archived by the owner on Nov 13, 2017. It is now read-only.

Add time factor support for trajectory time parametrization #547

Merged

Conversation

skohlbr
Copy link
Contributor

@skohlbr skohlbr commented Dec 22, 2014

This adds support for setting a motion_execution_time_factor in the MotionPlanRequest msg, which can be used to scale the velocity bounds in add_time_parametrization.

Includes necessary changes to

  • move_group
  • move_group_interface
  • Spinbox for motion planning rviz plugin

Requires other pulls requests in moveit_msgs and moveit_core which are stated below.

@@ -609,11 +609,35 @@
</sizepolicy>
</property>
<property name="maximum">
<number>1000</number>
<double>1000.000000000000000</double>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this really have changed? Seems this might be affecting something else?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll revert and test this. It appears a bit weird that the number of planning attempts is set in a QDoubleSpinBox. This should be a plain (integer) SpinBox. Maybe fodder for another (unrelated) Pull Request.

@davetcoleman
Copy link
Member

Great job with this! I implemented a similar feature just a few weeks ago, but only in moveit_core. This is much needed.

I'm not sure I like the term "motion_execution_time_factor", isn't it more a "motion_execution_velocity_factor" ? In my version I just named it 'velocity_scale'.

I'm also curious what we should do about the max acceleration limits - should it also be scaled? The same amount? This might be naive question, I haven't looked into it much though.

@davetcoleman
Copy link
Member

Could you add a quick screenshot of the UI change?

@mikeferguson
Copy link
Contributor

Hold on merging this until the moveit_msgs release makes it through the pipeline

@skohlbr
Copy link
Contributor Author

skohlbr commented Jan 9, 2015

@davetcoleman Here's a screenshot of the UI change. I think it makes the motion planning widget a little bit larger.
motion_planning_time_factor

@davetcoleman
Copy link
Member

That's what I was afraid of... the UI is already too wide IMHO. Can we name it something shorter like Velocity Scale?

@skohlbr
Copy link
Contributor Author

skohlbr commented Jan 10, 2015

I think it only got higher, not wider. Will make a tad shorter as suggested nevertheless.

@skohlbr
Copy link
Contributor Author

skohlbr commented Jan 12, 2015

Changed label from "Execution Time Factor:" to "Velocity Scaling:":
motion_planning_velocity_scaling

@davetcoleman
Copy link
Member

moveit_msgs is in shadow-fixed http://www.ros.org/debbuild/indigo.html?q=moveit_msgs

@davetcoleman
Copy link
Member

I have confirmed it slows down trajectories when displayed in REALTIME in the motion planning rviz plugin.

davetcoleman added a commit that referenced this pull request Jan 12, 2015
…uest

Add time factor support for trajectory time parametrization
@davetcoleman davetcoleman merged commit abd87d6 into moveit:indigo-devel Jan 12, 2015
@mikeferguson
Copy link
Contributor

Thanks for merging -- I'll push new releases shortly

@mikeferguson
Copy link
Contributor

Released new moveit_core in order to get this building again.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants