[doc] positionerd: add filter options
Also add default value explanation in owlps-positioner.conf.
This commit is contained in:
parent
e4b8e7239b
commit
7d84e7c957
|
@ -228,6 +228,29 @@ below.
|
||||||
: **--positioning.nss.ignore-cp-reference-points** < //true// | //false// >
|
: **--positioning.nss.ignore-cp-reference-points** < //true// | //false// >
|
||||||
With the NSS algorithm, try to avoid selecting the reference points
|
With the NSS algorithm, try to avoid selecting the reference points
|
||||||
which are coordinates of a CP. Default: false.
|
which are coordinates of a CP. Default: false.
|
||||||
|
: **--positioning.filter.max-speed** //max-speed//
|
||||||
|
Maximal speed at which the mobile terminal can move, in km/h. This
|
||||||
|
option also controls the activation of the filter. Default: 0
|
||||||
|
(disabled).
|
||||||
|
: **--positioning.filter.cp-reset-distance** //distance//
|
||||||
|
With this option set to a positive number, the maximum speed is
|
||||||
|
temporarily set to //max-speed-cp// instead of //max-speed// (see
|
||||||
|
these options) when the mobile terminal is found to be close enough to
|
||||||
|
a capture point. This option determines this “close enough” distance,
|
||||||
|
in metres.
|
||||||
|
This is useful in deployments where the system is much more accurate
|
||||||
|
when the mobile is close to a capture point, such as underground
|
||||||
|
mining tunnels; in such environments, 15 m appears to be a reasonable
|
||||||
|
value to start experimenting.
|
||||||
|
Default: 0 (disabled, i.e. never change the speed even when the
|
||||||
|
terminal is close to a capture point).
|
||||||
|
: **--positioning.filter.max-speed-cp** //max-speed-cp//
|
||||||
|
Maximal (virtual) speed at which the mobiles can move when they are
|
||||||
|
within //cp-reset-distance// (see this option), in km/h.
|
||||||
|
//max-speed// × 10 seems to be a good value to start experimenting.
|
||||||
|
Default: 0, which corresponds to an unlimited speed (i.e. filtering
|
||||||
|
will be completely disabled when the mobile is found to be close to a
|
||||||
|
capture point).
|
||||||
|
|
||||||
|
|
||||||
== Output options ==
|
== Output options ==
|
||||||
|
|
|
@ -265,6 +265,7 @@ mobile-csv-file = /usr/local/etc/owlps/mobiles.csv
|
||||||
# when the mobile is close to a capture point, such as underground
|
# when the mobile is close to a capture point, such as underground
|
||||||
# mining tunnels; in such environments, 15 m appears to be a reasonable
|
# mining tunnels; in such environments, 15 m appears to be a reasonable
|
||||||
# value to start experimenting.
|
# value to start experimenting.
|
||||||
|
# The default is 0, i.e. never change the maximum speed.
|
||||||
#cp-reset-distance = 0
|
#cp-reset-distance = 0
|
||||||
|
|
||||||
# Maximal (virtual) speed at which the mobiles can move when they are
|
# Maximal (virtual) speed at which the mobiles can move when they are
|
||||||
|
|
Loading…
Reference in New Issue