From AIRWiki
Revision as of 22:59, 24 June 2009 by BernardoDalSeno (Talk | contribs) (Crash Course)

Jump to: navigation, search

Airpaper (authentication needed) is the repository of papers written at Airlab.

It is based on Subversion; you can find some help in configuring Subversion in the Configuring Subversion page, but you don't need the key and Ssh part as Airpaper uses Http authentication. is the repository Url when you checkout your working copy.

You have to be added as a user to the project by one of the administrators, even if you already are a user of Dei's Savane. Administrators/authors currently are: Rossella Blatt, Bernardo Dal Seno, Giulio Fontana, Matteo Matteucci, Simone Tognetti. (New administrators, please add your names here)


This is a partial structure of the repository:

  • bci: BCI-related stuff
  • benchmarking: papers related to benchmarking in robotics
  • common: common stuff
    • bib: bibliography (Bibtex files, databases and styles)
    • images: obvious
  • slam: simultaneous localization ans mapping
  • wheelchair: Lurch-related stuff

All files related to a paper should be contained in one directory; please use a name that is clear and begins with a year, e.g., 2009_Science, 2010_Nature_Higgs.

Crash Course

For a more detailed discussion see Using Subversion.

Being a subversion repository you need a subversion client to use it (rather obvious). The simplest one is a terminal client, and the following are first command you can use to start using airpaper immediately:

$ svn co

or for a subdirectory just

$ svn co

to add a new file or directory (directories are imported recursively) to the repository just execute

$ svn add <filename/dirname>

this code does not actually update the svn repository to do this you need to check-in the change with

$ svn ci <filename/dirname>

and you can use this command to check-in any change to your local file not just to import new ones.

If you just want to check if something is changed locally or remotely, you can use

$ svn stat

while to update your local version with the last changes in the repository you just need to update with

$ svn update

this command might generate conflicts you need to settle ... but this is another story and you should read it by you own from

$ svn help



For administrators

Instruction for managing users are on the page DEI Subversion Administration