It's been awhile since I've posted but over the last few weeks I have studied over the 802.11ad standard and its particulars, along with a detailed review of the wlan flow within ns-3, and I have started on adding a couple of 802.11ad PHY into ns-3.
I have a reasonable grasp of 802.11ad but there are of course a few things I'll need to properly cover when the time comes such as the association beamforming training and medium contention within the announcement period. This stuff will come when I need to add it into ns-3.
I have begun my additions to ns-3 by starting with the channel and PHY layers with the addition of 2 out of 32 different modulation and coding scheme types, the Control PHY at 27 Mbps and a single carrier BPSK PHY at just over a Gbps. I am currently working on the addition of a TxVector object to be passed up and down the stack to allow easy attribute additions in the future.

This week I've spent most of the time doing other assignments, one of which is a deep packet inspector in a FPGA. But I have managed to get the code starting to handle x y translations and early results are looking promising. Over the next few weeks I'll be writing the mid term report so I'm not sure how much time I'll get on the actually project.

Spent a little bit of time getting the wrampsim software working in the
student labs again. Something in the layout code appears to have changed,
which was causing elements to be rendered in the wrong place.

Finished up the python decoder for the http test to properly extract
results from the reported data.

Got most of the core functionality in place to create smokeping style
timeseries graphs to display data we've collected from smokeping sources.
Once I have feature parity I hope to start marking events on the graphs,
as well as extending them to be used with other data sources (for example,
this would be really cool to use with AMP latency tests).

Spent a little time reviewing my old YouTube paper in preparation for discussing it in 513.

Tracked down and fixed a few outstanding bugs in my new and improved anomaly_ts. The main problem was with my algorithm for keeping a running update of the median -- I had a rather obscure bug when inserting a new value that was between the two values I was averaging to calculate the median that was causing all sorts of problems.

Added an API to ampy for querying the event database. This will hopefully allow us to add little event markers on our time series graphs. Also integrated my code for querying data for Munin time series into ampy.

Churned out a revised version of my L7 filter paper for the IEEE Workshop on Network Measurements. I have repositioned the paper as an evaluation of open-source payload-based traffic classifers rather than a critique of L7 filter. I also spent a fair chunk of time replacing my nice pass-fail system for representing results with the exact accuracy numbers because apparently reviewers found the former confusing.

Tried to continue my work in tidying up and releasing various trace sets, but ran into some problems with my rsyncs being flooded out over the faculty network. This was quite a nuisance so we need to be more careful in future about how we move traces around (despite it not really being our fault!).

Have gotten to the point where the cloud controller recognises the new compute node. Requires some modification for the compute node to be fully functioning. Will be starting on my literature review for my report.

Implemented the reporting side of the new AMP's throughput test. It now record results of every test from both the sending and receiving side of the throughput test. Next week I will add Web10G statistics and hopefully start testing.

This week my time was nearly entirely divided up between preparing for my 552 test and writing my lit review for 513 so haven't had much time to spend on my project.

Just about completed script for automatically scanning a cloud service for vulnerabilities

Negotiations were carried out with CAIDA arc regarding the use of some of their nodes for scamper data collection. Further optimisations of scamper for this environment have been carried out on Yoyo and the set of messages that scamper reports to the error file has been further reduced. This means that it may not be necessary to use screens to manually control each node in order to access error messages.

Scamper has also been upgraded to use a wide range of addresses when running the per destination modes.

An initial document regarding the use of the Internet Simulator has been written. I have been studying the code to determine how the initial changes may be made. A set of parameter settings for the first new scenario has been produced and some optimal values have been obtained from published information on the topic.

I've managed to get my program to take in a video in a number of formats and convert them to a usage format and process them frame by frame. Sadly that's all I did since I was having problems getting the library to work properly. But now I can start looking at the output and stabilizing X and Y movements.