hersh

Thanks for writing go.matrix and making it available! I needed an SVD that worked for m

TrajectoryExecutionManager has two parallel (redundant?) paths for sending a trajectory out to be executed and waiting for it to finish. One of them does not work as it should. I...

benchmarks_gui: selecting a reachability query point when more than one point exists moves other point.

3

For example, if I have 2 points: ``` A b ``` where capital indicates selected-ness, and I click in the 3D view on "b", something like this will result: ```...

If an end-effector is not specified, it should be automatically configured from remaining links.

2

I did not initially realize that an end-effector needed to be specified, so was frustrated trying to use the tools. @sachinchitta says that it should actually be able to automatically...

First time I loaded my robot's .urdf and .srdf files, the GUI had nothing in the "planning group" dropdown and nothing worked. I just reloaded the .urdf and .srdf and...

The checkboxes called "show x", y, and z start in an incorrect default state (off, off, on). All axis arrows are shown by default, so the checkboxes should all start...

A planning group filled with joints doesn't work, same group defined with chain works fine.

3

Following the tutorial http://moveit.ros.org/wiki/PR2/Setup_Assistant/Quick_Start I created a moveit config for PR2 which did not work. When I compared the resulting config with the official pr2_moveit_config, I saw that the tutorial...

This is a duplicate of https://github.com/ros-planning/moveit_setup_assistant/issues/58, but should be addressed in all GUIs. Here I'm specifically thinking of benchmarks_gui, but could affect others too I expect.

benchmarks_gui: simplify finding URDF and SRDF

2

Loading a robot in benchmarks_gui requires opening a .urdf file and a .srdf file. - setup assistant supports loading a .xacro instead of a .urdf, but benchmarks_gui requires .urdf. Should...

In the keybinding example in the readme, the command is listed as "toggle", not "settings.cycle" as it should be. I guess this was left over from the original toggle extension's...