rtsprofile package from rtsprofile repo


Third-Party Package

This third-party package's source repository does not contain a package manifest. Instead, its package manifest is stored in its release repository. In order to build this package from source in a Catkin workspace, please download its package manifest.

Package Summary

Tags No category tags.
Version 2.0.0
License EPL
Build type CMAKE

Repository Summary

Checkout URI https://github.com/gbiggs/rtsprofile.git
VCS Type git
VCS Version 2.0.0
Last Updated 2010-06-01
CI status No Continuous Integration
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

Additional Links


  • Kei OKada
  • Isao Isaac Saito


  • Geoffrey Biggs

rtsprofile is a Python library providing an interface to the RT System Profile
specification. This specification describes a complete RT system and can be
used to reconstruct that system at a later time. The library supports both XML
and YAML formatted files.

This software is developed at the National Institute of Advanced Industrial
Science and Technology. Approval number H22PRO-1141. The development was
financially supported by the New Energy and Industrial Technology Development
Organisation Project for Strategic Development of Advanced Robotics Elemental
Technologies.  This software is licensed under the Eclipse Public License -v
1.0 (EPL). See LICENSE.txt.


rtsprofile uses the new string formatting operations that were introduced in
Python 2.6. It will not function with an earlier version of Python. It has not
been tested with Python 3 and it is likely that several changes will be
necessary to make it function using this version of Python.

For Ubuntu users, if you are using a version of Ubuntu prior to 9.04, you will
need to install a suitable Python version by hand. You may want to consider
upgrading to Ubuntu 9.04 or later (10.04 offers LTS).


There are several methods of installation available:

1. Download the source from either the repository (see "Repository," below) or
a source archive, extract it somewhere, and install it into your Python

 a. Extract the source, e.g. to a directory /home/blag/src/rtsprofile

 b. Run setup.py to install rtsprofile to your default Python installation:

    $ python setup.py install

 c. If necessary, set environment variables. These should be set by default,
    but if not you will need to set them yourself. On Windows, you will need to
    ensure that your Python site-packages directory is in the PYTHONPATH
    variable and the Python scripts directory is in the PATH variable.
    Typically, these will be something like C:\Python26\Lib\site-packages\ and
    C:\Python26\Scripts\, respectively (assuming Python 2.6 installed in

2. Use the Windows installer. This will perform the same job as running
   setup.py (see #1), but saves opening a command prompt. You may still need to
   add paths to your environment variables (see step c, above).

Using the library

The library has one main entry point: the RtsProfle class. Create an instance
of this class, giving the constructor just one data source. The library will
parse that source and give you a complete RT System Profile. You can then use
the properties (they're Python properties, not class methods) to access
information about the RT System. For further details, see the doxygen-generated

Running the tests

A pair of test specifications, one in each format, are included with the
library. You can execute the test on these files as below:

 $ python test/test.py ./test/rtsystem.xml
 $ python test/test.py ./test/rtsystem.yaml

Be aware that, depending on your Python paths, the tests may be executed
against an installed copy of rtsprofile rather than the copy in the current
working directory.

These tests are not yet complete coverage.

API naming conventions

rtsprofile follows the standard Python naming conventions as laid out in PEP8

Most importantly, the private, internal API functions begin with an underscore
(_). If a function begins with an underscore, it is not intended for use
outside the class and doing so could lead to undefined behaviour. Only use
those API functions that do not begin with an underscore and have a docstring
in your programs.

Further documentation and examples

For further documentation, see the Doxygen-generated API documentation.

For examples of using the library, see the "rtresurrect" and "rtcryo" tools.

Future features

The following features are planned for future releases:

- Complete unit tests.


The latest source is stored in a Git repository at github, available at
http://github.com/gbiggs/rtsprofile. You can download it as a zip file or
tarball by clicking the "Download Source" link in the top right of the page.
Alternatively, use Git to clone the repository. This is better if you wish to
contribute patches.

 $ git clone git://github.com/gbiggs/rtsprofile.git


- Fixed parsing of Message Sending nodes.
- PrecedingCondition timeout type is now integer.
- Added YAML support.
- Added tests.
- Changed the default string for Preceding conditions to "SYNC".
- Minor bug fixes


Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

Deps Name
1 catkin

System Dependencies

Dependant Packages

Launch files

No launch files found


No message files found.


No service files found


No plugins found.

Recent questions tagged rtsprofile at answers.ros.org