Logbook Times are not in UTC

Question

jpienaar13 opened this issue 8 years ago · comments

The log book time stamps are currently reading UTC+1 instead of UTC

Not pax

Mohamed Lotfi Benabderrahmane · Answer 1 · Wed Mar 15 2017 23:00:24 GMT+0800 (China Standard Time)

Dear Jacques since when this is happening and for which detetor is this, TPC or MV or both. Thanks

On 3/15/17 6:58 PM, Jacques Pienaar wrote: The trigger time stamps are currently reading UTC+1 instead of UTC — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#554>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AK4hhVBEZDa6jrBuTA4EOpTBBvz12-jlks5rl_ybgaJpZM4MeD0f>.

Daniel Coderre · Answer 2 · Wed Mar 15 2017 23:02:13 GMT+0800 (China Standard Time)

Uh @jpienaar13 did I misunderstand the issue? Trigger time stamp would refer to time in the data. That would be very bad if this time was off.

I thought the issue was with the logbook time stamps? So having nothing to do with the data?

The event times come from the run database. I just checked again and those times are 100% for sure UTC.

Jacques Pienaar · Answer 3 · Wed Mar 15 2017 23:03:31 GMT+0800 (China Standard Time)

Sorry, I meant logbook, I was reading it as "trigger error" and typed the wrong thing. Sorry.

On 15 March 2017 at 16:02, Daniel Coderre ***@***.***> wrote: Uh @jpienaar13 <https://github.com/jpienaar13> did I misunderstand the issue? Trigger time stamp would refer to time in the data. That would be very bad if this time was off. I thought the issue was with the logbook time stamps? So having nothing to do with the data? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#554 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/APdTOjQ9oyNts_VEry2seZOrl7v3NTTeks5rl_13gaJpZM4MeD0f> .