How to Use Parameters and Parameter files

Contents

• Parameter Overview
• Parameter Files

• The parameter names must be in the String array returned by your models getInitParam() method. For example,

  public String[] getInitParam() {
      String[] params = {"evapRate", "diffusionConstant", "maxIdealTemp",
            "minIdealTemp", "maxOutputHeat", "minOutputHeat", "worldXSize",
            "worldYSize", "numBugs"};
      return params;
  }     
  
  

  These ("evapRate", etc.) are the parameters for this model.
• The parameters must have associated get and/or set methods. If both are present the parameter is readable and writable, if only the get method is present the parameter is read-only. Get and set method are methods whose name is "get" or "set" followed by the parameter name. For example, given the above set of parameters, the model must then contain methods such as

  public void setEvapRate(double rate) {
    eRate = rate;
  }
  
  public double getEvapRate() {
    return eRate;
  }
  
  

  and so on for the rest of the parameters. All access to the parameters is through these methods and any actual variables that represent the parameters (such as eRate in the above example) remain hidden.

Many of the Repast data collection mechanisms rely on these parameters remaining constant throughout the life time of a run once the model begins to run. This does not preclude in any way changing the parameters via the user interface or parameter files, but only that these parameters are not expected to change once the model is actually running. Once the parameters are defined in this way, they can be changed through the user interface or through parameter files.

Parameter Files
Parameter files can be used with both gui and batch models. For gui models, the parameter file sets some or all initial parameter values, as if the user had entered those values by hand. For a batch model, a parameter file defines a parameter space and describes how the model should explore that space. A parameter file has the following format:

runs: x
Parameter {
 value_definition
}

where x is some number and Parameter is the name of some model parameter accessible through get and set methods. Runs specifies the number of runs to execute for the current parameter value. "runs:" is ignored for non-batch models. The value_definition is composed of one or more keywords and corresponding values.

The multi-keyword value definitions:

• "start:" the starting numerical value of a parameter.
• "end:" the ending numerical value of a parameter.
• "incr:" the amount to increment the current value of the parameter.

The start, end, and incr keywords together provide a value defintion and must always occur together. For a batch simulation they define a parameter space which will be automatically iterated through. start: defines the initial parameter. end: the parameter up to and including ending parameter, and incr: the amount to increment the start: value and any succeeding values to reach the end: parameters. For a gui simulation the start: value is taken as the default parameter and the remaining keywords are ignored.

Single keyword value_definitions:

• "set:" defines a single numerical value as a constant for the entire collection of batch runs.
• "set_list:" defines a space separated list of numerical values. A batch simluation will iterate through the list.
• "set_boolean:" defines a boolean value as a constant for the entire batch simulation. Allowed values are "true" and "false" (without the quotes).
• "set_string:" defines a string value as a constant for the entire batch simluation. The string value must not contain any white space.
• "set_boolean_list:" same as set_list but a list of boolean values (true or false).
• "set_string_list:" same as set_list but a list of string values.

For non-batch models the list keywords are equivalent to the "set:" keywords where the value is the first member of the list.

Some examples,

runs: 10
Food {
 start: 10
 end: 30
 incr: 10
}

This means start with a food parameter with a value of 10 and run the simulation 10 times using this value. Increment the food value by 10 and run the simulation 10 times with a food value of 20 (start 10 + incr 10). Increment the food value by another 10, and run another 10 times with the food value of 30 (start 10 + incr 10 + incr 10). Incrementing the current value at this point would result in a value greater than the ending value and so the simulation ends.

More than one parameter can be specified, so for example,

runs: 10
Food {
 start: 10
 end: 30
 incr: 10
}

MaxAge {
 start: 10
 end: 30
 incr: 10
}

Where both food and max age are incremented as described above. If using more than one parameter it is important to synchronize them, as whenever any parameter's current value is greater than its end value, the simulation will exit.

Parameters can also be nested. For example,

runs: 1
Food {
 start: 10
 end: 30
 incr: 10
 {
   runs: 10
   MaxAge {
     start: 0
     end: 40
     incr: 1
   }
 }
}

This example means starting with a food value of 10 run the simulation 10 times with a MaxAge of 0. Increment MaxAge by 1 and run the simulation 10 times, continue until the value of MaxAge is greater than 40. At this point, increment Food by 10 and run the simulation 10 times with a MaxAge of 0. Increment MaxAge by 1 and run the simulation 10 times. This continues until the value of Food is greater than 30. Multiple levels of nesting are possible.

Setting constants:

runs: 1
Food {
 start: 10
 end: 30
 incr: 10
 {
   runs: 10
   MaxAge {
     start: 0
     end: 40
     incr: 1
   }
 }
}
RngSeed {
 set: 1
}

RngSeed is parameter of every model and can be manipulated like any other parameter. And here it is set to one and this value will remain constant over all the individual batch runs.

List parameters:

runs: 1
Food {
 start: 10
 end: 30
 incr: 10
 {
   runs: 10
   MaxAge {
     set_list: 1.2 3 10 12 84
   }
 }
}
RngSeed {
 set: 1
}

This is the same as above except that maxAge will be incremented via the list. So first run with maxAge as 1.2, do this for 10 runs. Then set maxAge to 3 and run with this value for 10 times. Continue until the end of the list, then increment Food and start at the beginning of the MaxAge list, and so on until the Food parameter is greater than 30.

The boolean and string keywords work in an identical manner, but set boolean and string values instead of numeric ones.

Parameter files can contain comments delimited by the standard c/c++/java comment markers: '//', '/*...*/'

For more information on loading a parameter file into your model, see How Run a Simulation, The Main Method, and How To Use Multi-Run.