The official installation guide is available here. For Windows and Mac, binaries are available to be downloaded. For Linux, you need to choose your distribution and follow the guide for installation from repository (recommended), .deb package, or with a convenience script.
tag
can be one of full, icub, graspit, hri
. Tag full
contains iCub, grasping and HRI related things. Tag icub
contains only iCub related software, tag graspit
contains only grasping related things and tag hri
contains HRI related software.
docker pull b3m33hro/labs:tag
<image_name>
is an arbitrary name for your image, e.g., hro_image
docker tag b3m33hro/labs:tag <image_name>
-it
is for interactive mode. -p
determines which ports will be accessible from the host system. <container_name>
is an arbitrary name of your container, e.g., hro
. -v
specifies which folder will be shared between the container and the host system (optional). <image_name>
is the name selected in the previous step.
docker run -it -p 6080:6080 -p 8888:8888 --name <container_name> -v path_to_data_folder_host_system:/root/data <image_name>
start-vnc-session.sh
http://localhost:6080
to the address bar. A window with a Linux environment should open. start-vnc-session.sh
again.choregraphe
654e-4564-153c-6518-2f44-7562-206e-4c60-5f47-5f45
sed -i 's|su -c ./naoqi-bin chore &||g' /usr/bin/choregraphe && sed -i 's|./choregraphe-bin -p 9559 --ip 127.0.0.1 --no-naoqi --no-discovery|su -c ./choregraphe-bin chore|g' /usr/bin/choregraphe
and run choregraphe
, or B) cd /opt/Aldebaran/bin
and su -c ./choregraphe-bin chore
, or C) download the newest Docker image with tag full
or hri
. Robot can be then changed in Edit→Preferences→Virtual robot
—chose Pepper V16 robot. Next time you can run only choregraphe
and Pepper will be there.
/root/Install-RoboDK
. The program can be then run with command /installation_path/RoboDK-Start.sh
(where installation_path
is /RoboDK
in default), or with Desktop icon.
docker stop <container_name>
CTRL+D
exit
docker start <container_name> docker attach <container_name>
docker exec -it <container_name> /bin/bash
docker container rm <container_name>
docker system prune -a
graspit_simulator
jupyter-notebook
. Open a browser (in container or in the host machine) and enter http://localhost:8888
and you should see Jupyter notebook interface.
fix_windows.sh
.
git clone https://gitlab.fel.cvut.cz/body-schema/teaching/b3m33hro-labs.git cd b3m33hro-labs/lab3/tutorial_cartesian-interface/smoke-test ./test.sh
In case of problems with Docker on your computer, you can use Docker on Gitpod. Gitpod allows running Docker images on their servers for free (each registered user can use 50 hours per month).
full
, check other branches of https://github.com/rustlluk/B3M33HRO-
* gitpod to open other tags
/workspace
will be saved after you stop and start the workspace again!
docker run
and others are needed
root
. If not, please run su
with password root
.
su
as the first command in each new terminal you open and use the environment as before
root
Everything should work almost the same as in the local installation, but server resources are used. However, you can not link folder from your PC as in the case of local Docker. You can either use data only in docker, or there are several ways how to share code:
/workspace
and linked to /root/workspace
-v
option in local Docker installation.
You can copy/paste things to the Gitpod workspace terminals, but you need to approve it (popup window with the question should appear after you first try to paste something).
apt update
will most probably be needed to be run first. Else you will get no package …
error.
$(lsb_release -cs)
when adding the repository, but use name of Ubuntu version corresponding to your Ubuntu kernel from Ubuntu versions.
some_path/smoke-test/fixtures/fixture.xml
in the given project you want to test and remove/comment the whole <module>
section containing gzclient
.
top
or htop
and kill it (look for anything with yarp, gz, iCartesian* etc.). However, using pkill -f gz
, pkill -f yarp
and pkill -f tutorial
should be enough in most cases to kill all Gazebo and Yarp related things.
You need to install Robotology superbuild, GraspIt!, gpd, Python 2.7 and 3.X. Optionally, ROS is needed. You can check Dockerfile to get an idea of how everything is installed.