ICubBrain: Difference between revisions
Line 8: | Line 8: | ||
== Operating system installation == | == Operating system installation == | ||
The chassis contains two separate machines, each one having two hard disk drive drawers. Next, we will explain how we configured the left part of the server, called '''icubbrain1'''. The settings for icubbrain2 will be just about the same, with the last octet of the IP address being 42 instead of 41. | The chassis contains two separate machines, each one having two hard disk drive drawers. Next, we will explain how we configured the left part of the server, called '''icubbrain1'''. The settings for icubbrain2 will be just about the same (unless otherwise noted), with the last octet of the IP address being 42 instead of 41. | ||
=== Boot === | === Boot === |
Revision as of 11:23, 1 July 2009
In June 2009, we installed Ubuntu 8.04 LTS Server ('Hardy Heron') on the "1U Twin" servers that are to be used as iCub Brain (hence the name). The box includes a SC808T-980 1U chassis and two twin X7DWT serverboards. Each of the two boards hosts an Intel Xeon 8-core processor. In other words, they are two independent computers, each one with its hard disk, power button, reset button.
- left half of the chassis: icubbrain1 - has Ubuntu 8.04 LTS 64bit
- right half of the chassis: icubbrain2 - has Ubuntu 8.04 LTS 32bit
For full system specifications, go here (PDF) or on the entry on tsunami.pt
Operating system installation
The chassis contains two separate machines, each one having two hard disk drive drawers. Next, we will explain how we configured the left part of the server, called icubbrain1. The settings for icubbrain2 will be just about the same (unless otherwise noted), with the last octet of the IP address being 42 instead of 41.
Boot
We booted the Ubuntu Server CD from an external USB CD drive without problems. We then had to manually confirm the usage of a 'cdrom' module within the installation (following all the default selections).
Network interface
icubbrain1 has two Gbit interfaces. First we plugged an Ethernet cable into the first one (which turns on the "1" led in the chassis front). Then, when Ubuntu asked us to choose between eth0 and eth1, we picked up eth0.
Partitions
We chose the 'Guided - use entire disk' option, which yielded the following:
size | mountpoint | filesystem |
---|---|---|
133GB | / | ext3 |
5GB | swap |
Ubuntu installation parameters
- machine name: icubbrain1
- user name: icub
- software selection: OpenSSH
Operations after first boot
- choose Main server (rather than Portugal server, which is incomplete) as the software repository. We do this by removing all the "pt." strings from /etc/apt/sources.list
- sudo apt-get update; sudo apt-get upgrade
Other operations performed
Network configuration
- manually configured the internet connection (/etc/network/interfaces):
auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 10.10.1.41 netmask 255.255.255.0 network 10.10.1.0 broadcast 10.10.1.255 gateway 10.10.1.254
- added the following lines to /etc/hosts, to enable running commands like: ping cortex1.
10.10.1.50 pc104 10.10.1.51 icubsrv 10.10.1.52 chico2 10.10.1.53 chico3 10.10.1.1 cortex1 10.10.1.2 cortex2 10.10.1.3 cortex3 10.10.1.4 cortex4 10.10.1.5 cortex5 10.10.1.41 icubbrain1 10.10.1.42 icubbrain2
Additional packages and environment variables
- Install some required packages:
sudo apt-get install gcc g++ make cmake cvs subversion ssh libace-dev libgsl0-dev libncurses5-dev gfortran
- Create a file called ~/.bash_env (used by non-interactive sessions, namely commands launched via yarprun from another machine) containing these lines:
export ICUB_DIR=/home/icub/iCub export ICUB_ROOT=$ICUB_DIR export YARP_DIR=/home/icub/yarp2 export YARP_ROOT=$YARP_DIR export PATH=$PATH:$ICUB_DIR/bin export PATH=$PATH:$YARP_DIR/bin export ICUB_ROBOTNAME=iCubLisboa01
and one of these two:
export IPOPT_DIR=/home/icub/Ipopt-3.6.1 // for icubbrain1 (manual compilation -- TO BE FIXED: TRY v3.6.0) export IPOPT_DIR=/opt/Ipopt-3.5.5-linux-x86_32-gcc4.2.4 // for icubbrain2 (pre-compiled 32 bit binaries)
- Copy all that stuff at the bottom of ~/.bashrc, too:
cat ~/.bash_env >> ~/.bashrc
- Then, before the following line of /etc/bash.bashrc
[ -z "$PS1" ] && return
add this:
# per-user environment variables (non-interactive and interactive mode) source $HOME/.bash_env
Additional RobotCub software
OpenCV
Ubuntu prepackaged version 1.0.0-4:
sudo apt-get install libcv1 libcvaux1 libcvaux-dev libcv-dev libhighgui1 libhighgui-dev opencv-doc python-opencv
iCub: downloading the repository
In /home/icub, do:
cvs -d vislab@cvs.robotcub.org:/cvsroot/robotcub co iCub
For now, don't compile iCub but start installing YARP instead. (This is the most general approach which always works. However, since this machine does not have special iCub hardware to be found by YARP, like in the case of the PC104, then in this case we could've probably compiled straight ahead.)
YARP
- Type this from the homedir (/home/icub):
cvs -d:pserver:anonymous@yarp0.cvs.sourceforge.net:/cvsroot/yarp0 login cvs -z3 -d:pserver:anonymous@yarp0.cvs.sourceforge.net:/cvsroot/yarp0 co -P yarp2 cd yarp2
- Proceed with the configuration and compilation:
ccmake .
Click 'c' when CMake starts, then enable:
CREATE_DEVICE_LIBRARY_MODULES CREATE_LIB_MATH
Click 'c' again, then choose
ENABLE_yarpmod_opencv_grabber
Click 'c' a couple of times more, until nothing happens when you do it. Now hit 'g': generate and quit.
make make test sudo make install
iCub: compiling and installing
- Off we go:
cd /home/icub/iCub ccmake . c <-- whenever necessary
- Enable these modules:
BUILD_IN_ROOT <-- it is already ON, most likely
(I don't think we need more modules here. Right?)
- And finally:
g make sudo make install
Final configuration
yarp namespace /icub