Repository Structure


  • master: the latest stable release, always tagged with a version
  • dev: the development branch where all features start from and are merged to
  • release-X.Y.Z: release candiate for version X.Y.Z with an upcoming release, receives updates for bug fixes and documentation such as change logs but usually no new features

Directory Structure

  • include/

    • C++ header files
    • set -I here
    • prefixed with project name
  • src/

    • C++ source files
  • lib/

    • python/
      • modules, e.g. for RT interfaces, pre* & post-processing
      • set PYTHONPATH here
  • examples/

    • read and write examples
  • samples/

    • example files; need to be added manually with: .travis/
  • test/

    • unit tests which are run on make test
  • .travis/

    • setup scripts for our continuous integration system
  • docs/

    • documentation files
  • cmake/

    • CMake scripts