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

add trajectory points when received points are few #54

Conversation

aginika
Copy link
Contributor

@aginika aginika commented Feb 14, 2015

From #53.
This Pull Request is just a kind of suggestion.

@130s
Copy link
Member

130s commented Mar 23, 2015

ping

rethink-imcmahon pushed a commit that referenced this pull request Apr 12, 2015
This commit partially resolves baxter_interface issue (#53 and #54),
where the JTAS would error out if too few points were passed into it.

There was a bug in the Bezier library which did not properly check for
two points, which this resolves. We will also pull in Aginika's commit
for adding a beginning trajectory point when there are just one.

Trac ticket #11669
rethink-imcmahon pushed a commit that referenced this pull request Apr 13, 2015
This commit partially resolves baxter_interface issue (#53 and #54),
where the JTAS would error out if too few points were passed into it.

There was a bug in the Bezier library which did not properly check for
two points, which this resolves. We can safely remove the additional
two point check in the joint trajectory action server based on this.

Trac ticket #11669
@aginika
Copy link
Contributor Author

aginika commented Apr 14, 2015

#55 covers this problem.

@aginika aginika closed this Apr 14, 2015
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