ISRWiki - User contributions [en]

Journals

2015-05-20T08:21:54Z

WurmD: added link to spreadsheet

More information such as average review times can be found at: [[Vislab list of journals]]

==Robotics==

*Autonomous Robots, Springer Netherlands
*International Journal on Humanoid Robot, World Scientific
*IEEE Transactions on Robotics
*Advanced Robotics, The Robotics Society of japan

==Vision / Signal Processing==

*IEEE Transactions on Image Processing
*Signal Processing, Elsevier

==Artificial Intelligence==

* IEEE Transactions on Systems, Man and Cybernetics
* Artificial Intelligence, Elsevier)
* Journal of Artificial Intelligence Research: http://www.jair.org/

==Machine Learning==

* IEEE Transactions on Pattern Analysis and Machine Intelligence (TPAMI), http://www.computer.org/portal/web/tpami
* Machine Learning, Springer: http://www.springer.com/computer/artificial/journal/10994
* IEEE Transactions on Neural Networks: http://www.ieee-cis.org/pubs/tnn/
* Journal of Machine Learning Research: http://jmlr.csail.mit.edu/

==Miscellaneous==

*Pattern Analysis and Applications, Springer
*IEEE Transactions on Intelligent Transportation Systems

Administrative checklist

2015-02-26T18:23:30Z

WurmD: /* ACTIVITIES FUNDED BY LARSyS (PLURIANUAL) BUDGET (FCT rules) */

== Funding acknowledgments ==

'''(updated 30-Jan-2012)'''

=== ACTIVITIES FUNDED BY LARSyS (PLURIANUAL) BUDGET (FCT rules) ===

<code>This work was supported by the FCT project [UID/EEA/5009/2013]</code>

=== ACTIVITIES FUNDED BY FCT PROJECTS (FCT rules) ===

<code>This work was supported by project [CONTRACT REFERENCE HERE]</code>

(example PTDC/EEA-CRO/111197/2009 MAST AM)

=== ACTIVITIES UNDER AN FCT GRANT (e.g. BII, PhD, Postdoc) ===

example (replace grant reference)

<code>Partially funded with grant SFRH/BD/0000/2006, from Fundação para a Ciência e a Tecnologia.</code>

=== EU PROJECTS ===

<code>This work was partially funded by EU Project ACRONYM</code>

Obviously if more than one funding source is involved, one needs to combine several of these references together.

Example

<code>This work was partially funded by FCT [PEst-OE/EEI/LA0009/2013] and EU Project MYGOD</code>

This is very important since the incorrect acknowledgment to the funding agency will cause ELIGIBILITY problems.

== For conference trips ==

All professors and researchers have to ask their secretariat for taking care of ''Modelo 94'' form. To do that, send her/him the following information. NOTE THAT THIS INFORMATION HAS TO BE SENT AT LEAST 15 DAYS BEFORE THE DEPARTURE DATE!
* Conference name, place, and URL
* Final version of the paper to be presented, if any
* Acceptance document (can be an email) or formal invitation
* Trip dates (departure and arrival)
* Airplane ticket cost (not needed if ticket reservation is done by them, which is the usual case)
* Additional transportation expenses estimate, if any (e.g., taxi, train, etc.)
* Whether ''ajudas de custo'' are at 100% or 70%
** 100% (=148,91EUR per day) means that it has to cover the hotel expenses, while 70% (of the previous amount) means that the hotel is paid separately
** if 70% is choosen, also indicate number of nights and nightly rate
** NOTE: according to regulations, hotel cannot be above three stars (exceptions are accepted as long as properly justified)
* Conference registration cost (with proof document, e.g. invoice or printout of registration form)

In case of being a professor at IST, one has also to contact the ''Area Científica/Secção/Departamento'' for secretariat for obtaining an authorization of leave, indicating the following information ALSO AT LEAST 15 DAYS BEFORE THE DEPARTURE DATE.
* Conference name, place, and URL
* Final version of the paper to be presented, if any
* Acceptance document (can be an email) or formal invitation
* Trip dates (departure and arrival)
* ''Modelo 94'', usually sent by ISR secretariat directly (but check for it anyway)

During the trip do not forget to:
* keep the '''boarding passes''' for all airplane legs
* bring an invoice/receipt of the conference registration, '''including''' the reference '''IST-501507930''' somewhere (the address field is usually the best place)
* bring a conference participation certificate
* a confirmation of the number of stars of the hotel
and send all these items to the ISR secretariar after the return

== Purchases ==

Send to the ISR secretariat a proposal complying with the following rules:

* FUNDING SOURCE: '''IST'''
** addressed to '''Instituto Superior Tecnico'''
** containing VAT number: '''501507930'''
** containing a proposal reference number
** with and without IVA (VAT)
** validity of 66 days (if it is omitted it is assumed to be 66 days)
** containing the delivery date
** containing the payment conditions (at least 30 days)

* FUNDING SOURCE: '''IST-ID'''
** addressed to '''IST-ID'''
** containing VAT number: '''509830072'''
** containing a proposal reference number
** with and without IVA (VAT)
** validity of 66 days (optional; if it is omitted it is assumed to be 66 days)
** containing the delivery date
** containing the payment conditions (at least 30 days)

Versão Portuguesa:
* FONTE DE FINANCIAMENTO: '''IST'''
** endereçada a '''Instituto Superior Técnico'''
** contendo o seguinte NIF: '''501507930'''
** contendo um número de proposta
** preços com e sem IVA
** validade da proposta de 66 dias (se for omitida, será assumida uma validade de 66 dias)
** contendo um prazo de entrega
** contendo as condições de pagamento (pelo menos 30 dias)

* FONTE DE FINANCIAMENTO: '''IST-ID'''
** endereçada a '''IST-ID'''
** contendo o seguinte NIF: '''509830072'''
** containing a proposal reference number
** contendo um número de proposta
** preços com e sem IVA
** validade da proposta de 66 dias (se for omitida, será assumida uma validade de 66 dias)
** contendo um prazo de entrega
** contendo as condições de pagamento (pelo menos 30 dias)

[[Códigos CPV para aquisições]]

There is a list of products (mostly office supplies) that *should* be bought via Economato's stock, not externally. The list of products can be found here: [http://nca.ist.utl.pt/files/Listagem-artigos-Economato-jan-2013.pdf Listagem-artigos-Economato-jan-2013.pdf]

== Grants ==

For requesting a grant, the following forms have to be filled-in and sent to the secretariat: '''B5''' and '''Minuta de edital'''.

The Word templates for these (and other) forms can be found here: http://drh.ist.utl.pt/bolseiros/formularios/

HDA dataset issues

2014-11-18T19:55:28Z

WurmD:

<del>== hda_sample_train_data could be increased ==</del>

<del>Person 72 appears fully visible in camera 56 in frame 259 and is not in the hda_sample_train_data 
Person 78 appears fully visible in camera 56 in frame 12 and is not in the hda_sample_train_data</del>

<del>It seems that since those two people are people that at the time needed to have their face blurred out, at the time they were not added to the training set.</del>

<del>It's probably not a good idea to change (add) stuff to hda_sample_train_data now, since there is already published results with this 250 image training set</del>

HDA new training set made. Previous one archived.

== Annotation errors ==

Ped 17 on Cam 57 in frames 425 and 426 is unoccluded (but marked occluded in the annotations, and in the allD files..., and has the masks...)

HDA dataset issues

2014-11-18T13:59:42Z

WurmD:

== hda_sample_train_data could be increased ==

Person 72 appears fully visible in camera 56 in frame 259 and is not in the hda_sample_train_data 
Person 78 appears fully visible in camera 56 in frame 12 and is not in the hda_sample_train_data

It seems that since those two people are people that at the time needed to have their face blurred out, at the time they were not added to the training set.

It's probably not a good idea to change (add) stuff to hda_sample_train_data now, since there is already published results with this 250 image training set

---

Ped 17 on Cam 57 in frames 425 and 426 is unoccluded (but marked occluded in the annotations, and in the allD files..., and has the masks...)

HDA dataset issues

2014-11-18T13:55:28Z

WurmD:

HDA dataset issues

2014-11-18T13:55:19Z

WurmD:

HDA dataset issues

2014-11-18T13:42:38Z

WurmD:

HDA dataset issues

2014-11-18T13:30:28Z

WurmD: Ped 17 on Cam 57 in frames 426 and 427 is unoccluded

== hda_sample_train_data could be increased ==

Person 72 appears fully visible in camera 56 in frame 259 and is not in the hda_sample_train_data 
Person 78 appears fully visible in camera 56 in frame 12 and is not in the hda_sample_train_data

It seems that since those two people are people that at the time needed to have their face blurred out, at the time they were not added to the training set.

It's probably not a good idea to change (add) stuff to hda_sample_train_data now, since there is already published results with this 250 image training set

---

Ped 17 on Cam 57 in frames 426 and 427 is unoccluded (but marked occluded in the annotations, and in the allD files..., and has the masks...)

2011-12-16T19:46:16Z

Temp 2010-11 iCub system update/Update YARP on icubsrv

2010-11-22T18:02:12Z

WurmD: New page: http://mediawiki.isr.ist.utl.pt/wiki/Temp_2010-11_iCub_system_update#icubsrv Previous page svn update /exports/code-pc104/yarp2 '''In pc104''' updated cmake to cmake 2.6.4 yarp i...

Temp 2010-11 iCub system update/Update YARP on Chico3

2010-11-22T17:58:53Z

WurmD:

[[http://mediawiki.isr.ist.utl.pt/wiki/Temp_2010-11_iCub_system_update#icubsrv Previous page]]

'''Backed up yarp and iCub'''

cp -r /usr/local/bin/ /usr/local/bin-YARP-backup-22Nov2010

cp -r /home/icub/YARP /home/icub/YARP-backup-22Nov2010

mkdir iCub-backup-22Nov2010

cp -r iCub iCub-backup-22Nov2010/iCub

cp -r iCub_cvs iCub-backup-22Nov2010/iCub_cvs

* Complied with suggestion and changed environment variables

export YARP_ROOT=/home/icub/YARP/yarp2

export YARP_DIR=$YARP_ROOT/build

Installed package cmake-curses-gui (ccmake), with 'sudo synaptic'

In 'ccmake $YARP_ROOT$' turn on: CREATE_GUIS, CREATE_LIB_MATH; set CMAKE_BUILD_TYPE to 'Release'

$PATH was already pointing to '/home/icub/YARP/yarp2/build/bin'

'''ALTERATION OF ''$YARP_ROOT'' TO ''$YARP_DIR'' TO BE COMMITED in ''/home/icub/iCub/scripts/yarpserver.sh'''''

Temp 2010-11 iCub system update/Update iCub on Chico3

2010-11-22T17:58:35Z

WurmD:

[[http://mediawiki.isr.ist.utl.pt/wiki/Temp_2010-11_iCub_system_update#icubsrv Previous page]]

'''Backed up iCub'''

cp -r /usr/local/bin/ /usr/local/bin-YARP-backup-22Nov2010

mkdir iCub-backup-22Nov2010

cp -r iCub iCub-backup-22Nov2010/iCub

cp -r iCub_cvs iCub-backup-22Nov2010/iCub_cvs

* Checked out

Changed environment variables to:

export ICUB_ROOT=~/iCub

export ICUB_DIR=$ICUB_ROOT/main/build

em $ICUB_DIR 'ccmake $ICUB_ROOT/main'

'make'

(no $PATH tá também o '~/iCub/icub/bin' (que já não é usado) mas não sei aonde que é adicionado isto ao PATH)

'''experimental:''' copiar do backup a pasta 'iCub/app/default'

Temp 2010-11 iCub system update

2010-11-22T17:27:10Z

WurmD: /* icubsrv */

= ToDo =

Legenda:
;[[Image:empty_bullet.png]] Not done.
;[[Image:WIP_bullet.png]] In process...
;[[Image:full_bullet.png]] Done!

== Chico3 ==

;[[Image:full_bullet.png]] Update OS packages on Chico3 :
;[[Image:full_bullet.png]] Run disk check on Chico3 (the OS wanted to do it since some time):
;[[Image:full_bullet.png]] Upgrade OS release on Chico3, from 8.04 to 10.04:
;[[Image:full_bullet.png]] [[backup-yarp|Update YARP on Chico3]]:
;[[Image:full_bullet.png]] [[Update iCub on Chico3|Update iCub on Chico3]]:

== icubbrain1 ==

;[[Image:full_bullet.png]] Update OS packages on iCubBrain 1 :
;[[Image:full_bullet.png]] Upgrade OS release on iCubBrain 1 from 8.04.2 to 10.04:
;[[Image:full_bullet.png]] Reboot iCubBrain 1 to use new kernel (SHOWS ONLY ONE CORE, WHY?):
;[[Image:full_bullet.png]] Update YARP on iCubBrain 1:
;[[Image:WIP_bullet.png]] Update iCub on iCubBrain 1:

== icubbrain2 ==

;[[Image:full_bullet.png]] Update OS packages on iCubBrain 2 :
;[[Image:full_bullet.png]] Upgrade OS release on iCubBrain 2? current is 8.04.2:
;[[Image:full_bullet.png]] Reboot iCubBrain 2 to use new kernel:
;[[Image:full_bullet.png]] Update YARP on iCubBrain 2:
;[[Image:WIP_bullet.png]] Update iCub on iCubBrain 2:

== cortex1-5 ==

;[[Image:full_bullet.png]] Update OS packages on Cortex 1-5 :
;[[Image:WIP_bullet.png]] Upgrade OS release on Cortex 1-5? current is 8.04.2:
;[[Image:empty_bullet.png]] Restart each Cortex1-5:
;[[Image:empty_bullet.png]] change settings for booting Cortex1-5 on the Cortex server, in /tftpboot/pxelinux.cfg. IT IS JUST SOME TIMING PROBLEM WITH THE MOUNTING OF HOME.:
;[[Image:empty_bullet.png]] Update YARP on Cortex 1-5, for user icub:
;[[Image:empty_bullet.png]] Update iCub on Cortex 1-5, for user icub:

== cortex6 ==

;[[Image:full_bullet.png]] Update OS packages on Cortex 6 :
;[[Image:WIP_bullet.png]] Upgrade OS release on Cortex 6? current is 8.04.2:
;[[Image:empty_bullet.png]] Update YARP on Cortex 6, for user icub:
;[[Image:empty_bullet.png]] Update iCub on Cortex 6, for user icub:

== icubsrv ==

;[[Image:full_bullet.png]] Update OS packages on icubsrv :
;[[Image:WIP_bullet.png]] [[Update YARP on icubsrv|Update YARP on icubsrv]], under the path /exports/code-pc104 and, if you will, the local 64bits version:
;[[Image:empty_bullet.png]] Update iCub on icubsrv, under the path /exports/code-pc104 and, if you will, the local 64bits version:
;[[Image:empty_bullet.png]] Check the scripts that are mounted from icubsrv to pc104 still work:

= Once everything builds =

;[[Image:empty_bullet.png]] Check that each demo works:

= Useful bits of code =

* Update packages
sudo aptitude
then click on u, U and g.

* Check which is the version of the OS that will be installed through an upgrade:
nano /etc/update-manager/release-upgrades

* Start the upgrade:
sudo do-release-upgrade

[[Category:Vislab]]

Temp 2010-11 iCub system update/Update YARP on Chico3

Temp 2010-11 iCub system update/Update iCub on Chico3

2010-11-22T16:23:44Z

WurmD:

'''Backed up iCub'''

cp -r /usr/local/bin/ /usr/local/bin-YARP-backup-22Nov2010

mkdir iCub-backup-22Nov2010

cp -r iCub iCub-backup-22Nov2010/iCub

cp -r iCub_cvs iCub-backup-22Nov2010/iCub_cvs

* Checked out

Changed environment variables to:

export ICUB_ROOT=~/iCub

export ICUB_DIR=$ICUB_ROOT/main/build

em $ICUB_DIR 'ccmake $ICUB_ROOT/main'

ligar as flags: CREATE_GUIS_GTK, CREATE_GUIS_GTKMM, CREATE_GUIS_QT

Temp 2010-11 iCub system update/Update iCub on Chico3

2010-11-22T16:21:35Z

WurmD:

Temp 2010-11 iCub system update/Update iCub on Chico3

2010-11-22T16:19:15Z

WurmD:

ICub software

2010-11-22T16:16:56Z

WurmD: /* Linux environment variables */

This article explains how to install YARP and iCub software.

== Preliminary software ==

Effective August 2009, YARP and iCub software repositories have been moved to SourceForge.net servers and must be downloaded with Subversion (SVN).

You should install an SVN client on your system if you do not have one already. For Windows, [http://tortoisesvn.tigris.org/ TortoiseSVN] is recommended. If you run Linux or other UNIX flavours, chances are high that you can just go ahead using <code>svn</code> in command line (if that is not the case, install it with <code>sudo apt-get install subversion</code> or equivalent).

Furthermore, you should install [http://www.cmake.org/ CMake]. In Linux, type <code>sudo apt-get install make cmake cmake-curses-gui</code>

== Environment variables ==

The following environment variables must be set. Since summer 2010, it is recommended that they really point to different directories on your system:
* <code>YARP_ROOT</code>: location of the yarp2 source code
* <code>YARP_DIR</code>: yarp2 build directory
* <code>ICUB_ROOT</code>: location of the iCub source code
* <code>ICUB_DIR</code>: iCub build directory

=== Windows environment variables ===

Typical choices are:
* <code>YARP_ROOT</code> = C:/yarp2
* <code>YARP_DIR</code> = C:/yarp2/build
* <code>ICUB_ROOT</code> = C:/icub
* <code>ICUB_DIR</code> = C:/icub/main/build

=== Linux environment variables ===

Typical choices are:
export YARP_ROOT=~/yarp2
export YARP_DIR=$YARP_ROOT/build
export ICUB_ROOT=~/iCub
export ICUB_DIR=$ICUB_ROOT/main/build

Create a file called <code>.bash_env</code> in your home directory and copy the above lines in there.

Then, before the following line of <code>/etc/bash.bashrc</code>
[ -z "$PS1" ] && return
add this:
# per-user environment variables (non-interactive and interactive mode)
source $HOME/.bash_env

This is not the only way to set these variables systemwide and enforce them in non-interactive mode too (needed by <code>yarprun</code>), however we recommend it.

== YARP ==

=== Browsing the yarp2 repository online ===

http://yarp0.svn.sf.net/viewvc/yarp0/trunk/yarp2/

=== Getting the yarp2 repository in Windows ===

Inside TortoiseSVN, use the file manager to browse to the location where you would like to download the code. Right click on an empty region of the window and select "SVN checkout" from the contextual menu.

Type the following string in the entry "URL of repository":

https://yarp0.svn.sourceforge.net/svnroot/yarp0/trunk/yarp2

No password or username will be required.

Note: if you use Cygwin, refer to Linux instructions instead.

=== Installing yarp2 in Windows ===

Note: all environment variables should have '/' and NOT '\' (except in the <code>PATH</code> enviroment variable)! The directories do not need to be the same as the ones presented here, just be sure to alter the environment variables correctly.

# Download ACE and GSL from http://eris.liralab.it/iCub/downloads/packages/windows/msvc8/ ; unzip them to a directory of your choice and remember it.
# If you want GUIs, download GTKMM from http://live.gnome.org/gtkmm/MSWindows and use the installer.
# Create the environment variables <code>ACE_ROOT</code>, <code>GTK_BASEPATH</code>, <code>GTKMM_BASEPATH</code>, <code>GSL_DIR</code> as follows:
#* <code>ACE_ROOT</code> is ACE dir (e.g., C:/ace_wrappers).
#* <code>GTK_BASEPATH</code> and <code>GTKMM_BASEPATH</code> is GTKMM dir (C:/gtkmm).
#* <code>GSL_DIR</code> is GSL dir (C:/gsl-1.8).
# Add this to the <code>PATH</code> environment variable: <code>%ACE_ROOT%/lib</code> (important: make sure you put it at the beginning of the <code>PATH</code> environment variable, to avoid conflicts with other existing ACE versions on the system)
# Make sure that <code>YARP_ROOT</code> and <code>YARP_DIR</code> are correctly set.
# Add this to the <code>PATH</code> enviroment variable: <code>%YARP_DIR%/bin/Release</code> (and/or <code>Debug</code>). Note: these directories will be created later
# Use CMake to build the YARP SLN files. Point the source code to the yarp2 dir, and build to the yarp2/build dir (which will be created now).
# In CMake, check the flags CREATE_DEVICE_LIBRARY_MODULES, CREATE_LIB_MATH and, optionally, CREATE_GUIS (don't uncheck anything!).
# Click: Configure, Configure, Generate.
# Go to <code>YARP_DIR</code> and open YARP.sln with Visual Studio
# Go to Build->Batch Build
# Check ALL_BUILD (Release and/or Debug) and Build!

=== Getting the yarp2 repository in Linux ===

Paste the following command in a console terminal:
svn co https://yarp0.svn.sourceforge.net/svnroot/yarp0/trunk/yarp2
This will create a new directory called '''yarp2''' that contains the software. Your environment variable <code>YARP_ROOT</code> should be set to that directory (e.g., <code>/home/yourname/yarp2</code>).

=== Compiling the yarp2 repository in Linux ===

To compile the yarp2 repository, go to <code>YARP_DIR</code> and '''generate the project files''' with the CMake program with the command
ccmake $YARP_ROOT
and you obtain a Makefile.

Having generated your project file, only the actual compilation remains to be done:
make

=== Updating the yarp2 repository in Linux ===

cd $YARP_ROOT
svn update

=== Recommended CMake flags for yarp2 ===

CMAKE_BUILD_TYPE Release
CREATE_GUIS ON
CREATE_LIB_MATH ON

=== Downloading YARP as a single file ===

If for whatever reason you cannot use SVN on a machine, or you do not want the very latest revision of the repository, you may just download a single file containing YARP here: [http://eris.liralab.it/yarp/specs/dox/download.html]. Pre-compiled binaries are also available.

== iCub ==

=== Browsing the iCub repository online ===

http://robotcub.svn.sf.net/viewvc/robotcub/trunk/iCub/

=== Getting the iCub repository in Windows ===

Inside TortoiseSVN, use the file manager to browse to the location where you would like to download the code. Right click on an empty region of the window and select "SVN checkout" from the contextual menu.

Type the following string in the entry "URL of repository":

https://robotcub.svn.sourceforge.net/svnroot/robotcub/trunk/iCub

No password or username will be required.

Note: if you use Cygwin, refer to Linux instructions instead.

=== Installing iCub in Windows ===

# Make sure that <code>ICUB_ROOT</code> and <code>ICUB_DIR</code> are correctly set.
# Install OpenCV 1.0, available at http://sourceforge.net/projects/opencvlibrary/files/ . Make sure that the variable <code>OPENCV_DIR</code> was created and add <code>%OPENCV_DIR%/bin</code> to the <code>PATH</code> environment variable.
# If you intend to use the iKin kinematics modules (normally you don't - this is only needed on servers), then download IPOPT, unzip it and create the environment variable <code>IPOPT_DIR</code>, e.g. C:\Ipopt-3.7.0-win32-msvc8-yarp
# Use CMake to build the iCub SLN files. Point the source code to the icub/main dir, and build to the icub/main/build dir (which will be created now).
# In CMake, check YARP_AUTO_LINK (not sure why?) and the modules you might want working (don't unheck anything!).
# Click: Configure, Configure, Generate.
# Go to <code>ICUB_DIR</code>, open iCub.sln
# Go to Build->Batch Build
# Check ALL_BUILD (Release and/or Debug) and Build! (sometimes frameGrabberGui2 will not compile correctly)

=== Getting the iCub repository in Linux ===

Paste the following command in a console terminal:
svn co https://robotcub.svn.sourceforge.net/svnroot/robotcub/trunk/iCub
This will create a new directory called '''iCub''' that contains the software. Your environment variable <code>ICUB_ROOT</code> should be set to that directory (e.g., <code>/home/yourname/iCub</code>).

=== Compiling the iCub repository in Linux ===

To compile the iCub repository, go to <code>ICUB_DIR</code> and '''generate the project files''' with the CMake program, typing with the command
ccmake $ICUB_ROOT/main
and you obtain a Makefile.

Having generated your project file, only the actual compilation remains to be done:
make

=== Updating the iCub repository in Linux ===

cd $ICUB_ROOT
svn update

=== Recommended CMake flags for iCub ===

CMAKE_BUILD_TYPE Release

=== Downloading iCub snapshot files ===

Periodic snapshots of the iCub repository are available at http://eris.liralab.it/iCub/downloads/src/

Note that there are two types of files:
* iCub-src-x.y.z.tar.gz: the whole iCub repository, version x.y.z
* iCub-dep-x.y.z.txt: a list of the libraries, software packages and environment variables that are required to compile the code in snapshot x.y.z, including YARP version number.

== iCub Simulator ==

This component is optional. Refer to the official iCub manual, section 9 (Software), subsection 6 (Simulators), available at http://eris.liralab.it/wiki/Manual#Nine._Software.2C_iCub

=== Installing iCub_SIM in Windows ===

# Download SDL (Simple DirectMedia Layer) from http://www.libsdl.org/ (Development Libraries), unzip it somewhere and note down the directory
# Download ODE from http://eris.liralab.it/iCub/downloads/packages/windows/msvc8/, unzip it somewhere as well
# Create the environment variables <code>SDLDIR</code>, <code>ODE_DIR</code>:
#* <code>ODE_DIR</code> is ODE dir (e.g., C:/ode-0.11.1).
#* <code>SDLDIR</code> is SDL dir (C:/SDL-1.2.14).
# Add <code>%SDLDIR%/lib</code> to the <code>PATH</code> variable.
# Re-run CMake with the ODE, OPENCV and SDL variables checked.
# Compile project iCub_SIM

=== Installing iCub_SIM in Mac OS X ===

See this page created by Martin Peniak of the University of Plymouth:
http://www.martinpeniak.com/index.php?option=com_content&view=article&id=186&Itemid=131

== Committing changes to the repositories ==

If you are a developer and you need to add/modify files within the repository, you need two things:
* a SourceForge.net account; once you have that, send an email to the [http://sourceforge.net/project/memberlist.php?group_id=139262 RobotCub project administrators] to join the project
* make sure that your SVN client is configured correctly with regard to '''auto-props''', which is a mechanism that takes care of line endings and MIME filetypes according to wildcards (for example, setting some flags for *.txt files and other flags for *.sh). Go [http://www.mediawiki.org/wiki/Subversion/auto-props here] for a better explanation, and check the 'Subversion client flags' subpage (part of the official manual, linked below) for auto-props adopted by RobotCub developers.

== See also ==

* http://eris.liralab.it/wiki/Manual#Six._Software.2C_Compiling_YARP_and_iCub - official iCub manual
* http://eris.liralab.it/iCub/downloads/packages/windows/msvc8/

[[Category:Vislab]]

Temp 2010-11 iCub system update/Update iCub on Chico3

2010-11-22T16:15:37Z

WurmD:

Temp 2010-11 iCub system update

2010-11-22T16:15:10Z

WurmD: /* Chico3 */

= ToDo =

Legenda:
;[[Image:empty_bullet.png]] Not done.
;[[Image:WIP_bullet.png]] In process...
;[[Image:full_bullet.png]] Done!

== Chico3 ==

;[[Image:full_bullet.png]] Update OS packages on Chico3 :
;[[Image:full_bullet.png]] Run disk check on Chico3 (the OS wanted to do it since some time):
;[[Image:full_bullet.png]] Upgrade OS release on Chico3, from 8.04 to 10.04:
;[[Image:full_bullet.png]] [[backup-yarp|Update YARP on Chico3]]:
;[[Image:WIP_bullet.png]] [[Update iCub on Chico3|Update iCub on Chico3]]:

== icubbrain1 ==

;[[Image:full_bullet.png]] Update OS packages on iCubBrain 1 :
;[[Image:full_bullet.png]] Upgrade OS release on iCubBrain 1 from 8.04.2 to 10.04:
;[[Image:full_bullet.png]] Reboot iCubBrain 1 to use new kernel (SHOWS ONLY ONE CORE, WHY?):
;[[Image:full_bullet.png]] Update YARP on iCubBrain 1:
;[[Image:WIP_bullet.png]] Update iCub on iCubBrain 1:

== icubbrain2 ==

;[[Image:full_bullet.png]] Update OS packages on iCubBrain 2 :
;[[Image:full_bullet.png]] Upgrade OS release on iCubBrain 2? current is 8.04.2:
;[[Image:full_bullet.png]] Reboot iCubBrain 2 to use new kernel:
;[[Image:full_bullet.png]] Update YARP on iCubBrain 2:
;[[Image:WIP_bullet.png]] Update iCub on iCubBrain 2:

== cortex1-5 ==

;[[Image:full_bullet.png]] Update OS packages on Cortex 1-5 :
;[[Image:WIP_bullet.png]] Upgrade OS release on Cortex 1-5? current is 8.04.2:
;[[Image:empty_bullet.png]] Restart each Cortex1-5:
;[[Image:empty_bullet.png]] change settings for booting Cortex1-5 on the Cortex server, in /tftpboot/pxelinux.cfg. IT IS JUST SOME TIMING PROBLEM WITH THE MOUNTING OF HOME.:
;[[Image:empty_bullet.png]] Update YARP on Cortex 1-5, for user icub:
;[[Image:empty_bullet.png]] Update iCub on Cortex 1-5, for user icub:

== cortex6 ==

;[[Image:full_bullet.png]] Update OS packages on Cortex 6 :
;[[Image:WIP_bullet.png]] Upgrade OS release on Cortex 6? current is 8.04.2:
;[[Image:empty_bullet.png]] Update YARP on Cortex 6, for user icub:
;[[Image:empty_bullet.png]] Update iCub on Cortex 6, for user icub:

== icubsrv ==

;[[Image:full_bullet.png]] Update OS packages on icubsrv :
;[[Image:empty_bullet.png]] Update YARP on icubsrv, under the path /exports/code-pc104 and, if you will, the local 64bits version:
;[[Image:empty_bullet.png]] Update iCub on icubsrv, under the path /exports/code-pc104 and, if you will, the local 64bits version:
;[[Image:empty_bullet.png]] Check the scripts that are mounted from icubsrv to pc104 still work:

= Once everything builds =

;[[Image:empty_bullet.png]] Check that each demo works:

= Useful bits of code =

* Update packages
sudo aptitude
then click on u, U and g.

* Check which is the version of the OS that will be installed through an upgrade:
nano /etc/update-manager/release-upgrades

* Start the upgrade:
sudo do-release-upgrade

[[Category:Vislab]]