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

kuka examples are broken #7314

Closed
RussTedrake opened this issue Oct 23, 2017 · 8 comments
Closed

kuka examples are broken #7314

RussTedrake opened this issue Oct 23, 2017 · 8 comments

Comments

@RussTedrake
Copy link
Contributor

RussTedrake commented Oct 23, 2017

After partial repairs in #7313, I still see the following state of affairs in my kuka examples directory:

How do we put better test coverage on these?

@sammy-tri
Copy link
Contributor

state_lcm_translator is broken; director is failing to load the IIWA_STATUS. possibly due to #7166?

I suspect it is due to #7166 and the fact that any directorPython you managed to load from drake-distro/build would be from back in the CMake days and wouldn't be getting lcmtypes updates.

kuka_sim_dual.pmd can't even run the simulation

Will fix and add a test.

sammy-tri added a commit to sammy-tri/drake that referenced this issue Oct 23, 2017
As noted in RobotLocomotion#7314, the dual arm simulation of the iiwa described in
kuka_sim_dual.pmd no longer works.  This fixes it by conditonally
ignoring the errors trying to find the frames to visualize, and adds a
test to confirm that the simulation works.
@sammy-tri
Copy link
Contributor

Opened #7317 to fix the dual arm simulation.

sammy-tri added a commit to sammy-tri/drake that referenced this issue Oct 23, 2017
As noted in RobotLocomotion#7314, the dual arm simulation of the iiwa described in
kuka_sim_dual.pmd no longer works.  This fixes it by conditonally
ignoring the errors trying to find the frames to visualize, and adds a
test to confirm that the simulation works.
sammy-tri added a commit to sammy-tri/drake that referenced this issue Oct 23, 2017
As noted in RobotLocomotion#7314, the dual arm simulation of the iiwa described in
kuka_sim_dual.pmd no longer works.  This fixes it by conditonally
ignoring the errors trying to find the frames to visualize, and adds a
test to confirm that the simulation works.
@sammy-tri
Copy link
Contributor

sammy-tri commented Oct 25, 2017

In light of the issue I just noted in #7024 (our prebuilt drake-visualizer can't load robot models), reviving director_ik_app.py is effectively impossible (which, uh, reduces the importance of the state translator).

Given this state of affairs, I'm not totally sure what the best thing to do is. One idea would be to create a couple of canned demos which send a canned plan to a simulation (probably single arm and dual arm versions) either by doing some IK or just recording the series of joint states and sending a trajectory. Does that sound worthwhile? Other ideas?

@RussTedrake
Copy link
Contributor Author

if the pick and place demos are coming soon from @avalenzu , then perhaps they can play that role?
i do think having a graphical interface to IK is highly desirable.

N.B. - @sammy-tri i think you might have linked to the wrong issue number above?

@sammy-tri
Copy link
Contributor

This came up in RobotLocomotion/drake-iiwa-driver#14 (comment) -- without a working directorPython built against drake, providing a graphical IK example is going to be tough. This may call for increasing the priority of #7024 (built against a fixed drake target) or finding a way to package directorPython along with the files currently in examples/kuka_iiwa_arm to deliver an example which can run alongside a binary install of drake.

@EricCousineau-TRI
Copy link
Contributor

Just to check, are these issues still relevant? This is currently marked as high-priority, would be nice to either lower the priority or close the issue if possible.

@sammy-tri
Copy link
Contributor

I think it's up to Russ to determine if the manipulation station examples are sufficient to close this ticket (I'm leaning toward "yes" on that question). I'll lower the priority at any rate.

@sammy-tri
Copy link
Contributor

I guess I should elaborate on my proposal for closing, since I don't think I mean just pressing the "close" button:

Resolve this and #7321 by removing all director-based examples and any other broken stuff.

sammy-tri added a commit to sammy-tri/drake that referenced this issue Feb 11, 2019
These haven't worked in a long time since we haven't had a version of
director with the needed functionality available.

Fixes RobotLocomotion#7314

Fixes RobotLocomotion#7321
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants