Interfacing with the toolbox

For how to add an example to the toolbox see the Adding an example page.

IMPORTANT

• The SUMO Toolbox works on any input domain (= design space = input parameter ranges) specified in the simulator configuration file by a 'minimum' and 'maximum' attribute, for each input parameter.
  • If a 'minimum' is not specified, the default value of '-1' is assumed.
  • If a 'maximum' is not specified, the default value of '+1' is assumed.
  • Example:

	<InputParameters>
		<Parameter name="a" type="real" minimum="47.0" maximum="50.0"/>
		<Parameter name="b" type="real" minimum="-20.0"/>
	</InputParameters>

• Be aware that all input values that are not in the specified input domain are trimmed, and thus not used in the modeling process.

Also remember that:

• Complex output should always be returned as 2 real values (i.e., real part and imaginary part separately).

Make sure your data source complies with these requirements. This is your responsibility.

Passing data directly

As mentioned on the Running page you pass your (input and corresponding output) data directly to the toolbox. Remember though that the dimensions of your data must still match the information in the toolbox configuration file used.

Native simulator

If your simulator is a native code or script it is expected to produce one output value per line. So every output should be on a new line, with complex outputs using two lines.

There are 2 input methods supported for native simulators: batch mode and command line mode.

In command line mode (= the default option), the inputs are given to the simulator as command line arguments. A call to a simulator in command line mode looks like (for a problem with 3 input parameters):

>> ./someSimulationCode  0.5  0.6  0.5

The code should then produce one value per output per line.

In batch mode, multiple samples can be evaluated in batches. The simulation code is called with no command line arguments (except for optional options, see below). The inputs for a batch are instead given to the simulator on standard input (stdin). First, the size of the batch (the number of samples) is placed on stdin. Then, one line is written for each sample. this means that in total, 1 + (batchSize * inputDimension) numbers are written to stdin. An example of the format looks like:

3
0.5  0.6  0.5
0.2  0.7  0.3
0.2  0.6  0.8

The executable 'someSimulationCode' must be in your path (easiest is just to place it in the <SUMO-Toolbox-installation-dir>/bin/c or the absolute path to the executable must be specified in the simulator configuration xml file.

If your xml file contains options, these will be passed to the simulator as command line arguments (both in single and batch mode). For example:

>> ./someSimulationCode  0.5  0.6  0.5  option1=value1  option2=value2  etc..

Matlab simulator

Matlab function

If your simulator is a Matlab file you just have to provide the following function to your code (for the same 3D example):

function [output1 output2 output3] = mySimulationCode(input1, input2 ,input3)
   ...
   % do the calculation

Then you just need to make sure the Matlab file is in the toolbox path (e.g., you can place it in src/matlab/examples).

Options (if present) are passed to the simulator as an extra cell array parameter:

function [output1 output2 output3] = mySimulationCode(input1, input2 ,input3, options)

where 'options' is a cell array of strings of the form:

options : {'option1','value1','option2','value2',...}

Note: since Matlab is single threaded it is impossible to execute the simulator script while modeling (and vica versa). Thus the two are done sequentially which can lead to significant slowdowns if your simulator takes a long time to execute. In that case it is best to use a native executable or script. This will change in future versions when we start using the parallel/distributed computing toolbox.

Java simulator

You can also implement your simulator as a Java class. All you need to do is write a class that implements the Simulator interface.

Options are passed as a java Properties object.

Scattered datasets

Each row should contain exactly one data point, with one column per dimension.

Gridded datasets

Gridded datasets assume that the data is spread uniformly over a grid. By making this assumption, it becomes pointless to store the sample locations as in a scattered dataset: only the outputs are stored. In order to know the grid size, you do need to specify how many samples are taken in each dimension in the simulator file. For example, a gridSize of 20,40,50 will result in a grid of 20x40x50 or a total of 40000 samples for which the outputs have to be saved on disk.