![]() |
User Manual, Developers Guide and API Documentation |
![]() |
#include <scenario/pathloss/SingleSlope.hpp>


Public Member Functions | |
| SingleSlope (const wns::pyconfig::View &config) | |
| virtual | ~SingleSlope () |
Private Types | |
| typedef OneSlope < NoHeightFreqAttFormula, NoHeightDistAttFormula > | Super |
Private Attributes | |
| Pathloss * | outOfMaxRange |
| Pathloss * | outOfMinRange |
pl = offset + distFactor * log10(distance/m * distNormFactor) + freqFactor * log10(frequency/MHz)
As in all Pathloss-models, minPathloss is guaranteed, so the returned value is max(minPathloss, pl).
offset, distFactor and freqFactor are configurable via pyconfig::Parser, distNormFactor is 1, if distanceUnit was set to "m", 1/1000, if it was "km" in the original formula. The distance argument, however, must always be given in meters [m].
You have to provide sensible values for validDistances and validFrequencies in your configuration. You can use whichever Pathloss model you like as out of range strategy (e.g. Constant, Deny, FreeSpace, another SingleSlope), but keep in mind that the pathloss will be discontinuous at the validDistances borders, if set up improperly.
Pathloss.py contains two example configurations, one sets up the Umts3003Outdoor model that was used in SGOOSE, the other sets up a free space model.
Definition at line 63 of file SingleSlope.hpp.
typedef OneSlope<NoHeightFreqAttFormula, NoHeightDistAttFormula> rise::scenario::pathloss::SingleSlope::Super [private] |
Definition at line 66 of file SingleSlope.hpp.
| SingleSlope::SingleSlope | ( | const wns::pyconfig::View & | config | ) |
Definition at line 41 of file SingleSlope.cpp.
| virtual rise::scenario::pathloss::SingleSlope::~SingleSlope | ( | ) | [inline, virtual] |
Definition at line 70 of file SingleSlope.hpp.
Definition at line 76 of file SingleSlope.hpp.
Definition at line 75 of file SingleSlope.hpp.
1.5.5