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.
 
 
 
 
 
 

284 lines
12 KiB

  1. # Sample configuration file for OwlPS Positioner
  2. # [Miscellaneous options]
  3. # This option controls whether or not the output text files are flushed
  4. # (written to the storage support) after each line.
  5. # The default is to flush.
  6. #flush-output-files = true
  7. # "Replay" mode. With this option enabled, the current time is the
  8. # emission timestamp of the most recent request; you will want to
  9. # enable this when reading inputs (requests) off-line to replay
  10. # scenarios, if time-related options are enabled (e.g.
  11. # positioning.calibration-requests-timeout).
  12. # To be useful, this option requires the listeners' clocks to be
  13. # synchronised. If it is not the case, you should leave it disabled.
  14. # The default is to run in "live mode", i.e. with this option disabled.
  15. #replay = off
  16. [data-input]
  17. # The options in this section are related to the data that are read
  18. # when the program starts.
  19. # Description of the machines running the listeners (capture points).
  20. cp-medium = CSV
  21. cp-csv-file = /usr/local/etc/owlps/listeners.csv
  22. # Description of the clients
  23. mobile-medium = CSV
  24. mobile-csv-file = /usr/local/etc/owlps/mobiles.csv
  25. # Description of deployment area topology.
  26. # You probably don't need a full description of the topology, see the
  27. # topology example file for details.
  28. # Uncomment the following line to activate the topology reading.
  29. #topology-medium = CSV
  30. #areas-csv-file = /usr/local/etc/owlps/topology.csv
  31. #waypoints-csv-file = /usr/local/etc/owlps/waypoints.csv
  32. #reference-points-medium = CSV
  33. #reference-points-csv-file = /usr/local/etc/owlps/reference_points.csv
  34. [input]
  35. # The following options are related to the input of the requests
  36. # (positioning requests and (auto-)calibration requests) from the
  37. # aggregator.
  38. #medium = CSV
  39. #csv-file = /tmp/input.csv
  40. #medium = UDP
  41. #udp-port = 9902
  42. [log]
  43. # The following options allow to log the requests received from the
  44. # aggregator.
  45. # Uncomment the following line to completely disable logging (has
  46. # precedence over the other logging options):
  47. #medium = none
  48. #medium = CSV
  49. #csv-file = /tmp/owlps-positioner.log
  50. [positioning]
  51. # The options in this section are related to the way the requests are
  52. # handled and the results are computed.
  53. # Uncomment lines to activate one or more algorithm.
  54. #algorithm = Real
  55. #algorithm = InterlinkNetworks
  56. #algorithm = FBCM
  57. #algorithm = NSS
  58. #algorithm = FRBHMBasic
  59. # This option allows to create a new mobile when a request is sent by
  60. # a mobile which is not currently in the mobiles' list (i.e. not
  61. # declared in the mobiles' configuration file). If unset, the requests
  62. # sent by unknown mobiles will be dropped.
  63. # It is unactivated by default, mainly to avoid interferent devices.
  64. #accept-new-mobiles = false
  65. # This option allows to create a new capture point (CP) when a request
  66. # is captured by a CP which is not currently in the CPs' list (i.e. not
  67. # declared in the CPs' configuration file), or when a self-calibration
  68. # request is sent by an unknown CP.
  69. # It is unactivated by default for the sake of security.
  70. #accept-new-cps = false
  71. # When receiving a calibration or autocalibration request from a CP,
  72. # containing the transmiter's coordinates, memorise the new CP's
  73. # coordinates.
  74. # This is unactivated by default for the sake of security.
  75. #update-cp-coordinates-online = false
  76. # Coordinates of the deployment area.
  77. # This is used to delimit the area in which reference points are
  78. # generated (when generate-reference-points includes "mesh"), and
  79. # also by the MinMax trilateration method.
  80. # Since MinMax is currently the only trilateration method implemented
  81. # in OwlPS, you should define these parameters if you use any of the
  82. # trilateration-based algorithms (InterlinkNetworks, FBCM, FRBHM).
  83. # With the autocalibration, the Z coordinate is the floor number, not
  84. # a true coordinate in meters.
  85. # They are declared as strings (X;Y;Z). Do not quote!
  86. #area-start = -2;-2;0
  87. #area-stop = 20;30;6
  88. # Algorithm to calculate the similarity, in the signal strength space,
  89. # of two measurements.
  90. # The following algorithms are implemented:
  91. # - mean: The mean of all the packets in the measurement is
  92. # computed, then the euclidean distance between the two means is
  93. # used.
  94. # - interval: The mean Im and the standard deviation Is of the
  95. # packets in the measurement I are computed; the closest reference
  96. # measurement R is the one with the highest number of packets in
  97. # the interval [Im-Is, Im+Is].
  98. # - interval2: Derived of the previous one, this algorithm
  99. # computes the percent of packets in both the intervals
  100. # [Im-0.674×Is, Im+0.674×Is] and [Im-Is, Im+Is].
  101. # Assuming a normal distribution, we should find approximately
  102. # 50% of the packets in the first interval, and 68% in the second
  103. # interval. The closest R is the one for which the percents of
  104. # the two intervals are the closest to these theoretical scores.
  105. # The default is "mean".
  106. #ss-similarity = mean
  107. #ss-similarity = interval
  108. #ss-similarity = interval2
  109. # Smallest possible value for a received signal strength, in dBm. This
  110. # depends on the sensibility of the CPs' Wi-Fi hardware. It is used to
  111. # compensate for CPs that are not in coverage in a given measurement.
  112. # The default value is -99 dBm, which should be fine in most cases.
  113. #smallest-ss = -99
  114. # Generate reference points from the (auto)calibration requests
  115. # received.
  116. # This option can be set to any combination of the following values,
  117. # separated by any characters of your choice (or even none):
  118. # - false (default): do not generate reference points; this is
  119. # equivalent to an empty string and if at least one of the next
  120. # values are present, the presence of the "false" string in the
  121. # option's value will be ignored.
  122. # - mesh: generate reference points according to the regular meshing
  123. # defined by the options area-start/stop and
  124. # generated-meshing-grain-*.
  125. # - line: generate reference points according to the line defined by
  126. # the option generated-line-path and generated-line-step.
  127. # - list: generate only the reference points defined by the option
  128. # generated-points-list.
  129. # Any other or extra characters are ignored, and the string is
  130. # equivalent to "false" if it doesn't contain any valid value.
  131. # Default value:
  132. #generate-reference-points = false
  133. # Example of valid value to activate both meshing and list generation:
  134. #generate-reference-points = mesh+list
  135. #generate-reference-points = list,mesh
  136. #generate-reference-points = meshlist
  137. #generate-reference-points = falselistmesh
  138. # With this option disabled, each generated reference point contains
  139. # a single packet in a single calibration request, computed from the
  140. # mean of the real measurements.
  141. # If enabled, the generated reference points will contain a series of
  142. # packets, better matching the real requests; if no packet ID from the
  143. # real requests match, a single packet reference point is generated
  144. # instead. Default is enabled.
  145. #generate-multi-packet-reference-points = true
  146. # When generate-reference-points includes "list", the reference points
  147. # are generated with the specified distance (in metres) between one
  148. # another, in the X and Y axis.
  149. #generated-meshing-grain-x = 0.5
  150. #generated-meshing-grain-y = 0.5
  151. # The Z option is currently a floor number instead of a vertical
  152. # coordinate in meters. You should leave it to 1, except if you are
  153. # deploying across non-contiguous floors, which is unlikely.
  154. #generated-meshing-grain-z = 1
  155. # When generate-reference-points includes "line", the reference points
  156. # are generated along to the path defined by this option. They are
  157. # generated in a straight line between the given points. At least one of
  158. # the points provided must be the coordinates of a capture point, and
  159. # the path defined here should "link" (include) all the capture points
  160. # that are going to be used for this kind of autocalibration.
  161. # In the string, the values are separated by semicolons, and each group
  162. # of coordinates can optionally be surrounded by parenthesis. The two
  163. # following examples, which declare a path following the points (1;1;1),
  164. # (10;1;1) and (10;10;1), are equivalent:
  165. #generated-line-path = (1;1;1);(10;1;1);(10;10;1)
  166. #generated-line-path = 1;1;1;10;1;1;10;10;1
  167. # When generate-reference-points includes "line", the reference points
  168. # are generated with this (approximate) distance (in metres) between one
  169. # another.
  170. #generated-line-step = 0.5
  171. # When generate-reference-points includes "list", the list of reference
  172. # points declared here is be generated. In the string, the values are
  173. # separated by semicolons, and each group of coordinates can optionally
  174. # be surrounded by parenthesis. The two following examples, which
  175. # declare the points (1;2;1) and (4;2.5;1), are equivalent:
  176. #generated-points-list = (1;2;1);(4;2.5;1)
  177. #generated-points-list = 1;2;1;4;2.5;1
  178. # This option allows the calibration requests sent during the
  179. # positioning phase to be added to the calibration request's list. They
  180. # are added to the calibration requests read by InputDataReader during
  181. # the start-up phase. If this option is not activated, the calibration
  182. # requests are handled as positioning requests.
  183. # This option must be activated for the self-calibration to work, but
  184. # it is not activated by default for security purposes.
  185. #accept-new-calibration-requests = false
  186. # Maximum age of the calibration requests, in seconds. If greater than
  187. # zero, the calibration requests older than this timeout will be
  188. # deleted. See also the replay option.
  189. #calibration-requests-timeout = 0
  190. # With this option activated, the calibration requests associated with
  191. # an existing reference point are deleted when receiving a new
  192. # calibration request, before to associate the new request with the
  193. # reference point.
  194. # The default is true, as there is generally no point keeping old
  195. # calibration requests.
  196. #unique-calibration-requests = true
  197. # If you activate the above option and want the calibration requests
  198. # to be treated as positioning requests (in addition to the normal
  199. # treatment of calibration requests), activate this option.
  200. # The default is false: the first calibration requests' purpose is to
  201. # serve the positioning process, not to use it.
  202. #position-calibration-requests = false
  203. [positioning.nss]
  204. # This subsection contains the options related to the NSS (a.k.a. RADAR)
  205. # algorithm and derivated.
  206. # For a given positioning request, average all the calibration requests
  207. # associated with a reference point before to compute the SS similarity.
  208. # The default is false, i.e. the positioning request is compared
  209. # directly to each calibration request.
  210. #average-reference-points = false
  211. # Do not select reference points on which a CP is sit, as far as
  212. # possible (i.e. if there are reference points where no CP sits).
  213. # This is useful if you are using autocalibration and want to select
  214. # only the generated reference points.
  215. # The default is false.
  216. #ignore-cp-reference-points = false
  217. [output]
  218. # The following options are related to the output of the results.
  219. # Compute the euclidean distance error in two dimensions instead of
  220. # three dimensions. This can be useful when doing experiments on only
  221. # one floor.
  222. # The default is false, i.e. the error is computed in 3D.
  223. #2d-error = false
  224. # This is the default output if none is specified.
  225. #medium = Terminal
  226. #medium = CSV
  227. #csv-file = /tmp/owlps-positioner.out
  228. #medium = UDP
  229. # Currently, the host must be an IPv4 address (not a DNS name, nor an
  230. # IPv6).
  231. #udp-host =
  232. #udp-port = 9910
  233. # The TCPEvAAL output follows the specification of EvAAL 2012 to
  234. # communicate with the SocketAdapter program developed by the
  235. # organizers.
  236. # Note: you can use only one algorithm when using the TCPEvAAL output.
  237. #medium = TCPEvAAL
  238. # Currently, the host must be an IP address (not a DNS name).
  239. #tcpevaal-host = 127.0.0.1
  240. #tcpevaal-port = 4444
  241. # vim: syntax=cfg