Closed adamltaylor closed 8 years ago
Fixed in c0f109540aaaed75813f6c86076ca7e5ecd0a68e in develop, by moving the call to clock() to the looper, just before the call to tic(). The looper then send the clock value back to the frontend for logging via a ZMQ message.
In 0.918, ClockAtRunStart is earlier than it should be by 3-4 seconds. This is essentially because the call to clock() happens in the frontend, whereas the call to tic() used to get the ticID used for the toc() calls that determine the timestamps for each sweep happens in the looper. And these end up being 3-4 seconds apart because of slowness in the looper.