-
Notifications
You must be signed in to change notification settings - Fork 154
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
Regenerated Ikfast Plugin #81
Regenerated Ikfast Plugin #81
Conversation
I suspect the plugin was regenerated with the latest version of If that is the case, this PR should be considered as not only a bug fix, but as a potentially behaviour changing (and bw-compat breaking) upgrade of the plugin. Nothing wrong with that, but I thought I'd at least point it out. |
That is correct. |
3d4e907
to
60ef460
Compare
I amended the commit message to include more details so the change logs will indicate the upgrade. Is there anything else I can do to make this more acceptable? |
Tell us how you've tested it? :) In all seriousness: my conservative-me would rather you'd regenerate the plugin using the version of However, if we feel that is too much of a hassle (considering the estimated usage of this particular pkg, our commitment to bw compatibility and semantic versioning, etc), then this PR is as acceptable as any. As long as you've sufficiently tested it, we could probably just go ahead and merge it. |
Also, btw, the fix should probably also be backported to the Hydro package, as this is really a critical bugfix. |
@Jmeyer1292, are you able to regenerate the plugin using the version of moveit_ikfast that was used to create the current version? |
@gavanderhoorn As I said in my first post, I tested by using it as the IK plugin for the moveit demo (by dragging the end effector around), and by using it in the Godel project to generate reasonable looking paths for blending. :) I will of course be happy to regenerate the plugin with whatever version you guys want: moveit/moveit_ikfast@7ca7125 is the commit corresponding to the first Moveit_ikfast version prior to the date that the current irb2400 module was last modified. Is this one okay? I will wait for your approval on the version. |
@Jmeyer1292: I think moveit/moveit@a2360256 is also ok. That would include some fixes to the generated pkg manifests (although the Basically any point in the repos history up-to the 10th of June (3a61010b) is fine. That should result the diff showing only changes to the actual FK/IK code, not the rest of the logic. |
…ersion of moveit-ikfast plugin. Fixes issue where the ik solutions and the URDF were off by 90 degrees.
c06737e
to
1e0326f
Compare
@gavanderhoorn @Levi-Armstrong Have a look. I have tested this by dragging it around using the MoveIt demo and it appears to work (in contrast to the original which turned the end effector by 90 degrees). |
Also there's an |
This looks a lot better, no changes other than to the FK/IK code. re:
|
Yea, I missed it. Once this gets merged I will remove the deprecated package for indigo and update it for hydro. @gavanderhoorn Is this ready to merge? |
Afaict, +1 from me. |
Regenerated Ikfast Plugin
As the title suggests, I reran the IKFast generation module for the 2400 and have tested it with the existing demo.launch file and with Descartes in the godel project. It appears to work as expected.