- Find out why bad data is getting written out... even though there are asserts!
- √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
- 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...
- Run the workers repeatedly, trying to identify some of the malformed output errors.
- 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.
Monday, January 25, 2010
To Do - 1/25
Ah... good weekend. Back to work!
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment