Creating random walk scenario

Under instructions, I am creating a random walk scenario for NDN mobility.
Random Position generator within a regular Hexagon

Python code to be transfered to the main code for generating random locations.
Will be fun to implement completely in C++.
Changing center and placing points to one side

This commit adds a couple of commits to try to make this code legible.

The code can also now change the center of the hexagon and can move all points
to one side of the hexagon, specifically for rhombus 1, which is at the top
part of the hexagon.

This will be required when I generate the points for the scenarios.

Cheers.
Hexagon random generator with Arguments

This commit lets the script create all the points for the hexagons as well
as the random location of wireless access points. It accepts command line
arguments making it easy to modify.

For the time being the display is in the terminal. I am thinking of putting
that in a png as well as showing it on the screen.

I have yet to print out the file with the relevant information for the
simulator script.

Enough for today.
Output file argument and results in files

This commit adds the output file argument to place the generated information
into a png for the plot and a txt file for the information to be used by the
simulator.

The txt file has the following format:

Number of central nodes
Positions of central nodes
Number of wireless nodes per central node
Total number of wireless nodes
Positions of wireless nodes
X and Y axis print and wscript

The python hexagon generator now prints the X and Y axis into the results file.
Wscript, necessary to use waf has been included.

Cheers.
Read topology file and creating all ptp links

Commit creates the topology from results given by the random hexagon generator
and at the moment I have created all the PtP links in the simulation.

Wifi is missing as well as a option to change the speed of the mobile node.

To be continued.
Wifi AP selection, producer, consumer and speed

I have implemented the Wifi AP selection, though it is probably not as nice
as it should be. All Wifi APs use the same SSID on the same channel. This is
not good, but it forces the simulation to constantly change AP, which is not
exactly bad.

Consumer, producer and the speed has been also implemented.
Added one more core node to connect server

Slightly modified the code to have one more first level node that works in mesh
so that we can connect the single server node for the scenario.

Also added some more comments so that it will be slightly easier for people
reading the code to understand what I am doing.
Created personalized MAC to implement RSSI

Created StaMApWifiMac to be able to implement a RSSI choosing MAC.
Correctly indented code use of StaMApWifiMac

The sta-wifi-mac.cc was indented to follow my indenting rules. I do not think
this follows ns-3 rules, but at least makes it easier for me to read.

The ndn-mobility-random scenario now points to StaMApWifiMac, meaning that any
change to the extension code will directly affect the simulations.

I have created two vectors in sta-map-wifi-mac.cc to store the information I
have about the APs in the vicinity. Barring big changes, the vectors will be
maintained throughout the simulation.
Addition of mac-tx-middle, changes to StaMAC

I am starting to see a pattern in the Wifi simulation of ns3. The addition of
mac-tx-middle is interesting because it doesn't seem to get installed in the
ns3/ndnSIM package. Since I will need it, I am including it as part of the
design.

I also modified sta-map-wifi-mac to maintain all the SSIDs it encounters. I
will have to modify the channel to find out how far away things are but that
is a whole different ballgame.

The implementation of a Wifi that is closer to real life will be much more
painful than I imagined.
Where to put the SSID calculation

Since RSSI is not standarized, it isn't directly included in Ns3.

After reading through the information and flowing the flow chart found here:

http://www2.engr.arizona.edu/~junseok/ns3_wifi.htm

I have decided to make a function to run within StaMApWifiMac to change the
SSID taking into account the distance the node is from the SSID he has seen.
This is not a perfect combination but it is within the scope of Wifi RSSI.

Cheers.
Assign SSID to connect to by distance

After reading through a bunch of resources, I ended up using the distance
metric to pick SSID. I was unable to implement this function for calculation
within the MACs or the channels, meaning I had to implement it from the main
program.

Although it is slower than expected, it works as intended and has the virtue
that it doesn't go connecting to places randomly. I can probably improve the
selection but for now it is enough for the primary experiment runs.

Tomorrow will be a fun day.
Lingering StaMAp include file

I was too happy yesterday and forgot to remove all lingering includes to the
deleted header files, causing a failure when trying to compile the code. This
fixes the issue.
Car speed, change SSID every 100 m

Changes included.
Licensing changes

Small changes to licensing.
Simulation end time

Small changes to simulation end time variables.
Changes to file licenses

Included Sato Laboratory.
File type description changes