close Warning: BrowserModule failed with ConfigurationError: Look in the Trac log for more information.

Changes between Version 31 and Version 32 of OverSimDevelop


Ignore:
Timestamp:
Sep 10, 2009, 1:57:59 PM (15 years ago)
Author:
Ingmar Baumgart
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OverSimDevelop

    v31 v32  
    603603Now, once the network type has been set, we can set the parameter values that we'll need. For example, let's create a configuration called "Example". There are two basic parts that should be configured: the churn type, and the node parameters.
    604604
    605 The churn generator tells OverSim how often it should add or delete nodes from the network. There are several different churn generators (e.g. NoChurn for a static network, LifetimeChurn for creating nodes with a given lifetime distribution, and so on); for a complete list look at OverSimChurn. In our example, we'll use NoChurn, which disables churn in our network. There are plenty of examples in !OverSim/simulations/omnetpp.ini for using other churn generators.
     605The churn generator tells !OverSim how often it should add or delete nodes from the network. There are several different churn generators (e.g. NoChurn for a static network, LifetimeChurn for creating nodes with a given lifetime distribution, and so on); for a complete list look at OverSimChurn. In our example, we'll use NoChurn, which disables churn in our network. There are plenty of examples in !OverSim/simulations/omnetpp.ini for using other churn generators.
    606606
    607607The second part are the node parameters. Two node parameters are obligatory: tier1Type (to specify the application module), and overlayType (for the overlay module). Further parameters can be specified for these application and overlay modules. For this example, we'll use the module !MyOverlayModules, which we declared in a previous chapter.