fix minjerk interpolation sometimes returns large acceleration #596
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes jsk-ros-pkg/jsk_pr2eus#457
#f(0) #f(1) #f(2) #f(3)
, if your data is#f(0) #f(1) #f(0) #f(1)
, veocity of all sample point is #f(0), so default velocity/acceleration data works.↓ without velocity and acceleration data

↓ with velocity and acceleration data

time-list
is not algined withdt
,(draw-grph 0.001)
,(draw-grph 0.0013)
,(draw-grph 0.005)
ofhttps://gist.github.com/k-okada/c575606258a822971e3dc6dbe3eb337e is as follows.
note: @708yamaguchi
angle-vector-sequence
with MoveIt! and then use minjerk interpolator to create the data, but did you try create interpolated data from normal euslisp style input like(send *ri* :angle-vector (send *robot* :reset-pose))
?. I think we should test this case as a first try, because it is a much simpler case.c.f. https://github.com/jsk-ros-pkg/jsk_pr2eus/blob/a228cc7d3bb5b26b92ed25c7d55f32a64d9d7825/pr2eus/robot-interface.l#L567-L576, RethinkRobotics/baxter_interface#72