Changes between Version 30 and Version 31 of OverSimDevelop

Timestamp:

Sep 10, 2009, 1:56:33 PM (15 years ago)

Author:

Ingmar Baumgart

Comment:

--

OverSimDevelop

@@ -591 +591 @@
 [General]
 // set all simulations to last 1000 seconds
-sim-time-limit = 1000s
+measurement-time = 1000s
 
 // this is a module path! do not confuse with parameter paths.
@@ -597 +597 @@
 }}}
 
-Now, unless specified otherwise, all configurations will use [http://www.oversim.org/chrome/site/doc/neddoc/oversim.underlay.simpleunderlay.SimpleUnderlayNetwork.html SimpleUnderlayNetwork] as their network. Notice that the value of "network" is a module path, which represents the location of the ned file, and not a parameter path.
-
-Further on networks, there are two base networks: SimpleUnderlay and Ipv4Underlay. !SimpleUnderlay is a simplified flat network where each node is assigned coordinates, packet latencies are calculated based on the distance of the source and destination node coordinates, and each nodes are directly connected to one another. Ipv4Underlay emulates real-life networks and contain hierarchies of nodes, routers, and backbones. Network modules can be accessed under the names of !SimpleUnderlayNetwork for !SimpleUnderlay and Ipv4Network for Ipv4Underlay. 
+Now, unless specified otherwise, all configurations will use SimpleUnderlayNetwork as their network. Notice that the value of "network" is a module path, which represents the location of the ned file, and not a parameter path.
+
+Further on networks, there are two base networks: SimpleUnderlayNetwork and InetUnderlayNetwork. !SimpleUnderlay is a simplified flat network where each node is assigned coordinates, packet latencies are calculated based on the distance of the source and destination node coordinates, and each nodes are directly connected to one another. Ipv4Underlay emulates real-life networks and contain hierarchies of nodes, routers, and backbones. Network modules can be accessed under the names of SimpleUnderlayNetwork for !SimpleUnderlay and InetUnderlayNetwork for !InetUnderlay. 
 
 Now, 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.
 
-The churn type tells OverSim how often it should add or delete nodes from the network. There are many churn types (e.g. NoChurn for a static network, LifetimeChurn for creating nodes with a given lifetime distribution, and so on); for a complete list see the ned files in !OverSim/src/common. In our example, we'll use the less interesting NoChurn, which disables churn in our network. There are plenty of examples in !OverSim/simulations/omnetpp.ini for all churns.
+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.
 
 The 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.
@@ -664 +664 @@
 #!cpp
 ...
-**.application.sendPeriod = ${Period=1s, 2s, 5s}
+**.application.sendPeriod = ${Period=1, 2, 5}s
 }}}