Experimental measurements done with OwlPS.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

832 lines
30 KiB

9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
  1. OwlPS experiments at Numerica, 2012
  2. * Presentation
  3. These experiments were conducted at the Numerica building in
  4. Montbéliard, France, in the summer of 2012. Two different areas were
  5. tested, a room in which the environment could be controlled to some
  6. extent, and a floor of an office environment. The main goal of these
  7. experiment was to be able to test the importance of various parameters
  8. on the Wi-Fi signal and on the positioning results.
  9. * File naming convention
  10. : sS_tT_dev_YYYY-MM-DD[_info][+suffix][_similarity].extension
  11. With:
  12. - S :: scenario number, on two digits.
  13. - T :: test number; for a given scenario, the first test number is 01,
  14. and each time the scenario is played the test number is
  15. incremented.
  16. - YYYY :: year.
  17. - MM :: month.
  18. - DD :: day.
  19. - dev :: client device short name.
  20. - info :: an optional informative string can be added, for example when
  21. a scenario has to be run several times with different parameters; when
  22. not obvious, the meaning of such suffixes should be documented in the
  23. report files.
  24. - suffix :: an optional suffix can be added, separated by a +; suffixes
  25. have the following meanings:
  26. + coord :: the real coordinate were added in the file;
  27. + calib :: the file is a manual calibration file, containing
  28. calibration requests (type 1) (+coord is implied, as
  29. manual calibration requests always contain the mobile's
  30. coordinates); it can be made from real calibration
  31. requests, or from simple positioning requests with added
  32. coordinates and adapted type.
  33. - extension :: file extension:
  34. + agg :: OwlPS Aggregator output file;
  35. + txt :: experiment report;
  36. + log :: OwlPS Positioner log file (recorded at the input);
  37. + pos :: OwlPS Positioner results;
  38. + out :: OwlPS Positioner standard output;
  39. + err :: OwlPS Positioner standard error;
  40. + ods :: results formatted in a spreadsheet.
  41. For the result files, the name of the similarity algorithm used to
  42. compute the positions is added after the suffix. For now it can be one
  43. of the following:
  44. - mean,
  45. - interval,
  46. - interval2.
  47. * Client devices
  48. The following mobile terminals can be used:
  49. - and :: Android smartphone (Samsung Nexus S);
  50. - fon :: Fonera 2.0;
  51. When received by a Fonera 2.0, the default packet size is 103 bytes for
  52. a positioning request, and 116 bytes for an (auto)calibration request.
  53. Unless stated otherwise:
  54. - the Fonera is equipped with a 1.8 dBi antenna and its transmission
  55. power is 18 dBm;
  56. - the transmission power of the EeePC is 14 dBm.
  57. * Common rules
  58. Except if stated otherwise, all the scenarios follow these rules (or
  59. should follow them for future tests). The description of the scenarios
  60. has precedence over these common rules. Moreover, the report files
  61. associated with each test should also warn about each noticed mistake,
  62. and each exception made to these rules or to the scenario description.
  63. ** Devices used
  64. - Mobile terminal: cf. the file names. The OwlPS Client version is
  65. v1.3.0-11-gc4e0352.
  66. - Aggregation server: Asus EeePC 701 4G running Debian GNU/Linux
  67. squeeze (Linux 2.6.32), with an Atheros AR 500 Wi-Fi interface. It
  68. runs OwlPS Aggregator v1.3.1-14-ge278aab.
  69. - Listeners: 4 Fonera 2.0 with 1.8 dBi antennas, running OpenWrt
  70. Backfire. They run OwlPS Listener v1.3.0-11-gc4e0352, and their
  71. transmission power is 18 dBm.
  72. ** Network
  73. The aggregation server, the listeners and the terminal communicate
  74. through an ad-hoc network. This limits the rate at which positioning and
  75. autocalibration requests are transmitted, but allows for a quick
  76. deployment.
  77. ** Environmental parameters:
  78. Each test's report file should report the temperature and humidity when
  79. the test was started. If the information is missing, one can assume
  80. that the temperature is controlled around 22-24°C, and the humidity
  81. varies from 38% to 55%.
  82. ** OwlPS Configuration
  83. *** Aggregator
  84. OwlPS Aggregator is run with the default parameters as of the version
  85. used, with autocalibration enabled. These parameters can be found in the
  86. configuration file [[./owlps-config/owlps-aggregator.conf]].
  87. These parameters are not very important, except for the delay between
  88. two autocalibration orders. The default value is 1000 ms.
  89. The default aggregation timeout should fit most test cases, but keep in
  90. mind that for requests as long as one second (including manual
  91. calibration request with the default parameters), it is too short and
  92. must be extended in the Aggregator's configuration.
  93. You should also be aware of the fact that for a capture point to
  94. transmit autocalibration requests, it must be known by the
  95. Aggregator. Therefore, it is not sufficient to wait for 10 seconds
  96. (cf. Measurement procedure) after starting the Aggregator to guarantee
  97. that each capture point transmits autocalibration requests for 10
  98. seconds. The counter must be started after the Aggregator received a
  99. Hello message from all the capture points.
  100. At the end of a test, beware of not stopping the Aggregator too early,
  101. e.g. if requests are sent with long delays, or simply if the aggregate
  102. timeout is not reached for all the requests in memory (as of August
  103. 2012, OwlPS Aggregator does not flush the non-aggregated requests upon
  104. exiting, but simply deletes them; this was fixed in OwlPS v1.3.4).
  105. *** Listeners
  106. The OwlPS Listener program runs continuously, with the autocalibration
  107. activated. It is launched with the following command:
  108. : owlps-listenerd -A -v -i 192.168.11.254 -I 192.168.11.254 -r ath1 -w ath0
  109. The default autocalibration parameters are used, i.e.:
  110. - 20 packets (-n20),
  111. - 25 ms between two packets (-t25).
  112. *** Client
  113. The mobile terminal continuously sends positioning requests with the
  114. following parameters:
  115. - 20 packets (-n20),
  116. - 10 ms between two packets (-t10),
  117. - 800 ms between two requests (-F800).
  118. Therefore, one request is transmitted approximately each second.
  119. The destination IP address is the Aggregator's one (i.e. 192.168.11.254
  120. in our setup).
  121. The complete command used to launch OwlPS Client is the following:
  122. : owlps-client -i 192.168.11.254 -n20 -t10 -F800
  123. When using a metronome, the command should be adjusted so that exactly
  124. one request is transmitted for each beat of the metronome. For 60 bpm
  125. (one request per second), the following parameters have been found to be
  126. almost exact:
  127. : owlps-client -i 192.168.11.254 -n20 -t10 -F761
  128. When a precise number of requests have to be sent during the scenario,
  129. one can use the -N parameter introduced in OwlPS v1.3.2.
  130. During a manual calibration scenario, the default OwlPS Client's values
  131. are used for the number of packets and the delay, i.e. 20 packets
  132. separated by 50 ms (-n20 -t50).
  133. The mobile terminal's antenna is vertical.
  134. ** Measurement-related rules
  135. - Three mobile terminal's altitudes are defined:
  136. + floor (0 m),
  137. + hip (0.82 m),
  138. + ear (1.57 m).
  139. - For the altitudes higher than “floor”, when the mobile terminal is not
  140. carried by a human operator, it is put on a non-metallic object. In
  141. our setup, the “hip” altitude is achieved by stacking an empty plastic
  142. trash (32 cm) on a cardboard box (50 cm); for the “ear” altitude, we
  143. add a stack of small boxes (75 cm).
  144. - When a human operator carries the mobile terminal, the altitude of the
  145. terminal is 1 m (hips/belly).
  146. - The antenna of the mobile terminal is vertical. When the mobile
  147. terminal is a laptop computer, the screen is vertical, and the
  148. computer is set up so that the display side of the screen is in
  149. direction of the wall opposite to the point where the mobile is
  150. located (when applicable).
  151. ** Measurement procedure
  152. - The infrastructure (Listeners and Aggregator) must be started first
  153. and at least two rounds of autocalibration request done (i.e. each
  154. capture point must have sent at least two autocalibration requests)
  155. before the mobile terminal is started. As a best practice, the
  156. measurements should start at least 10 seconds after the Aggregator
  157. knows all the Listeners (cf. section Aggregator for more details).
  158. - In the scenarios in which a human has to move along a path, a
  159. metronome is set up with the tempo at which the person has to
  160. walk. For example, 60 bpm if the pace is of one step per second.
  161. * One-room scenarios
  162. This series of scenarios is schematised in the figure
  163. [[./figures/room.svg]]. (You can play with the layers to hide or display
  164. various elements.)
  165. ** Testing area
  166. *** Area description
  167. The deployment area is a room of 5.80 × 10.60 metres. The origin of the
  168. plan is set to the South-West corner of the room.
  169. This simple topology is described in the OwlPS Positioner's
  170. configuration file [[./owlps-config/room/topology.csv]].
  171. The file [[./figures/room_panorama_180.jpg]] is a panoramic (180°)
  172. photograph of the room.
  173. The East wall is a weight-bearing wall made of concrete, whereas the
  174. others are simple partitions, 9.5 cm thick. The West wall has two doors
  175. and four windows made of Plexiglas. The doors and windows height is 2.5
  176. m.
  177. A West-East room divider built from wood, metal, and plastic can be
  178. folded or unfolded to separate the room in two areas of approximately
  179. the same size.
  180. The room is clear from any obstacle, except for the following elements:
  181. - Two technical columns made of aluminium containing electricity and
  182. network cables, and whose diameter is 12.5 cm, sitting at the
  183. coordinates (1.74;4.72) and (2.46;6.63).
  184. - Another technical column (which is likely to contain water) of floor
  185. dimensions 31 × 51.5 cm. It sits against the East wall, its centre
  186. being approximately (2.3;5.65).
  187. - The room divider. Folded its floor dimensions are 115 × 71 cm, and
  188. its centre is around (5.4;5.7) (against the East wall); when it is set
  189. up, it splits the room at approximately 5.25 m in the Y axis.
  190. - Four heaters (air conditioners) that measure each 150 × 23 × 92 cm,
  191. sitting at each end of the East wall and between the two doors of the
  192. West wall.
  193. - Two light metal and wood tables and three plastic and metal chairs.
  194. *** Listeners
  195. The capture points are attached to the walls and all have their antennas
  196. in vertical position, in the direction of the ceiling.
  197. Their coordinates are given in the OwlPS Positioner's configuration file
  198. [[./owlps-config/room/listeners-fonera.csv]].
  199. *** Measurement points
  200. To simplify the scenario explanation, the following measurement points
  201. are predefined:
  202. 1. (5;10)
  203. 2. (1;10)
  204. 3. (5;1)
  205. 4. (1;1)
  206. 5. (2.5;5.5)
  207. 6. (5;5)
  208. 7. (5;2)
  209. 8. (3;2)
  210. 9. (3;0)
  211. 10. (1;5)
  212. 11. (1;3)
  213. ** Scenario 1 (static, hip)
  214. The mobile terminal is still, without human operator, at hip altitude.
  215. Measurements are taken at each corner and the centre of the room
  216. (measurement points 1 to 5), during 1 minute at each position.
  217. ** Scenario 2 (static, floor)
  218. Repeat the scenario 1, but the mobile terminal is on the floor.
  219. ** Scenario 3 (antenna angle & direction)
  220. This scenario tests the antenna angle and measurement direction, with a
  221. human operator. The measurement points 2 and 5 are tested.
  222. For each point, measurements are taken in two directions, with a 45°
  223. angle (clockwise) between the two directions.
  224. For the measurement point 2, the directions are:
  225. 1. East,
  226. 2. South-East.
  227. For the measurement point 5, the directions are:
  228. 1. North-West.
  229. 2. North,
  230. For each direction, three antenna orientations are measured:
  231. 1. horizontal,
  232. 2. diagonal,
  233. 3. vertical.
  234. Therefore, we have 6 measurements per point. Each measurement lasts one
  235. minute.
  236. ** Scenario 4 (mobility)
  237. Test with a human operator carrying the mobile terminal. The operator
  238. moves along a path following the measurement points 1 to 5, and stands
  239. at each point for 10 seconds. The pace of the operator is 1 m/s (one
  240. second per step, with one-metre steps).
  241. Timing:
  242. Before to start the timer, start the aggregation server (with
  243. autocalibration activated) and wait for all the listeners to send a
  244. Hello message.
  245. - t-10 :: Stand at MP#1 in the direction of MP#2, while the listeners
  246. send autocalibration requests.
  247. - t0 :: Start the client, stay at MP#1 until t10.
  248. - t10 :: Start walking to MP#2 (4 m distance).
  249. - t14 :: Arrived at MP#2, start rotating in the direction of MP#3.
  250. - t15 :: Rotation achieved, stay at MP#2 until t25.
  251. - t25 :: Start walking to MP#3 (about 9.85 m distance, so the walk pace
  252. is around 1.1 m/s to achieve MP#3 in 9 seconds).
  253. - t34 :: Arrived at MP#3, start rotating in the direction of MP#4.
  254. - t35 :: Rotation achieved, stay at MP#3 until t45.
  255. - t45 :: Start walking to MP#4 (4 m distance).
  256. - t49 :: Arrived at MP#4, start rotating in the direction of MP#5.
  257. - t50 :: Rotation achieved, stay at MP#4 until t60.
  258. - t60 :: Start walking to MP#5 (about 4.74 m distance, so the walk pace
  259. is around 1.2 m/s to achieve MP#5 in 4 seconds).
  260. - t64 :: Arrived at MP#5, start rotating to the right (in the direction
  261. of the mobile wall).
  262. - t65 :: Rotation achieved, stay at MP#5 until t75.
  263. - t75 :: Stop the client.
  264. ** Scenario 5 (inter-packet delay)
  265. This scenario aims to evaluate the impact of the delay between the
  266. packets sent by the mobile terminal. The delay between two requests
  267. (-F), must be the same as the delay between two packets (-t).
  268. Each request lasts approximately for one second, and the total number of
  269. packets transmitted during each test must be approximately the same, in
  270. order to ease the statistical treatment.
  271. The following parameters are evaluated:
  272. - 10 ms, 100 packets, 60 requests (6000 packets);
  273. - 20 ms, 50 packets, 120 requests (6000 packets);
  274. - 30 ms, 33 packets, 182 requests (6006 packets);
  275. - 40 ms, 25 packets, 240 requests (6000 packets);
  276. - 50 ms, 20 packets, 300 requests (6000 packets).
  277. The mobile is on the floor, at the centre of the room (2.5;5.5;0).
  278. For each value, the following procedure is run:
  279. 1. The aggregation server is launched, and autocalibration requests from
  280. all the capture points are received for at least 10 seconds.
  281. 2. The aggregation server is restarted without autocalibration.
  282. 3. The client is run.
  283. Alternatively, if the experiments are done during only one session, the
  284. autocalibration process can be run only once, at the beginning, and the
  285. autocalibration requests stored in a separate file.
  286. Please keep in mind that for requests as long as one second, the
  287. aggregation timeout must be extended in the Aggregator's configuration
  288. (cf. Common rules for details).
  289. ** Scenario 6 (altitude)
  290. This scenario uses measurement points 1 and 5-10. For each measurement
  291. point, three altitudes of the terminal are tested: floor, hip and ear.
  292. The room divider is half-closed (from the East wall to the centre of the
  293. room), and there is no human operator in the room.
  294. For each point, each altitude is measured for one minute, in the
  295. following order:
  296. 1. floor,
  297. 2. hip,
  298. 3. ear.
  299. Alternative procedure (advised for easier use of the measurements): a
  300. separate aggregation file is made for each point and each altitude.
  301. ** Scenario 7 (altitude & human presence)
  302. Repeat the scenario 6, but with a human operator standing 0.5 m at the
  303. West of the terminal.
  304. Only the hip altitude is studied.
  305. ** Scenario 8 (altitude & fixed human presence)
  306. Repeat the scenario 7, but the human operator is always standing at the
  307. measurement point 11.
  308. ** Scenario 9 (packet size)
  309. This scenario is similar to the scenario 5, but the parameter evaluated
  310. is the size of the packets:
  311. - 64 B,
  312. - 128 B,
  313. - 256 B,
  314. - 512 B,
  315. - 1024 B,
  316. - 1450 B.
  317. This size is the parameter given to OwlPS Client, and is less than the
  318. size of the radio packet. The size of the packet received at the
  319. listeners must be written in the report files, as it can vary.
  320. Please refer to the scenario 5 for details and measurement procedure.
  321. ** Scenario 10 (autocalibration inter-packet delay)
  322. Repeat the scenario 1 several times, varying the delay between two
  323. packets of the autocalibration requests (option -t of owlps-listenerd):
  324. - 5 ms,
  325. - 10 ms,
  326. - 15 ms,
  327. - 20 ms,
  328. - 25 ms.
  329. ** Scenario 11 (autocalibration frequency, mobility)
  330. Repeat the scenario 4 several time with different autocalibration
  331. frequencies on the Aggregator (delay between two autocalibration
  332. orders). The autocalibration requests' settings (number of packets and
  333. delay between two packets) will be adjusted on the Listeners, so that a
  334. request emission lasts for around 20-25 ms less than the autocalibration
  335. frequency.
  336. The following frequencies are tested:
  337. - 100 ms (Listeners: -n10 -t8 = 80 ms),
  338. - 250 ms (Listeners: -n16 -t14 = 224 ms),
  339. - 500 ms (Listeners: -n20 -t24 = 480 ms),
  340. - 1000 ms (Listeners: -n39 -t25 = 975 ms).
  341. ** Scenario 12 (horizontal antennas)
  342. This scenario aims to evaluate the impact of horizontal capture points'
  343. antennas. The scenario 1 is repeated partially (for the measurement
  344. points 3, 4 and 5 only) two times:
  345. 1. Each capture point antenna is disposed horizontally, pointing in the
  346. direction of the opposite wall.
  347. 2. The antennas are still horizontal, but placed so that each antenna
  348. points in the direction of another capture point, in a circle: the
  349. North-West and South-East listeners' antennas stay in the same
  350. position as the previous test, but the North-East listener's antenna
  351. points to the West, and the South-West listener's antenna points to
  352. the East.
  353. #+CAPTION: Scenario 12, antennas in the direction of the opposite wall
  354. #+begin_src ditaa :cmdline -s 2 :file s12-opposite.png
  355. +---+ +---+
  356. | | | |
  357. | | | |
  358. +-+-+ +-+-+
  359. | |
  360. | |
  361. | |
  362. | |
  363. | |
  364. | |
  365. +-+-+ +-+-+
  366. | | | |
  367. | | | |
  368. +---+ +---+
  369. #+end_src
  370. #+CAPTION: Scenario 12, antennas forming a “circle”
  371. #+begin_src ditaa :cmdline -s 2 :file s12-circle.png
  372. +---+ +---+
  373. | | | |
  374. | | | |
  375. +-+-+ +-+-+
  376. | |
  377. | -----+
  378. |
  379. |
  380. +----- |
  381. | |
  382. +-+-+ +-+-+
  383. | | | |
  384. | | | |
  385. +---+ +---+
  386. #+end_src
  387. ** Scenario 13 (temperature)
  388. This scenario aims to evaluate the impact of the temperature. The
  389. terminal is on the floor, at the measurement point 1. The temperature
  390. starts from a maximum, and lowers to a minimum during the experiment.
  391. ** Scenario 14 (humidity)
  392. This scenario is similar to the scenario 13, but its goal is to evaluate
  393. the impact of the humidity rather than of the temperature. Like in the
  394. scenario 13, the terminal is at the measurement point 1, but it is
  395. placed at hip altitude.
  396. The humidity starts from a minimum, and is raised during the experiment.
  397. For this purpose, boilers and hot water basins can be used. That is why
  398. the client terminal should not be put on the floor, to avoid attenuation
  399. of the signal due to the liquid water itself.
  400. Nobody should enter the room during the measurements.
  401. ** Scenario 15 (autocalibration alone, static)
  402. Repeat the scenario 1, but without client. The terminal is instead
  403. replaced by a human operator. This scenario aims to evaluate the
  404. influence of the human body on the autocalibration requests.
  405. ** Scenario 16 (autocalibration alone, mobility)
  406. This scenario follows the same principles as the scenario 15, but this
  407. time the scenario 4 is played instead of the scenario 1.
  408. ** Scenario 17 (autocalibration alone, mobility, two humans)
  409. Repeat the scenario 16 (scenario 4 without mobile terminal), but with
  410. two human operators, each starting from two opposite corners of the
  411. room (measurement points 1 and 4). They move along the following
  412. measurement points:
  413. - Operator 1: 1, 2, 3, 4, 5 (same as scenario 16).
  414. - Operator 2: 4, 3, 2, 1, 5.
  415. Detailed procedure:
  416. - Start the aggregation server; human operator #1 is standing at MP#1,
  417. while operator #2 is standing at MP#4.
  418. - After 10 seconds at these positions, the operators start moving to the
  419. next measurement points: operator #1 goes to MP#2, while operator #2
  420. goes to MP#3. The operators walk at a pace of one step per second, in
  421. the direction of the next measurement point. It takes 4 seconds to
  422. reach the next measurement point.
  423. - Each time the next measurement point is reached, the operators turn in
  424. the direction of the next measurement point and stand for 10 seconds
  425. (so at the second position, operator #1 turns in the direction of the
  426. MP#3, and operator #2 turns in the direction of MP#2). The time to
  427. turn is one second (so the total movement time is 5s in this case).
  428. - After 10 seconds at these positions, the operators start walking:
  429. operator #1 to MP#3, and operator #2 to MP#2. The time needed to
  430. complete this walk is 10 seconds.
  431. - After 10 seconds at these positions, operator #1 starts walking to
  432. MP#4 operator #2 starts walking to MP#1. The time needed to reach
  433. these points is 5 seconds.
  434. - After 10 seconds at these positions, both operators walk to MP#5.
  435. - After 10 seconds at MP#5, the measurements are stopped.
  436. ** Scenario 18 (autocalibration alone, empty room)
  437. The autocalibration is performed for 5 minutes, without mobile terminal
  438. and without human operator.
  439. ** Scenario 19 (mobility, two humans)
  440. Repeat the scenario 17, but one of the operators carries the mobile
  441. terminal. (This scenario was not implemented.)
  442. ** Scenario 20 (manual calibration)
  443. Manual calibration, without autocalibration running. The mobile device
  444. is carried by a human operator.
  445. Please keep in mind that the default aggregation time is not sufficient
  446. to aggregate correctly manual calibration requests (cf. Common rules).
  447. ** Scenario 21 (obstacle)
  448. This scenario aims to evaluate the impact of an obstacle on the
  449. propagation. Only two equipments are used, one on each side of the
  450. obstacle. To evaluate the attenuation in both directions, the easiest
  451. way is to activate the autocalibration, but one can also use normal
  452. positioning requests.
  453. * Office space scenarios
  454. This series of scenarios is schematised in the figure
  455. [[./figures/offices.svg]].
  456. ** Common rules exceptions & additions
  457. *** Device used
  458. The Fonera use 5 dBi antennas.
  459. *** Measurement-related rules
  460. Due to the fact that the antenna used on the client terminal in not
  461. bendable, to have it vertical in a fixed position, a little stand was
  462. used, which increases the terminal altitude by 13 cm. Therefore, the
  463. standard altitudes become:
  464. - floor (0.13 m),
  465. - hip (0.95 m),
  466. - ear (1.70 m).
  467. ** Testing area
  468. *** Area description
  469. The floor used is the second floor of the west wing of the Numérica
  470. building, which is the office space of the OMNI team of the DISC
  471. department of FEMTO-ST (formerly LIFC). The plan of this area is
  472. presented in the figure [[./figures/offices.svg]]. It is mainly composed of
  473. four offices of identical sizes, and of two bigger rooms that are each
  474. equivalent to two offices in size. All these rooms are against the west
  475. wall and are served by a corridor at the east. The central staircase
  476. allows to go up from its north side, and down from its south side.
  477. The inner dimensions of the floor are 9 metres (west-east) by 29 metres
  478. (south-north, from the south wall to the doors at the north).
  479. For historical reasons (i.e. previous experiments), the origin of the
  480. plan is located /outside/ the building: the inner side of the west wall
  481. has the coordinate 1 on the X axis, and the inner side of the south
  482. wall is 0.5 on the Y axis. Therefore, the positioning area is between 1
  483. and 10 metres on the X axis, and between 0.5 and 29 metres on the Y
  484. axis.
  485. The west and east walls are load-bearing walls that include big glass
  486. windows with metallic armatures. The central wall that separates the
  487. offices from the corridor is a thick partition in which are installed
  488. electric and network cables as well as water pipes. In contrast, the
  489. partition that separate one office from another is only about 10 cm
  490. thick. The concrete slabs that separate the floors are about 30 cm
  491. thick and are lined with false ceilings.
  492. In the room, various pieces of furniture are present: desks, tables,
  493. chairs, and metal cupboards and filing cabinets. The most clear room is
  494. the meeting room (room 1060 on the map), in which there are essentially
  495. a big table and chairs.
  496. This space's topology is described in the OwlPS Positioner's
  497. configuration files [[./owlps-config/offices/topology.csv]] and
  498. [[./owlps-config/offices/waypoints.csv]].
  499. In this area, the temperature and humidity level are measured in the
  500. corridor, next to the office 0180.
  501. *** Listeners
  502. The capture points are put on pieces of furniture, at an altitude of
  503. approximately one metre; for this experiment, it is considered that the
  504. altitude is exactly one metre. All the capture points have their
  505. antennas in vertical position, in the direction of the ceiling.
  506. Their coordinates, as well as their real altitudes, are given in the
  507. OwlPS Positioner's configuration file
  508. [[./owlps-config/offices/listeners-fonera.csv]].
  509. *** Calibration points
  510. 1. (3;5.48)
  511. 2. (3;9.09)
  512. 3. (3;12.67)
  513. 4. (3;16.30)
  514. 5. (3;19)
  515. 6. (3;24)
  516. 7. (7.50;5.48)
  517. 8. (7.50;9.09)
  518. 9. (7.50;12.67)
  519. 10. (7.50;16.30)
  520. 11. (7.50;19)
  521. 12. (7.50;24)
  522. *** Measurement points
  523. 1. (3;5.48)
  524. 2. (6.85;7)
  525. 3. (1.66;8.49)
  526. 4. (2.95;11.79)
  527. 5. (6.31;13.80)
  528. 6. (4.90;15.10)
  529. 7. (2.75;16.63)
  530. 8. (8.41;13.15)
  531. 9. (9.59;16.20)
  532. 10. (7.50;18)
  533. 11. (5.15;21.07)
  534. 12. (3;19)
  535. 13. (1.77;23.30)
  536. 14. (3.55;23.80)
  537. ** Scenario 50 (manual calibration)
  538. This scenario is similar to the scenario 20. The calibration points are
  539. listed in the upper section “Calibration points”.
  540. ** Scenario 51 (static, hip)
  541. This scenario is similar to the scenario 1. The measurement points used
  542. are 1, 2, 5, 7, 10 and 11, and the terminal is at hip altitude, without
  543. human operator carrying it.
  544. ** Scenario 52 (static, floor)
  545. This scenario is similar to the scenario 2, i.e. a static measurement
  546. with the terminal on the floor, but with the following differences:
  547. - only the measurement point 8 is used;
  548. - the test lasts for at least 30 minutes.
  549. ** Scenario 53 (autocalibration alone)
  550. This scenario is similar to the scenarios 15 to 18, except the
  551. environment is not controlled, i.e. people move in the corridor and
  552. offices in a regular office activity.
  553. ** Scenario 54 (mobility)
  554. This scenario is similar to the scenario 4: a path is defined, going
  555. through all the 14 measurement points.
  556. *** Procedure
  557. Before to start the timer, start the aggregation server (with
  558. autocalibration activated) and wait for all the listeners to send a
  559. Hello message.
  560. - t-10 :: Stand at MP#1, facing the North, while the listeners send
  561. autocalibration requests.
  562. - t1 :: Start the client, stay at MP#1 until t10.
  563. - t11 :: Start walking to MP#2 (6 steps).
  564. - t16 :: Arrived at MP#2, face the North and wait until t26.
  565. - t27 :: Start walking to MP#3 (7 steps).
  566. - t33 :: Arrived at MP#3, rotate clockwise in two steps (until t35), to
  567. face the right side of the frame of the door between the two
  568. offices; wait until t44.
  569. - t45 :: Start walking to MP#4 (5 steps).
  570. - t49 :: Arrived at MP#4, rotating clockwise in one step (until t50) to
  571. face the office door (MP#5); wait until t60.
  572. - t61 :: Start walking to MP#5 (4 steps).
  573. - t64 :: Arrived at MP#5, face the stairway and wait until t74.
  574. - t75 :: Start walking to MP#6 (4 steps).
  575. - t78 :: Arrived at MP#6, face the West and wait until t88.
  576. - t89 :: Start walking to MP#7 (5 steps).
  577. - t93 :: Arrived at MP#7, rotate counter-clockwise in two steps (until
  578. t95) to face the middle of the office wall (the wall separating
  579. the office from the corridor); wait until t104.
  580. - t105 :: Start walking to MP#8 (8 steps).
  581. - t112 :: Arrived at MP#8, rotate counter-clockwise in one step (until
  582. t113) to face MP#9; wait until t122.
  583. - t123 :: Start walking to MP#9 (4 steps).
  584. - t126 :: Arrived at MP#9, rotate counter-clockwise in one step (until
  585. t127) to face the West; wait until t136.
  586. - t137 :: Start walking to MP#10 (4 steps).
  587. - t140 :: Arrived at MP#10, face the North and wait until t150.
  588. - t151 :: Start walking to MP#11 (6 steps).
  589. - t156 :: Arrived at MP#11, face the West and wait until t166.
  590. - t167 :: Start walking to MP#12 (4 steps).
  591. - t170 :: Arrived at MP#12, face the West and wait until t180.
  592. - t181 :: Start walking to MP#13 (6 steps).
  593. - t186 :: Arrived at MP#13, face the North and wait until t196.
  594. - t197 :: Start walking to MP#14 (4 steps).
  595. - t200 :: Arrived at MP#14, face the room door and wait until t210.
  596. - t210 and a few milliseconds :: Stop the client.
  597. One request should be transmitted each second, for a total of 210
  598. requests. To help meeting this goal, the client can be launched with the
  599. -N210 option.
  600. *** Detailed timing
  601. Note: this timing is based on test #7 (2012-09-11), with the slight time
  602. shift induced by the client's parameters (i.e. -n20 -t10 -F761 -N210).
  603. Due to this time shift, 210 requests are sent during 212 seconds, the
  604. end of the test (labelled “end” below) is therefore t212. The two “lost”
  605. seconds are rattrapées during the intervals indicated with a star (*).
  606. - t1-t10 :: (3;5.48;1)
  607. - t11 :: (3.60;6.30;1)
  608. - t12 :: (4.24;6.30;1)
  609. - t13 :: (4.88;6.30;1)
  610. - t14 :: (5.52;6.30;1)
  611. - t15 :: (6.15;6.30;1)
  612. - t16-t26 :: (6.85;7;1)
  613. - t27 :: (6.15;7.70;1)
  614. - t28 :: (5.39;7.83;1)
  615. - t29 :: (4.64;7.97;1)
  616. - t30 :: (3.89;8.10;1)
  617. - t31 :: (3.15;8.23;1)
  618. - t32 :: (2.41;8.36;1)
  619. - t33-t44 :: (1.66;8.49;1)
  620. - t45 :: (2.14;8.92;1)
  621. - t46 :: (2.62;9.36;1)
  622. - t47 :: (3.10;9.79;1)
  623. - t48 :: (3;10.79;1)
  624. - t49-t60 :: (2.95;11.79;1)
  625. - t61 :: (3.79;12.29;1)
  626. - t62 :: (4.63;12.80;1)
  627. - t63 :: (5.47;13.30;1)
  628. - t64-t74* :: (6.31;13.80;1)
  629. - t75 :: (6.50;14.30;1)
  630. - t76 :: (5.90;14.50;1)
  631. - t77 :: (5.40;14.50;1)
  632. - t78-t88 :: (4.90;15.10;1)
  633. - t89 :: (4.10;15.10;1)
  634. - t90 :: (3.60;15.60;1)
  635. - t91 :: (3.60;16.10;1)
  636. - t92 :: (3.60;16.60;1)
  637. - t93-t104 :: (2.75;16.63;1)
  638. - t105 :: (3.70;16.54;1)
  639. - t106 :: (4.65;16.44;1)
  640. - t107 :: (5;15.80;1)
  641. - t108 :: (5.30;15;1)
  642. - t109 :: (6.08;14.54;1)
  643. - t110 :: (6.85;14.08;1)
  644. - t111 :: (7.63;13.61;1)
  645. - t112-t122 :: (8.41;13.15;1)
  646. - t123 :: (8.71;13.91;1)
  647. - t124 :: (9;14.68;1)
  648. - t125 :: (9.30;15.44;1)
  649. - t126-t136 :: (9.59;16.20;1)
  650. - t137 :: (8.80;16.20;1)
  651. - t138 :: (8;16.20;1)
  652. - t139 :: (7.50;17;1)
  653. - t140-t150 :: (7.50;18;1)
  654. - t151 :: (7.50;18.80;1)
  655. - t152 :: (7.50;19.60;1)
  656. - t153 :: (7.50;20.40;1)
  657. - t154 :: (6.80;21.07;1)
  658. - t155 :: (6;21.07;1)
  659. - t156-t166* :: (5.15;21.07;1)
  660. - t167 :: (4.63;20.58;1)
  661. - t168 :: (4.12;20.09;1)
  662. - t169 :: (3.60;19.60;1)
  663. - t170-t180 :: (3;19;1)
  664. - t181 :: (2.40;19.60;1)
  665. - t182 :: (1.77;20.20;1)
  666. - t183 :: (1.77;20.98;1)
  667. - t184 :: (1.77;21.75;1)
  668. - t185 :: (1.77;22.52;1)
  669. - t186-t196 :: (1.77;23.30;1)
  670. - t197 :: (2.20;23.80;1)
  671. - t198 :: (2.70;24.50;1)
  672. - t199 :: (3.20;24.20;1)
  673. - t200-end :: (3.55;23.80;1)