Installation
Introduction
This page will walk you through the toolbox installation. Please refer to the system requirements first. See the downloading section on how to download the toolbox.
File structure
When you have unzipped the toolbox the directory structure is as follows:
- <installation directory>
- bin/ : binaries, executable scripts, ...
- config/ : configuration files, location of default.xml
- doc/ : some documentation
- doc/apidoc : Javadoc and other api docs
- lib/ : required libraries (eg: dom4j)
- output/ : all output will be placed here, including your logfile
- src/ : all source code
- src/c : C/C++ code for example simulators
- src/matlab/examples : matlab example simulator scripts
- examples/ : example simulator xml files (you can test with these problems)
Installation from Source
For a minimal system you will have to compile at least the java files. Instructions depend on your operating system.
Linux/Unix/OSX
- Ensure you have the following environment variables set:
- MATLABDIR=/path/to/your/matlab/installation
- JAVA_HOME=/path/to/your/SDK/installation
- Go to toolbox root directory and type 'make'. This will build everything for you (java files, C/C++ files, SVM libraries, binaries for the txt datasets, ...). If you only want to build the java stuff simply 'make java' (or, for versions 4.1 and earlier, run 'ant') in the toolbox root.
Windows
- Compiling java:
- it is advised you do this using Eclipse (www.eclipse.org). Run eclipse, and import the build.xml file.
- Set the output directory to <SUMO-toolbox-installation-dir>/bin/java (see project->properties->Build Path). Once this is done eclipse will automatically compile the java files for you and place them into the right directory.
Note: if you get errors about a missing jmi.jar, you can find this jar file in <your matlab directory>/java/jar
- Compiling C/C++ codes (examples):
- You will have to do this on your own using a C/C++ compiler of your choice: Dev-c++/Visual Studio/...
- Compiling SVM libraries:
- In order to use the LS-SVM based modellers, you will have to compile the SVM libraries.
- This can be done using the built-in LCC compiler of matlab, by calling 'makeLSSVM' from the Matlab command prompt. This will only work if the toolbox is already in the path of Matlab. If this is not the case, refer to the Binary Installation section for more information.
Binary Installation
Starting the toolbox is very easy, all you basically have to do is run startup.m in Matlab under the toolbox installation directory.
Macintosh OSX
Follow the instructions for Windows, although the Unix/Linux instructions will work as well.
Linux/Unix
Navigate to the toolbox installation directory and start matlab there OR start matlab, once in matlab navigate to the toolbox installation directory and run 'startup.m'.
Windows
Start matlab, once in matlab navigate to the toolbox installation directory and run 'startup.m'
Side Note: if you dont want to run the toolbox in its own directory you will need to make sure Matlab will be able to find the source files for the toolbox regardless of path. This can be accomplished as follows:
- Copy startup.m (found in the toolbox root directory), to the work directory of Matlab (e.g.: C:\Program files\MATLAB\R2006b\work)
- Open startup.m (This file will be executed automatically whenever Matlab boots)
- Edit the path so that it points to the toolbox root directory (i.e., where you unzipped the toolbox).
- Reboot Matlab.
Test run
- Make sure that you are in the toolbox root directory and you have run 'startup.m' (see above)
- Type 'go' and press enter.
- The toolbox will start to model the Academic2DTwice simulator. This simulator has 2 inputs and 2 outputs, and will be modeled using Rational functions, scored using crossvalidation, and samples selected using the gradient sample selection method.
- To see the exact settings used open config/default.xml. Feel free to edit this file and play around with the different options.
The examples directory contains many example simulators that you can use to test the toolbox with. See the configuration section on information about the possible options.
Problems
See the reporting problems page.