To Do - 1/21

• √Write a handle tool for collecting the resulting data
• Find out why bad data is getting written out... even though there are asserts!
• √Add sanity checking on the files... some kind of preprocess step (a flag to analyzer), identifying the areas that are malformed.
• Add this sanity checking to the writing of the data in worker. Add a flag to enable it. Put the functionality for it in an inline function in shader.h
• Log all of the data that is written out to std out as well, for later sanity checking.
• try running the worker in some kind of test mode on each server
• make sure udp messages are working correctly by sending two messages to a worker, and testing that two reads happen...
• Modify analyzer to spit out unprocessed data as a spreadsheet (peer x time), so as to graph the raw data, rather than just the processed data.