Some precisions

.gitignore

@@ -1,2 +1,3 @@
 *~
 .*.sw*
+results*

v1.3.1/README.org

@@ -128,6 +128,15 @@ in our setup).
 The complete command used to launch OwlPS Client is the following:
 : owlps-client -i 192.168.11.254 -n20 -t10 -F800
 
+When using a metronome, the command should be adjusted so that exactly
+one request is transmitted for each beat of the metronome. For 60 bpm
+(one request per second), the following parameters have been found to be
+almost exact:
+: owlps-client -i 192.168.11.254 -n20 -t10 -F761
+
+When a precise number of requests have to be sent during the scenario,
+one can use the -N parameter introduced in OwlPS v1.3.1-21-g5d94fe8.
+
 The mobile terminal's antenna is vertical.
 
 ** Measurement-related rules
@@ -157,9 +166,9 @@ The mobile terminal's antenna is vertical.
   before the mobile terminal is started. As a best practice, the
   measurements should start at least 10 seconds after the Aggregator
   knows all the Listeners (cf. Aggregator for more details).
-- In the scenario in which a human has to move along a path, a metronome
+- In the scenarios in which a human has to move along a path, a
-  is set up with the tempo at which the person has to walk. For example,
+  metronome is set up with the tempo at which the person has to
-  60 bpm if the pace is of one metre per second.
+  walk. For example, 60 bpm if the pace is of one step per second.
 
 
 * One-room scenarios
@@ -625,3 +634,7 @@ Timing:
 - t197 :: start walking to MP#14 (4 steps).
 - t200 :: arrived at MP#14, face the room door and wait until t210.
 - t210 and a few milliseconds :: stop the client.
+
+One request should be transmitted each second, for a total of 210
+requests. To help meeting this goal, the client can be launched with the
+-N210 option.

v1.3.1/s04/s04_j04_eee_2012-05-22.txt

@@ -1,12 +1,8 @@
-Rapport Jeu de Test 4
+Humidity: 54%
-
+Hour: 11:24
-
-Conditions :
-
-Humidité : 54
-Heure du test : 11h24
 
 taille des paquets : 103
 Puissance d'emission : 14 dBm
 
-Test effectué : Scénario 4
+/!\ The client has been launched with the standard parameter (-n20 -t10
+    -F800), therefore it transmitted less than one request per second.

v1.3.1/s04/s04_j08_fon_2012-05-22.txt

@@ -1,21 +1,17 @@
-Rapport Jeu de Test 8
+Humidity: 51%
-
+Hour: 15:35
-
-Conditions :
-
-Humidité : 51
-Heure du test : 15h35
 
 taille des paquets : 116
 
-Test effectué : Scénario 4
-
 /!\ The measurements from the mobile terminal were started too early
     after the autocalibration process started, therefore one round of
     autocalibration has not been achieved when the first measurement is
     received. For autocalibration tests, the first 3 positioning
     requests (at least) should be ignored.
 
+/!\ The client has been launched with the standard parameter (-n20 -t10
+    -F800), therefore it transmitted less than one request per second.
+
 Coordonnées exactes :
 
 Le temps t0 correspond à 1270517258.600336695, soit le moment où le

v1.3.1/s05/s05_t02_fon_2012-08-29.txt

@@ -14,5 +14,7 @@ The output files are suffixed with the number of milliseconds between
 two packets.
 The autocalibration was run only once at the beginning of the
 experiment. The output file is suffixed with “ac”.
+The number of packets of the autocalibration requests is 15 instead of
+20.
 
 Coordinates of the mobile terminal: (2.5;5.5;0).

v1.3.1/s21/s21_t01_fon_2012-09-06.txt

@@ -8,3 +8,5 @@ it is unfolded. The CP used are the one at the East: TBF06 at the North
 
 The autocalibration was used, and each file contains 28 request from
 both CPs.
+The number of packets of the autocalibration requests is 15 instead of
+20.