Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| pycram:installation [2022/05/13 10:38] – jdech | pycram:installation [2023/08/15 13:55] (current) – arthur | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | For more details, visit [[https:// | ||
| + | |||
| ====== Installing PyCRAM ====== | ====== Installing PyCRAM ====== | ||
| The setup of PyCRAM can be differentiated in four steps: | The setup of PyCRAM can be differentiated in four steps: | ||
| Line 8: | Line 10: | ||
| All dependencies are available via PyPi | All dependencies are available via PyPi | ||
| - | PyCRAM is developed and tested currently with Python3.8, Ubuntu 20.04 and ROS Noetic. | + | PyCRAM is developed and tested currently with Python3.8, Ubuntu 20.04 and ROS Noetic. |
| ===== Installing ROS ===== | ===== Installing ROS ===== | ||
| PyCRAM uses ROS for a variety of functionality, | PyCRAM uses ROS for a variety of functionality, | ||
| Line 41: | Line 42: | ||
| cd <Path to your ROS workspace> | cd <Path to your ROS workspace> | ||
| cd src/ | cd src/ | ||
| - | vcs import --input https:// | + | vcs import --input https:// |
| + | rosdep update | ||
| + | rosdep install --ignore-src --from-paths . -r | ||
| + | cd .. | ||
| + | catkin_make | ||
| </ | </ | ||
| The cloning and setting up can take several minutes. After the command finishes you should see a number of repositories in your ROS workspace. | The cloning and setting up can take several minutes. After the command finishes you should see a number of repositories in your ROS workspace. | ||
| + | < | ||
| + | <!-- | ||
| Now the last thing that needs to be done is clone the submodules of the PyCRAM repo, this is done via the following commands: | Now the last thing that needs to be done is clone the submodules of the PyCRAM repo, this is done via the following commands: | ||
| <code bash> | <code bash> | ||
| Line 52: | Line 58: | ||
| git submodule update | git submodule update | ||
| </ | </ | ||
| - | + | --> | |
| + | </ | ||
| The cloned repository contains the source code for PyCRAM as well as two short demos which demonstrate how to use it. | The cloned repository contains the source code for PyCRAM as well as two short demos which demonstrate how to use it. | ||
| Line 71: | Line 77: | ||
| < | < | ||
| sudo pip install -r requirements.txt | sudo pip install -r requirements.txt | ||
| + | sudo pip install -r src/ | ||
| </ | </ | ||
| Line 82: | Line 89: | ||
| source devel/ | source devel/ | ||
| </ | </ | ||
| + | |||
| + | ===== Using PyCRAM ===== | ||
| + | To start using PyCRAM you first need to launch the ROS launch file. This launchfile is located in the directory " | ||
| + | |||
| + | The launchfile can be started with the following command: | ||
| + | < | ||
| + | roslaunch pycram ik_and_description.launch | ||
| + | </ | ||
| + | |||
| + | What the launch file does is start a ROS master, upload the robot URDF to the parameter server as well as starting the IK solver. | ||
| + | |||
| + | ** Disclaimer ** | ||
| + | At the moment you also need a knowrob node running for PyCRAM to start. This is because while importing packages some will look for the rosprolog services. You don't need a belief state, it only requires the rosprolog services to be reachable. | ||
| + | |||
| + | |||
| < | < | ||

