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

[doc] Fix links to commands' manuals

This commit is contained in:
Matteo Cypriani 2013-06-12 12:32:12 -04:00
parent 6551bd6c3a
commit 35eef92e94
3 changed files with 13 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/owlps-architecture.t2t
View File

@ -48,7 +48,7 @@ Each step of this protocol corresponds to a different module:
signal strength, and send the information to the aggregation server.
They run the //OwlPS Listener// module; a capture point can be any
device with a Wi-Fi interface whose driver offers a support for
//Radiotap// – see owlps-listener.t2t.
//Radiotap// – see owlps-listenerd.t2t.
: **The aggregation server**
The aggregation server collects all the information from the capture
@ -56,13 +56,13 @@ Each step of this protocol corresponds to a different module:
address and the request timestamp, that together form a unique
identifier), and forwards them to the positioning server. This is done
by the //OwlPS Aggregator// module, which can run on a fairly modest
hardware – see owlps-aggregator.t2t.
hardware – see owlps-aggregatord.t2t.
: **The positioning server**
The positioning server, or computation server, takes as an input the
data from the aggregation server, and outputs the computed positions,
thanks to the //OwlPS Positioner// module, described in detail in
owlps-positioner.t2t.
owlps-positionerd.t2t.
@ -77,12 +77,12 @@ to avoid negative coordinates, but that is not a requirement.
All the coordinates are in metres, and it is also mandatory that all the
distance measurements provided in the positioning server's configuration
be in metres – see owlps-positioner.t2t.
be in metres – see owlps-positionerd.t2t.
= See also =
owlps.t2t, owlps-client.t2t, owlps-listener.t2t, owlps-aggregator.t2t,
owlps-positioner.t2t
owlps.t2t, owlps-client.t2t, owlps-listenerd.t2t, owlps-aggregatord.t2t,
owlps-positionerd.t2t

2
doc/owlps-client.t2t
View File

@ -40,7 +40,7 @@ invocation form, that is when the user provides the direction
(orientation) and the coordinates of the mobile terminal,
//owlps-client// will send calibration requests instead of positioning
requests, which can be registered (using OwlPS Aggregator, see
owlps-aggregator.t2t) to create a manual calibration database.
owlps-aggregatord.t2t) to create a manual calibration database.

13
doc/owlps.t2t
View File

@ -120,17 +120,16 @@ revision number is not mandatory, but it is allowed. For example:
++ Commands' user manuals ++
- owlps-client.t2t
- owlps-listener.t2t
- owlps-aggregator.t2t
- owlps-positioner.t2t
- owlps-listenerd.t2t
- owlps-aggregatord.t2t
- owlps-positionerd.t2t
++ Developping with OwlPS libraries ++
% FIXME: these man pages could be generated from Doxygen comments
- owlps.h
- owlps-client.h
- owlps-resultreader.h
- owlps.h (Doxygen-generated documentation)
- owlps-client.h (Doxygen-generated documentation)
- owlps-resultreader.h (Doxygen-generated documentation)