mcy
/
owlps
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

[Positioner] s/level/floor/

This commit is contained in:
Matteo Cypriani 2012-05-02 17:29:26 +02:00
parent d2f40bb49e
commit 38f34a693a
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
owlps-positioner/cfg/owlps-positioner.conf
View File

@ -87,7 +87,7 @@ csv-file = /tmp/owlps-positioner.log
# Since MinMax is currently the only trilateration method implemented
# in OwlPS, you should define these parameters if you use any of the
# trilateration-based algorithms (InterlinkNetworks, FBCM, FRBHM).
# With the autocalibration, the Z coordinate is the level's number, not
# With the autocalibration, the Z coordinate is the floor number, not
# a true coordinate in meters.
# They are declared as strings (X;Y;Z). Do not quote!
#area-start = -2;-2;0
@ -134,7 +134,7 @@ csv-file = /tmp/owlps-positioner.log
# and Y axis.
#generated-meshing-grain-x = 0.5
#generated-meshing-grain-y = 0.5
# The Z option is currently a level number instead of a vertical
# The Z option is currently a floor number instead of a vertical
# coordinate in meters.
#generated-meshing-grain-z = 1

4
owlps-positioner/src/userinterface.cc
View File

@ -262,8 +262,8 @@ void UserInterface::fill_positioning_options()
("positioning.generated-meshing-grain-z",
po::value<float>()->default_value(DEFAULT_Z_MESHING_GRAIN),
"When generating reference points, this parameter represents the"
" number of the level. Currently, each increment of Y is a new"
" level (full 3-D coordinates are not supported yet).")
" number of the floor. Currently, each increment of Y is a new"
" floor (full 3-D coordinates are not supported yet).")
("positioning.accept-new-calibration-requests",
po::value<bool>()->default_value(false),
"Add the calibration requests received during the run-time to"