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

allow execution of empty trajectories #940

Merged

Conversation

v4hn
Copy link
Contributor

@v4hn v4hn commented Jun 5, 2018

This is useful because the plan_execution allows arbitrary callbacks
to run after successful execution of individual plan_components_.

So although the trajectory might be empty, we miss to run the
associated callbacks if we just skip the component/trajectory altogether.

This mechanism is very convenient for modular plans where some components
only invoke side effects.

@rhaschke

This is useful because the plan_execution allows arbitrary callbacks
to run after successful execution of individual plan_components_.

So although the *trajectory* might be empty we miss to run the
associated callbacks if we just skip the component/trajectory altogether.

This mechanism is very convenient for modular plans where some components
only invoke side effects.
@rhaschke rhaschke merged commit 926feef into moveit:kinetic-devel Jun 5, 2018
rhaschke pushed a commit that referenced this pull request Jun 5, 2018
This is useful because the plan_execution allows arbitrary callbacks
to run after successful execution of individual plan_components_.

So although the *trajectory* might be empty we miss to run the
associated callbacks if we just skip the component/trajectory altogether.

This mechanism is very convenient for modular plans where some components
only invoke side effects.
dg-shadow pushed a commit to shadow-robot/moveit that referenced this pull request Jul 30, 2018
This is useful because the plan_execution allows arbitrary callbacks
to run after successful execution of individual plan_components_.

So although the *trajectory* might be empty we miss to run the
associated callbacks if we just skip the component/trajectory altogether.

This mechanism is very convenient for modular plans where some components
only invoke side effects.
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

Successfully merging this pull request may close these issues.

2 participants