The time display format used by the client is unclear. If it says "Timeout: 2013-08-02T03:53:24Z" while System Info says "UTC Offset -4", does it mean the timeout in local time is 2013-08-02 07:53:24 or 2013-08-01T23:53:24 ?
It would be best to show times using the local time, as is standard for other applications. It would also be good to show the amount of time left until timeout, and perhaps be able to set a warning to be displayed if the difference between that amount and ETA falls below some threshold (so that e.g. one can remember to run the client overnight). Thanks!
time display format
Moderators: Site Moderators, FAHC Science Team
Re: time display format
The international standard for time used to be called Greenwich Mean Time but it's now known as UTC (Coordinated Universal Time, in French). UTC isn't really a timezone since even in Greenwich, England, they observe seasonal adjustments of 1 hour. (UTC does not change.) The letter Z (pronounced "Zulu") at the end indicates that it's UTC or Zero offset from UTC, not local time.
You could get one of those special clocks with two hour-hands and offset one by -4 hours or just get used to mentally subtracting 4 hours.
You could get one of those special clocks with two hour-hands and offset one by -4 hours or just get used to mentally subtracting 4 hours.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
-
- Posts: 887
- Joined: Wed May 26, 2010 2:31 pm
- Hardware configuration: Atom330 (overclocked):
Windows 7 Ultimate 64bit
Intel Atom330 dualcore (4 HyperThreads)
NVidia GT430, core_15 work
2x2GB Kingston KVR1333D3N9K2/4G 1333MHz memory kit
Asus AT3IONT-I Deluxe motherboard - Location: Finland
Re: time display format
It's more or less standard format: ISO 8601. The "Z" (Zero, or Zulu in NATO phonetic alphabet, hence "Zulu time") means UTC+0. So, at UTC Offset -4 the local time would be 2013-08-01T23:53:24 in your example. Since FAH is a more or less global effort, I suppose they wanted to use a global standard for expressing time. FYI, there's ticket #807 concerning ETA readability etc.
Win7 64bit, FAH v7, OC'd
2C/4T Atom330 3x667MHz - GT430 2x832.5MHz - ION iGPU 3x466.7MHz
NaCl - Core_15 - display
2C/4T Atom330 3x667MHz - GT430 2x832.5MHz - ION iGPU 3x466.7MHz
NaCl - Core_15 - display
-
- Site Moderator
- Posts: 2850
- Joined: Mon Jul 18, 2011 4:44 am
- Hardware configuration: OS: Windows 10, Kubuntu 19.04
CPU: i7-6700k
GPU: GTX 970, GTX 1080 TI
RAM: 24 GB DDR4 - Location: Western Washington
Re: time display format
Folding@home is a very global project. See http://folding.stanford.edu/English/Maps Things are bit more sane if we're all on the same timezone when we examine logs and whatnot. Going with GMT/UTC is particularly helpful at comparing ETAs and timeouts, especially when not everyone broadcasts where they are.
F@h is now the top computing platform on the planet and nothing unites people like a dedicated fight against a common enemy. This virus affects all of us. Lets end it together.
-
- Posts: 887
- Joined: Wed May 26, 2010 2:31 pm
- Hardware configuration: Atom330 (overclocked):
Windows 7 Ultimate 64bit
Intel Atom330 dualcore (4 HyperThreads)
NVidia GT430, core_15 work
2x2GB Kingston KVR1333D3N9K2/4G 1333MHz memory kit
Asus AT3IONT-I Deluxe motherboard - Location: Finland
Re: time display format
BTW, Iceland (capital: Reykjavik) doesn't observe DST (Daylight Saving Time), so for them, it's always UTC+0. Might be a handy tidbit of information if you're traveling and you absolutely have to know actual Zulu time: just check Iceland/Reykjavik time in your preferred gadget if it doesn't show UTC+0 directly.bruce wrote:The international standard for time used to be called Greenwich Mean Time but it's now known as UTC (Coordinated Universal Time, in French). UTC isn't really a timezone since even in Greenwich, England, they observe seasonal adjustments of 1 hour. (UTC does not change.)
Win7 64bit, FAH v7, OC'd
2C/4T Atom330 3x667MHz - GT430 2x832.5MHz - ION iGPU 3x466.7MHz
NaCl - Core_15 - display
2C/4T Atom330 3x667MHz - GT430 2x832.5MHz - ION iGPU 3x466.7MHz
NaCl - Core_15 - display