Owl Positioning System: a Wi-Fi-based, infrastructure-centred indoor positioning system. http://owlps.pu-pm.univ-fcomte.fr/
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.
 
 
 
 
 
 

172 lines
5.4 KiB

  1. Introduction to the Owl Positioning System
  2. OwlPS {{OWLPS_VERSION}}
  3. June 2013
  4. %%%
  5. % Man title & section:
  6. %!postproc(man): "^(\.TH.*) 1 " ".TH owlps 7 "
  7. % Fix .TH, add NAME section and TABLE OF CONTENTS title:
  8. %!postproc(man): "^(\.TH.*)$" "\1 OwlPS\ User\ Manual\n.SH NAME\nowlps - Introduction to the Owl Positioning System\n\n.SH TABLE OF CONTENTS"
  9. % Add the table of contents:
  10. %!options(man): --toc
  11. % Man "links":
  12. %!preproc(man): "(owlps-architecture)\.t2t" "//\1//(7)"
  13. %!preproc(man): "(owlps-deployment)\.t2t" "//\1//(7)"
  14. %!preproc(man): "(owlps-[^ ]*)\.t2t" "//\1//(1)"
  15. %!preproc(man): "(owlps[^ ]*\.h)" "//\1//(3)"
  16. %%%
  17. + What is OwlPS? +
  18. **OwlPS** (//Owl Positioning System//) is a positioning (localization)
  19. system based on the IEEE 802.11 radio network (Wi-Fi). It targets mainly
  20. UNIX-like operating systems and is developed and tested primarily on
  21. GNU/Linux, but it should work on BSD platforms as well. Originally
  22. developed at the University of Franche-Comté (Université de
  23. Franche-Comté, France), it is released under the terms of the CeCILL
  24. free software license (GNU GPL-compatible).
  25. OwlPS uses an infrastructure-centred architecture, which means the
  26. infrastructure does the measurements and computes the mobile terminals'
  27. positions, rather than the terminals computing their own positions (as
  28. it is the case for instance with the GPS). The infrastructure is
  29. composed by several capture points that run //OwlPS Listener//, an
  30. aggregation server running //OwlPS Aggregator//, and a computation
  31. server running //OwlPS Positioner//. The role of each of these modules
  32. is detailed in the documentation's part dedicated to the system's
  33. architecture.
  34. OwlPS implements various positioning techniques and algorithms based on
  35. the radio signal strength (trilateration, signal strength
  36. fingerprinting, and hybrid techniques). //OwlPS Listener// uses the
  37. Radiotap header of the network packets to extract the RSS value. It
  38. would be possible to extend the system to work with the TOF (Time of
  39. Flight, i.e. the signal propagation time), but that is out of scope for
  40. now (unless someone is willing to contribute).
  41. OwlPS features a self-calibration (or autocalibration) mechanism for
  42. signal strength fingerprinting-based algorithms, that avoids the
  43. time-consuming manual fingerprinting phase and allows considering
  44. dynamic changes of the environment (human, climatic, etc.) when
  45. computing the location of mobile terminals.
  46. + Contribute +
  47. If you would like to contribute to OwlPS, you can:
  48. - use it, test it, and report suggestions and bugs on the forge:
  49. http://code.lm7.fr/p/owlps/issues/
  50. - get the last development code, add functionalities and send me pull
  51. requests by email or submit code reviews on the forge:
  52. http://code.lm7.fr/p/owlps/review/
  53. + Releases +
  54. ++ Timeline ++
  55. There is no precise timeline for OwlPS, but the file TODO.t2t lists a
  56. bunch of things that should be addressed at some point. A development
  57. point release is made after some work has been done, usually mainly on a
  58. particular topic. Usually such a release represents between 30 and 90
  59. commits.
  60. A stable release is made when a major goal has been reached and the
  61. interfaces stabilised. For research purposes, it is probably better to
  62. use the last development point release or even the last source version
  63. from the Git repository, especially if you are willing to contribute by
  64. integrating your changes in the main repository.
  65. ++ Version numbers ++
  66. Releases are numbered according to the format //M.m.r//, where //M// is
  67. the major version number, //m// is the minor one, and //r// is the
  68. revision number.
  69. Development point release are numbered with an odd minor version number
  70. and a mandatory revision number starting at 0, for example:
  71. - v0.9.0
  72. - v1.1.2
  73. - v1.3.3
  74. A stable release is numbered with an even minor version number; the
  75. revision number is not mandatory, but it is allowed. For example:
  76. - v0.8
  77. - v1.0
  78. - v1.2
  79. - v1.2.1 (this one doesn't exist for real!)
  80. ++ Cross-version compatibility ++
  81. The communication protocol between the elements of the system is
  82. guaranteed to stay the same across revisions of a given stable branch
  83. (e.g. mixing modules of versions 1.2, 1.2.1 and 1.2.2 is possible). In
  84. development branches, the protocol can evolve from one point release to
  85. the next (e.g. mixing modules of versions 1.3.0 and 1.3.1 is not
  86. possible). Changes in communication protocols, libraries' APIs, file
  87. formats, etc., are pointed out in the ``CHANGELOG`` file.
  88. + Documentation summary +
  89. ++ Architecture and other considerations ++
  90. - owlps-architecture.t2t
  91. - owlps-deployment.t2t
  92. ++ Commands' user manuals ++
  93. - owlps-client.t2t
  94. - owlps-listenerd.t2t
  95. - owlps-aggregatord.t2t
  96. - owlps-positionerd.t2t
  97. ++ Developing with OwlPS libraries ++
  98. - owlps.h (Doxygen-generated documentation)
  99. - owlps-client.h (Doxygen-generated documentation)
  100. - owlps-resultreader.h (Doxygen-generated documentation)
  101. + Online ressources +
  102. - Official OwlPS' web page:
  103. http://owlps.pu-pm.univ-fcomte.fr/
  104. - Project manager (source code, bug reports, documentation):
  105. http://code.lm7.fr/p/owlps/
  106. - Experimentations using OwlPS:
  107. http://git.lm7.fr/?p=owlps-experiments.git
  108. = Copying =
  109. This documentation is part of the Owl Positioning System (OwlPS)
  110. project. It is subject to the copyright notice and license terms
  111. in the COPYRIGHT.t2t file found in the top-level directory of the
  112. OwlPS distribution and at
  113. http://code.lm7.fr/p/owlps/source/tree/master/COPYRIGHT.t2t