[numerica] README: presentation, area description

Add a general presentation at the top of the file, finish the things to
do and especially the office space area description, as well as some
fixes.

2012-numerica/README.org

@@ -1,4 +1,14 @@
-Scenarios
+OwlPS experiments at Numerica, 2012
+
+
+* Presentation
+
+These experiments were conducted at the Numerica building in
+Montbéliard, France, in the summer of 2012. Two different areas were
+tested, a room in which the environment could be controlled to some
+extent, and a floor of an office environment. The main goal of these
+experiment was to be able to test the importance of various parameters
+on the Wi-Fi signal and on the positioning results.
 
 
 * File naming convention
@@ -6,7 +16,7 @@ Scenarios
 : sS_tT_dev_YYYY-MM-DD[_info][+suffix][_similarity].extension
 
 With:
-- S :: scenario number.
+- S :: scenario number, on two digits.
 - T :: test number; for a given scenario, the first test number is 01,
        and each time the scenario is played the test number is
        incremented.
@@ -49,9 +59,6 @@ of the following:
 The following mobile terminals can be used:
 - and :: Android smartphone (Samsung Nexus S);
 - fon :: Fonera 2.0;
-- iph :: iPhone;
-- eee :: Asus EeePC 1001-PX (Atheros AR2427 Wi-Fi chipset, Linux
-         3.0.0).
 
 When received by a Fonera 2.0, the default packet size is 103 bytes for
 a positioning request, and 116 bytes for an (auto)calibration request.
@@ -95,7 +102,9 @@ the test was started. If the information is missing, one can assume
 that the temperature is controlled around 22-24°C, and the humidity
 varies from 38% to 55%.
 
-** Aggregator
+** OwlPS Configuration
+
+*** Aggregator
 
 OwlPS Aggregator is run with the default parameters as of the version
 used, with autocalibration enabled. These parameters can be found in the
@@ -121,9 +130,9 @@ At the end of a test, beware of not stopping the Aggregator too early,
 e.g. if requests are sent with long delays, or simply if the aggregate
 timeout is not reached for all the requests in memory (as of August
 2012, OwlPS Aggregator does not flush the non-aggregated requests upon
-exiting, but simply deletes them).
+exiting, but simply deletes them; this was fixed in OwlPS v1.3.4).
 
-** Listeners
+*** Listeners
 
 The OwlPS Listener program runs continuously, with the autocalibration
 activated. It is launched with the following command:
@@ -133,7 +142,7 @@ The default autocalibration parameters are used, i.e.:
 - 20 packets (-n20),
 - 25 ms between two packets (-t25).
 
-** Client
+*** Client
 
 The mobile terminal continuously sends positioning requests with the
 following parameters:
@@ -154,7 +163,11 @@ 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.
+one can use the -N parameter introduced in OwlPS v1.3.2.
+
+During a manual calibration scenario, the default OwlPS Client's values
+are used for the number of packets and the delay, i.e. 20 packets
+separated by 50 ms (-n20 -t50).
 
 The mobile terminal's antenna is vertical.
 
@@ -166,9 +179,9 @@ The mobile terminal's antenna is vertical.
   + ear (1.57 m).
 - For the altitudes higher than “floor”, when the mobile terminal is not
   carried by a human operator, it is put on a non-metallic object. In
-  our setup, the “hip” altitude is achieved by stacking a empty trash
-  (32 cm) on a cardboard box (50 cm); for the “ear” altitude, we add a
-  stack of small boxes (75 cm).
+  our setup, the “hip” altitude is achieved by stacking an empty plastic
+  trash (32 cm) on a cardboard box (50 cm); for the “ear” altitude, we
+  add a stack of small boxes (75 cm).
 - When a human operator carries the mobile terminal, the altitude of the
   terminal is 1 m (hips/belly).
 - The antenna of the mobile terminal is vertical. When the mobile
@@ -181,10 +194,10 @@ The mobile terminal's antenna is vertical.
 
 - The infrastructure (Listeners and Aggregator) must be started first
   and at least two rounds of autocalibration request done (i.e. each
-  capture point must have sent at least two autocalibration request)
+  capture point must have sent at least two autocalibration requests)
   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).
+  knows all the Listeners (cf. section Aggregator for more details).
 - In the scenarios in which a human has to move along a path, a
   metronome is set up with the tempo at which the person has to
   walk. For example, 60 bpm if the pace is of one step per second.
@@ -193,7 +206,8 @@ The mobile terminal's antenna is vertical.
 * One-room scenarios
 
 This series of scenarios is schematised in the figure
-[[./figures/room.svg]].
+[[./figures/room.svg]]. (You can play with the layers to hide or display
+various elements.)
 
 ** Testing area
 
@@ -537,10 +551,10 @@ Detailed procedure:
 The autocalibration is performed for 5 minutes, without mobile terminal
 and without human operator.
 
-** TODO Scenario 19 (mobility, two humans)
+** Scenario 19 (mobility, two humans)
 
 Repeat the scenario 17, but one of the operators carries the mobile
-terminal.
+terminal. (This scenario was not implemented.)
 
 ** Scenario 20 (manual calibration)
 
@@ -582,12 +596,46 @@ standard altitudes become:
 
 ** Testing area
 
-*** TODO Area description
+*** Area description
+
+The floor used is the second floor of the west wing of the Numérica
+building, which is the office space of the OMNI team of the DISC
+department of FEMTO-ST (formerly LIFC). The plan of this area is
+presented in the figure [[./figures/offices.svg]]. It is mainly composed of
+four offices of identical sizes, and of two bigger rooms that are each
+equivalent to two offices in size. All these rooms are against the west
+wall and are served by a corridor at the east. The central staircase
+allows to go up from its north side, and down from its south side.
+The inner dimensions of the floor are 9 metres (west-east) by 29 metres
+(south-north, from the south wall to the doors at the north).
+
+For historical reasons (i.e. previous experiments), the origin of the
+plan is located /outside/ the building: the inner side of the west wall
+has the coordinate 1 on the X axis, and the inner side of the south
+wall is 0.5 on the Y axis. Therefore, the positioning area is between 1
+and 10 metres on the X axis, and between 0.5 and 29 metres on the Y
+axis.
+
+The west and east walls are load-bearing walls that include big glass
+windows with metallic armatures. The central wall that separates the
+offices from the corridor is a thick partition in which are installed
+electric and network cables as well as water pipes. In contrast, the
+partition that separate one office from another is only about 10 cm
+thick. The concrete slabs that separate the floors are about 30 cm
+thick and are lined with false ceilings.
+
+In the room, various pieces of furniture are present: desks, tables,
+chairs, and metal cupboards and filing cabinets. The most clear room is
+the meeting room (room 1060 on the map), in which there are essentially
+a big table and chairs.
 
 This space's topology is described in the OwlPS Positioner's
 configuration files [[./owlps-config/offices/topology.csv]] and
 [[./owlps-config/offices/waypoints.csv]].
 
+In this area, the temperature and humidity level are measured in the
+corridor, next to the office 0180.
+
 *** Listeners
 
 The capture points are put on pieces of furniture, at an altitude of