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

[Positioning] Fix comments in Stock & Request

This commit is contained in:
Matteo Cypriani 2011-12-02 11:44:01 +01:00
parent b3b1f8eda2
commit fc0ab05620
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
owlps-positioning/src/request.cc
View File

@ -41,7 +41,6 @@ void Request::set_real_position(const Point3D &_real_position)
}
/// Reinitialises all attributes
/**
* - #mobile is NULLified, but the value it pointed to is not deleted.
* - The fields of #time_sent are initialised to 0.

1
owlps-positioning/src/request.hh
View File

@ -83,6 +83,7 @@ public:
void set_measurements(const std::tr1::unordered_map
<std::string, Measurement> &_measurements) ;
void set_real_position(const Point3D &_real_position) ;
/// Reinitialises all attributes
void clear(void) ;
//@}

4
owlps-positioning/src/stock.cc
View File

@ -464,8 +464,8 @@ void Stock::regenerate_reference_points()
* The reference point P we want to generate will end-up containing
* as many calibration requests as the total number of APs.
* For each of these requests, we consider a transmitter TRX (which is
* a virtual mobile) and a receiver RX (the current AP).
* To generate the signal strength (SS) received in P by RX from TRX,
* a virtual mobile located in P) and a receiver RX (the current AP).
* To generate the signal strength (SS) received by RX from TRX,
* we first select two reference APs REF1 and REF2. Then, we average
* the real measurements REF1->RX and REF2->RX, weighting in function
* of the angles REF-RX-TRX and the distance from RX to TRX to compute