collaborative-robotic-sanding
collaborative-robotic-sanding copied to clipboard
swri-robotics
Collaborative Robotic Sanding Application
This currently has Eigen Alignment issues. Do not merge
The motion planning services for free space move and process planning are currently setup as services and cannot be canceled by the main application. The solution would be to convert...
The IK functionality used by the motion planner is specific to the UR10 robot and so changing to a generic IK solution that can accommodate other robots is not possible...
The GUI layout currently has several unused widgets and tabs which need to be removed since they won't be used by the application
The system shall be able to support selecting 2 to 3 different robot base positions along the rail; selecting the base location should be configurable from the GUI, suggested solutions...
The following issues/improvements are needed in the part rework task: - [x] Colorized cropped toolpaths different than the full toolpath - [ ] Colorized the outer triangles of the interactive...
Using this to compile a list of breaking changes that will need to be updated if/when we need to update to the latest Tesseract. - [x] Update transforms to link_transforms...
This seems to happen randomly when executing a trajectory. The error code returns: `"Trajectory execution message: unknown error, didn't complete trajectory"` And from some minor inspection it seems like it...
When we integrate the vision system this will not be as big a deal, but this is very irritating for this application. It looks like it was an intentional decision....
So the launch file has a check to see if the crs_support directory exists([HERE](https://github.com/swri-robotics/collaborative-robotic-sanding/blob/035b8b3fee8486bfb68dc1fdc44fe477a1ead53f/crs_support/launch/gazebo_swri_demo.launch.py#L21)). However it does not check to see if ~/.gazebo/models exists. In my case I had neither....