[Shox-cvs] SF.net SVN: shox:[2088] trunk/conf/examples/configuration-Intro.txt

[<dir...@us...>]

Revision: 2088
          http://shox.svn.sourceforge.net/shox/?rev=2088&view=rev
Author:   dirk_held
Date:     2009-07-02 14:28:06 +0000 (Thu, 02 Jul 2009)

Log Message:
-----------
typos.

Modified Paths:
--------------
    trunk/conf/examples/configuration-Intro.txt

Modified: trunk/conf/examples/configuration-Intro.txt
===================================================================
--- trunk/conf/examples/configuration-Intro.txt	2009-07-02 13:13:23 UTC (rev 2087)
+++ trunk/conf/examples/configuration-Intro.txt	2009-07-02 14:28:06 UTC (rev 2088)
@@ -4,14 +4,14 @@
 1 locating and using sample configurations
 
 If you've downloaded ShoX, you can find several sample configurations in the 
-"shox/conf" directory. Have a look at "shox/conf/OSRdynamic.xml", which is
-used as example in this documentation. To start a simulation, you have to add 
-a new run-configuration to Eclipse (open menu  Run/Run Configurations... and 
-add a new Java Application). On the main-tab, you add the project shox 
-(depending on your choice, when creating the shox project). The main class is 
-"net.sf.shox.simulator.kernel.Simulator". In the Arguments-tab, you add the 
-configuration, you want to run, use "conf/examples/OSRdynamic.xml". To start 
-the gui, use the main-class "net.sf.shox.visual.ShoX" with no arguments.
+"shox/conf" directory. Have a look at "shox/conf/examples/OSRdynamic.xml", 
+which is used as example in this documentation. To start a simulation, you 
+have to add a new run-configuration to Eclipse (open menu  "Run/Run 
+Configurations..." and add a new Java Application). On the main-tab, you add 
+the project shox (depending on your choice, when creating the shox project). 
+The main class is "net.sf.shox.simulator.kernel.Simulator". In the Arguments-
+tab, you add the configuration, you want to run, use "conf/examples/OSRdynamic.xml". 
+To start the gui, use the main-class "net.sf.shox.visual.ShoX" with no arguments.
 
 2 sections of a configuration file
 
@@ -26,8 +26,8 @@
 
 Although each class can create its own pseudo random number generator (PRNG), 
 shox offers a central instance, which can be defined in the randomgenerator-
-section (l. 4-9). The example generator is currently the best choice. It will 
-generate a random seed for each simulation run, which is dumped on several 
+section (lines 4-9). The example generator is currently the best choice. It 
+will generate a random seed for each simulation run, which is dumped on several 
 occasions. If you only use the standard random number generator, you can
 reproduce a run to a large extend by specifying the dumped seed. Just uncomment 
 the seed parameter in line 7 and enter the value. The PRNG offers several
@@ -111,9 +111,9 @@
 
 f.) VariableDisc + PeakNoiseMangler|AddedNoiseMangler
 
-Simulates a quadratic decaying radio signal with two thresholds. One for
-the reachable distance, the other for the interference distance, by the 
-minimum needed RSSI, to have an effect.  
+Simulates a quadratic decaying radio signal with two thresholds. One for the minimum 
+needed signal strength at which a packet is still received successfully, the other 
+for the signal strength at which a transmission still interferes with other signals.  
 
 The easiest way to get some more realism, compared to the 
 example, is choice c or f. 
@@ -141,7 +141,7 @@
 2.4.2 MAC layers
 
 Likewise to the physical layer, only the dummy and the 802.11bg implementation
-are available. The 802.11bg MAC of course needs the 802.11bg physical
+are currently available. The 802.11bg MAC of course needs the 802.11bg physical
 layer and the MACdebug class works with the PhysicalDebug class.
 
 2.4.3 logical link layers
@@ -154,9 +154,9 @@
 implementation of a layer, which aggregates multiple packets to the same receiver 
 to a larger one, to reduce the overhead, when many packets are sent. To do so,
 small packets are delayed for some time and combined with other small packets
-for the same receiver, until they are sent. Although this is not a logical link task,
-this class can be used as an example, how to implement a layer and how to do
-logging and statistics.
+for the same receiver, until they are sent. Although this is not a logical link
+task, this class can be used as an example, how to implement a layer and how to 
+do logging and statistics.
 
 2.4.4 network layers
 
@@ -167,18 +167,18 @@
 
 b.) OptimalSourceRouting: Used in the example and determines the next hop by
 questioning an oracle. This class is applicable for static and for moving nodes
-and is the real dummy-implementation, since it performes real routing.
+and is the real dummy-implementation, since it performs real routing.
 
 c.) AodvNetworkLayer:  implements the aodv protocol.
 (timing parameters seem to be simulation steps, instead of seconds, thus be
-carefull, when you change the resolution of the simulation to another value)
+careful, when you change the resolution of the simulation to another value)
 
 d.) AodvmNetworkLayer: currently incomplete multipath variant of the aodv implementation.
 
 e.) Threephase: implements a geographic routing scheme.
 
 If you do not care about routing, or want to eliminate the influence of routing
-on your personal layers, you wand to analyze, use b. Implementation a makes
+on your personal layers, you want to analyze, use b. Implementation a makes
 not much sense for nontrivial setups, but d and e should be usable.
 
 2.4.5 operating system layers


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.