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.

41 lines
1.2KB

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