To Do - 1/20

• Continue to identify which servers are good and which are bad
•  √ extend output in controller to include ip when error
•  √remove worker from list when error Add a status field to the worker info struct so that we know the current state of a worker
• √wait until prepare is finished before letting run happen... at least notify when prepare is done...
• Find out why bad data is getting written out... even though there are asserts!
• 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.