Revision as of 12:01, 5 April 2013

AIRLab stores the source code of the software developed in the Lab in this Subversion repository. In order to ease code reuse, the repository must be used according to specific criteria and rules. This page describes them.

Contents of the repository

The repository is subdivided into two separate sections:

1. generic_libraries containing software packages that implement robot functionalities, in the form of libraries for general use. Each library must take the form of a stand-alone software package with its own Makefile, to be compiled separately from any software which uses it. A generic library is not intended to be used "as is". Instead, you have to set up one or more ROS nodes that use the library (see below). The source code for a "generic" ROS node template of this kind may be provided as part of the library.
2. specific_modules, containing software packages that are dedicated to specific robots (or other devices). Each package comprises one or more of the following elements:

• Special-purpose software libraries specifically dedicated to one robot or device. They provide functionalities that are too specialized for inclusion in the "generic_libraries" section.
• ROS nodes implementing one or more of the functionalities of the device. It is mandatory that each of these nodes takes the form of a ROS wrapper node: i.e., a node that does not contain data processing code, and uses instead an external library to do the processing. Such library can be a special-purpose one defined within the same module of the node, or one of the generic libraries available in the AIRLab repository. The wrapper node must give access to its capabilities to other ROS nodes through the exchange of ROS messages. If suitable predefined ROS message formats are not available, the wrapper node must also include the files that define new, suitable ROS message formats.
• ROS packages implementing the functionalities of the device that the specific_module refers to. A ROS package uses one or more of the ROS nodes defined by the module, combining them with other files (e.g., ROS "launchfiles") to define a working ROS system dedicated to managing the device.

Please note that ROS wrapper nodes are the only allowed method to access both generic and special-purpose libraries.

Structure of the repository

As already mentioned, the Development repository includes two subdirectories: Generic_Libraries and Specific_Modules. The first one contains one subdirectory for each software library, as shown by this example:

• generic_libraries
  • artoolkit
    • (library components)
    • WHATSTHIS.txt
  • brian
    • (library components)
    • WHATSTHIS.txt
  • fuzzy
    • (library components)
    • WHATSTHIS.txt
  • hokuyo
    • (library components)
    • WHATSTHIS.txt
  • joypad
    • (library components)
    • WHATSTHIS.txt
  • prosilica
    • (library components)
    • WHATSTHIS.txt
  • scare
    • (library components)
    • WHATSTHIS.txt
  • sonar
    • (library components)
    • WHATSTHIS.txt
  • xsense
    • (library components)
    • WHATSTHIS.txt
  • WHATSTHIS.txt

In every directory must be present a text file called WHATSTHIS.txt that describes the content of the directory. Every time the contents of the directory are changed, it is mandatory to check if the contents of WHATSTHIS.txt have to be updated, and perform the required changes immediately.

The Specific_Modules subdirectory of the Development repository includes one subdirectory for each special-purpose software modules. The following is an example of the type of content it includes, and refers to the Lurch autonomous wheelchair robot.

• specific_modules
  • ...

audio brian fuzzy hokuyo joypad motor odometry planner pose safety sonar vision WHATSTHIS.txt

• • wheelchair
    • audio (special-purpose software library and wrapper node)
    • brian (wrapper node for "brian" generic library)
    • emergency_batt_level (wrapper node for "airlab_remote" generic library)
    • fuzzy (wrapper node for "fuzzy" generic library)
    • hokuyo (wrapper node for "airlab_hokuyo" generic library)
    • joypad (wrapper node for "airlab_joypad" generic library)
    • misc (special-purpose software library and wrapper node)
    • motor (special-purpose software library and wrapper node)
    • odometry (special-purpose software library and wrapper node)
    • pose (special-purpose software library and wrapper node)
    • shared (special-purpose software library and wrapper node)
    • sonar (wrapper node for "airlab_sonar_board" generic library)
    • spike (wrapper node for "spike" generic library)
    • wheelchair (robot coordinator module: special-purpose software library and wrapper node)
    • wheelchair_imu (wrapper node for "airlab_xsense" generic library)
    • wheelchair_motor (special-purpose software library and wrapper node)
    • wheelchair_vision (wrapper node for "airlab_artoolkitplus" generic library)
  • ...

Rules to use the repository

Whoever develops software for AIRLab must comply with the following criteria for software design and inclusion in the Subversion repository.

Rule 1: everything must be sufficiently documented. Software is considered "sufficiently documented" only if the following condition is verified.

Any person with generic experience in robotics and programming but no idea whatsoever of what the software does must be able, after reading only the documentation provided with the software, to do all of the following:

• understand what the software is for;
• understand what each individual file belonging to the software is for;
• understand how to configure the software (if applicable);
• understand how the functionalities of the software can be used (by other software);
• compile the software.

Rule 2: a valid test application must be provided. A test application must be provided with the software. Such application is considered "valid" only if the following condition is verified.

Any person with generic experience in robotics and programming but no idea whatsoever of what the software does must be able, after reading only the documentation provided with the software, to do all of the following:

• compile and run the test application;
• understand how to configure the test application (if applicable);
• understand the functioning of the test application and interpret its output;
• verify, using only the test application, if every functionality of the software is correctly operating.

The test application must reside in a directory dedicated to it (within the software) and must have its own Makefile. Compilation of the test application must be independent from compilation of the software. It must be possible to remove the directory of the test application without any effect on the software.