The three files owlps-aggregator.log, owlps-positioning.log,
owlps-positioning.out are all in CSV format (actually the fields are not
separated by commas, but by semicolons).  The file
socket_adapter.log is the original log from which output data have been
taken in the competition.

owlps-aggregator.log is the log file of the aggregation server, that contains
all the positioning requests sent by the mobile, and the autocalibration
requests sent by the access points. The fields are the following:
  1. MAC address of the request's transmitter (the mobile terminal has
00:18:84:D0:2A:0D, the others addresses are the access points).
  2. Type of the request (0 for a simple positioning request sent by the
mobile terminal, 2 for an autocalibration request sent by one of the access
points).
  3. Timestamp of the request, i.e. the local time on the transmitter. It is a
UNIX timestamp, the format is "seconds_since_epoch.nanoseconds".
  4, 5, 6, 7. Coordinates and direction of the transmitter (here always
"0.00;0.00;0.00;0").
  8. MAC address of the first access point that captured the request.
  9. Signal strength measured by this access point, in dBm.
The next fields are pairs {MAC;Signal strength} for the others access points
that received the request.


owlps-positioning.log is the log file of the positioning server. It contains
the requests transmitted by the aggregation server. It is the same format as
owlps-aggregator.log, except that the coordinates of the access points are
present (for the autocalibration requests).


owlps-positioning.out is the output file of the positioning server. The fields
are the following:
  1. MAC address of the mobile terminal (here always 00:18:84:D0:2A:0D).
  2. Type of the request (here always 0, for simple positioning requests).
  3. Timestamp of the positioning request (local time on the mobile terminal).
  4. Name of the used algorithm (here always RADAR).
  5, 6. X and Y coordinates as computed.
  7. Z coordinate (here always 1 because we worked in 2-D).
  8. "Error"
  9. "-1"


Note that owlps-aggregator.log contains *all* the requests sent by the
terminals and access points since the deployment, so it contains also the
tests I made during the deployment and the first buggy test.
owlps-positioning.log contains about 75% less data than owlps-aggregator.log,
probably only the second test (after I modified the positioning server to fix
a bug, if you remember that). Same for owlps-positioning.out, which is
synchronised with owlps-positioning.log.
For the record, if you want to have the three files synchronised, the first
line of owlps-positioning.log corresponds to the line #28941 in owlps-
aggregator.log.