1
0
Atdalīts 0

[canmet] Add report files for all the scenarios

This commit is contained in:
Matteo Cypriani 2013-06-28 18:15:16 -04:00
vecāks 84935f5450
revīzija 9cc8d5483b
18 mainīti faili ar 216 papildinājumiem un 0 dzēšanām

Parādīt failu

@ -0,0 +1,2 @@
The client terminal is on the wooden table, its antenna is at 10 cm from
CP3's antenna, in direction of the middle of the tunnel.

Parādīt failu

@ -0,0 +1,3 @@
The client terminal is on top of CP3. Its antenna's base is 13 cm above
the base of CP3's antenna. Horizontally, the two antennas are only a
couple of cm apart.

Parādīt failu

@ -0,0 +1,3 @@
The client terminal is not located precisely between RB2 and RB3, it is:
- at 32.50 m from RB3
- at 31.50 m from the door (31.70 m from RB2)

Parādīt failu

@ -0,0 +1,10 @@
The client terminal is located precisely:
- at 32 m from CP3
- at 32 m from the door (32.20 m from CP2)
When on the east side of the tunnel, the terminal is between 5 and 15 cm
away from the wall (depending where the distance measurement is taken),
and is not in line of sight with CP2.
When on the west side, it is between 5 and 10 cm away from the wall and
is in line of sight with the two CPs.

Parādīt failu

@ -0,0 +1 @@
The client terminal is located precisely under CP1.

Parādīt failu

@ -0,0 +1,3 @@
The client terminal is located at 1.20 m from the position of t01 (i.e.
under CP1) in the direction of the south wall (or, more precisely, the
south-south-west wall).

Parādīt failu

@ -0,0 +1,4 @@
In this test, the access point was located in the operation room (south
of CP3), therefore it is not guaranteed that the mobile terminal could
always send positioning requests successfuly, and a lot of retry packets
have probably been transmitted.

Parādīt failu

@ -0,0 +1,3 @@
The client is located at the first intersection at the west of CP1, at
33 m from CP1, in line of sight, and at 1.60 m from the south wall of
the tunnel.

Parādīt failu

@ -0,0 +1,4 @@
The client terminal is located 10 m north of the position of t01, a few
metres south of the north-west/north-east bifurcation. Therefore, it is
at 11.60 m from the south wall. It is not in line of sight with CP1 any
more.

Parādīt failu

@ -0,0 +1,40 @@
The three tests were done in a row, just by deactivating the access
point for 30 seconds between two tests, and generated one big
aggregation file. Here is the detailed (but approximate) timing of the
three tests:
- T0: AP started (12:30)
- Elapsed: 00m 00s .00
- Total time: 00m 00s .00
- T1: t01 started
- Elapsed: 00m 06s .50
- Total time: 00m 06s .50
- T2: AP stopped
- Elapsed: 05m 05s .75
- Total time: 05m 12s .25
- T3: AP started
- Elapsed: 00m 37s .02
- Total time: 05m 49s .27
- T4: t02 started (12:36)
- Elapsed: 00m 14s .99
- Total time: 06m 04s .26
- T5: AP stopped
- Elapsed: 05m 07s .29
- Total time: 11m 11s .55
- T6: AP started
- Elapsed: 00m 34s .48
- Total time: 11m 46s .03
- T7: t03 started (12:42)
- Elapsed: 00m 06s .97
- Total time: 11m 53s .00
- T8: AP stopped
- Elapsed: 05m 09s .06
- Total time: 17m 02s .06
This timing is approximate because the chronometer was started only
after the given action had begun (because the chronometer was an app
running on the smartphone-access point, it was not possible to start
both the access point and the chronometer at the exact same time).
We assume time T0 is 12:30, but the precise hour was not wrote down at
the time. No big deal though.

Parādīt failu

@ -0,0 +1,3 @@
In this test, the human operator stands still at the same position as
for the scenario 01, i.e. at 2 m from the west wall, and faces this
wall.

Parādīt failu

@ -0,0 +1,2 @@
This test is similar to t01, except the operator stands at 30 cm from
the wall.

Parādīt failu

@ -0,0 +1,4 @@
In this test, the operator stays in the same area but can be in motion,
his orientation changes (sometimes he faces one of the three walls,
sometimes he turns in the direction of CP6), he can walk nearer of
further the walls, etc.

Parādīt failu

@ -0,0 +1,15 @@
t01 is the path towards CP5, and t02 is the return, from CP5 to the
emergency exit. Both tests were done in a row and generated only one
big aggregation file.
t01 started approximately at 13:07, and t02 finished approximately at
13:30, but some time passed between the two tests:
Timestamp of the last request of t01: 1368650837.872503991
Timestamp of the first request of t02: 1368651254.630584995
Difference: 416 seconds = about 6 minutes 56 seconds
t02 finished approximately at 13:15, and t01 started around 13:22.
Each test itself lasted about 7 minutes 30 seconds. See the dedicated
report files for precise timing.

Parādīt failu

@ -0,0 +1,43 @@
- T0: AP started (emergency exit)
- T1: start walking
- Elapsed: 00m 08s .72
- Total time: 00m 08s .72
- T2: AP stopped (RB6)
- Elapsed: 00m 53s .90
- Total time: 01m 02s .62
- T3: AP started
- Elapsed: 00m 34s .13
- Total time: 01m 36s .75
- T4: start walking
- Elapsed: 00m 06s .12
- Total time: 01m 42s .87
- T5: AP stopped (RB3)
- Elapsed: 01m 07s .39
- Total time: 02m 50s .26
- T6: AP started
- Elapsed: 00m 35s .51
- Total time: 03m 25s .77
- T7: start walking
- Elapsed: 00m 06s .62
- Total time: 03m 32s .39
- T8: AP stopped (RB2)
- Elapsed: 00m 55s .27
- Total time: 04m 27s .66
- T9: AP started
- Elapsed: 00m 32s .93
- Total time: 05m 00s .59
- T10: start walking
- Elapsed: 00m 06s .11
- Total time: 05m 06s .70
- T11: AP stopped (RB1)
- Elapsed: 00m 59s .75
- Total time: 06m 06s .45
- T12: AP started
- Elapsed: 00m 33s .73
- Total time: 06m 40s .18
- T13: start walking
- Elapsed: 00m 06s .38
- Total time: 06m 46s .56
- T14: AP stopped (RB5)
- Elapsed: 00m 51s .57
- Total time: 07m 38s .13

Parādīt failu

@ -0,0 +1,43 @@
- T0: AP started (RB5)
- T1: start walking
- Elapsed: 00m 05s .50
- Total time: 00m 05s .50
- T2: AP stopped (RB1)
- Elapsed: 00m 52s .27
- Total time: 00m 57s .77
- T3: AP started
- Elapsed: 00m 33s .68
- Total time: 01m 31s .45
- T4: start walking
- Elapsed: 00m 05s .82
- Total time: 01m 37s .27
- T5: AP stopped (RB2)
- Elapsed: 01m 01s .23
- Total time: 02m 38s .50
- T6: AP started
- Elapsed: 00m 33s .76
- Total time: 03m 12s .26
- T7: start walking
- Elapsed: 00m 05s .98
- Total time: 03m 18s .24
- T8: AP stopped (RB3)
- Elapsed: 00m 54s .46
- Total time: 04m 12s .70
- T9: AP started
- Elapsed: 00m 34s .10
- Total time: 04m 46s .80
- T10: start walking
- Elapsed: 00m 05s .62
- Total time: 04m 52s .42
- T11: AP stopped (RB6)
- Elapsed: 01m 03s .43
- Total time: 05m 55s .85
- T12: AP started
- Elapsed: 00m 35s .37
- Total time: 06m 31s .22
- T13: start walking
- Elapsed: 00m 05s .75
- Total time: 06m 36s .97
- T14: AP stopped (emergency exit)
- Elapsed: 00m 43s .69
- Total time: 07m 20s .66

Parādīt failu

@ -0,0 +1 @@
This test lasted about 2 minutes 30 seconds, to end at 14:11.

Parādīt failu

@ -0,0 +1,32 @@
This test is split is six sections, corresponding to six aggregation
files.
1 : from the starting point to CP6
- starting measurements: 10:07:11
- starting to drive: 10:07:50
- stopping at CP6: 10:08:30
2: from CP6 to CP3
- starting measurements: 10:09:10
- starting to drive: 10:09:38
- stopping at CP3: 10:10:44
3: from CP3 to CP2
- starting measurements: 10:12:14
- starting to drive: 10:12:37
- stopping: 10:13:34
4: from CP2 to CP1
- starting measurements: 10:14:14
- starting to drive: 10:14:43
- stopping: 10:15:47
5: from CP1 to CP5
- starting measurements: 10:16:16
- starting to drive: 10:16:42
- stopping: 10:17:54
6: from CP5 to the west intersection
- starting measurements: 10:21:23
- starting to drive: 10:21:55
- stopping: 10:23:00