RAMSES: Installation and Use as a Standalone Application

Download the Latest Stable Version of RAMSES

Sources and binaries of the latest stable version are available ‘here’.

Download the Under-Development Version of RAMSES

Nightly builds are performed on our ‘continuous integration server’.

Sources and binaries of the latest nightly build are available ‘here’.

Install RAMSES

1) unzip the archive; let’s call “path_to_resulting_directory” the path to the resulting directory.
2) export the ramses install directory by executing the command:

$export RAMSES_DIR=path_to_resulting_directory

In order to have a stable installation, consider writing these lines of code in your $HOME/.bashrc file.

Generate Code

To run ramses, simply execute the script provided with the binary release.

$osate2-cli --help will print the list of available options:

General Configuration Usage:

[-h|--help] [--parse] [(-l|--log) ] (-m|--model) source_models1,source_models2,...,source_modelsN  [(-i|--include) include_directories1,include_directories2,...,include_directoriesN ] [--analysis] [-a[:analysis_list1,analysis_list2,...,analysis_listN ]] [(-s|--system) ] [(-o|--output) ] [(-g|--generation) ] [(-r|--runtime-path) ] [--workflow ] [(-p|--parameter) key=value1,key=value2,...,key=valueN ]

        Print help for usage

        Only parse input models

  [(-l|--log) ]
        enable the logging file and set the level (all | trace | debug | info |
        warn | error | fatal

  (-m|--model) source_models1,source_models2,...,source_modelsN 
        List of input aadl files

  [(-i|--include) include_directories1,include_directories2,...,include_directoriesN ]
        List of path to find input models

        Parse, instantiate and analyze the instance model

  [-a[:analysis_list1,analysis_list2,...,analysis_listN ]]
        List of analysis to be performed on instance model; available analysis
        identifiers are: 

  [(-s|--system) ]
        Name of the system to instantiate in input aadl files

  [(-o|--output) ]
        Directory where files will be generated

  [(-g|--generation) ]
        Targeted platform for code generation (pok, etc.).

  [(-r|--runtime-path) ]
        Path to the targeted platform runtime

  [--workflow ]
        The specified ecore file contains the workflow

  [(-p|--parameter) key=value1,key=value2,...,key=valueN ]
        additional parameters given as key=value format

To execute the generated code, see how to install and run POK on the following link.