-
Notifications
You must be signed in to change notification settings - Fork 531
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
Fix circular dependency with moveit_resources (PILZ/PRBT) #885
Comments
…pace due to moveit#885 (moveit#915)" This reverts commit 0b908a1.
…pace due to moveit#885 (moveit#915)" This reverts commit 0b908a1.
* Adding PRBT config * Port prbt packages to ROS 2 * Move PRBT into test_configs directory * Fix pre-commit for pilz test_config * Revert "Docker - Temporarily move moveit_resources under target workspace due to #885 (#915)" * Reset repos file entry for moveit_resources * prbt_support: drop all test code Co-authored-by: Christian Henkel <post@henkelchristian.de> Co-authored-by: Michael Görner <me@v4hn.de> Co-authored-by: Sebastian Jahr <sebastian.jahr@picknik.ai>
reopening because the "fix" PR actually states itself that this is a temporary workaround and does not work towards the solution... |
It is a solution of sorts. There is no more circular dependency. When we have time I want to migrate the tests to a different robot. Until we figure out how to have deterministic IK without depending on moveit_core we won't get away from having the test config for pilz in moveit itself. Even if we switch robots for the tests. |
But that's the symptom, not the underlying issue (no deterministic IK+robot config in MoveIt&resources).
I don't follow. As Robert explained nicely in the original issue adding the opw plugin would be a nice community contribution and would directly allow to make fanuc a deterministic IK config in moveit_resources. |
That would be a really nice contribution. This "solution" does not prevent someone from doing that. As I stated in the other issue, I don't care about this more than other things. The primary reason I don't care about this is I don't think I am the right person to try to tackle this problem, and instead I should focus on improving things that are more in my domain. |
I agree that we should get this fixed, supporting the opw plugin efforts makes a lot of sense to me. I'm fine with keeping this issue open until it's really fixed. The reason we picked this solution is to unblock all the other work that's going on. |
The reason we picked this solution is to unblock all the other work that's going on.
I'm still wondering why this blocked anything, but maybe I just did not read the correct issues...
The only thing I can find is 0b908a1 ,
which is so much less invasive than what you did now...
|
Tracking issue for the MoveIt 2 side of moveit/moveit#2947.
The text was updated successfully, but these errors were encountered: