Closed dmegahan closed 9 years ago
Update: currently the output name for a stream session is the exact date and time the stream session was started. This isn't descriptive, and is hard to read/could be confusing. A better naming convention is needed.
Sessions are now implemented in the json file. Sessions are defined as blocks of time where a certain game is played, uninterupted.
A stream can end and begin on the same day, within a few hours of each other. This causes an issue where the 2 stream sessions are combined data wise, causing some weird graphs, see: https://plot.ly/~dmegahan/244/destiny20-04-2015/
Need to define a behavior where the file news are unique to the thread, instead of to the day. When a stream thread dies because of the stream going offline, not because of an error, we should output the graph and "lock" the csv file, so it isn't written to again.