log and EMA timestamps

Description

Hi Monowar,

I've been working on analyzing the log and EMA output files, and I have noticed that the epoch-based time stamps are off by an hour; for example, the attached files, taken from robas_10 on May 27, both list the completion time with an epoch-based timestamp of 1527439405-18000 = 1527421405, which when plugged into https://www.epochconverter.com/ gives Sunday, May 27, 2018 11:43:25 AM. However, the human-readable time in the log is 12:43:25, one hour later; we know that 12:43:25 is the correct time both because the EMA only delivers starting at 12:30 and because the tester who generated this data kept a log of when they answered each EMA.

Would you please check the code to see why the epoch-based timestamps are off by an hour? I can work-around it for now by adjusting all the times by an hour in my analyses, but it would be good to fix the root cause, since this discrepancy also affects the dashboard data.

Thanks,
Doug

Environment

None

Status

Assignee

Timothy Hnat

Reporter

Doug Morrison

Labels

Sprint

None

Priority

Medium