Is the Sota clock due to fall in line with GMT ?
In reply to M6RGF:
SOTA times are always in UTC
73 Graham G4JZF
In reply to G4JZF:
I know Graham…but I just posted this a minute ago and it said I posted it an hour ago.
Russ
M6RGF
In reply to M6RGF:
Test post.
It seems to be showing the correct (UTC) time on this post.
73
Brian G8ADD
In reply to M6RGF:
So it is correct then.
SOTA times are always UTC. UK local time is now UTC+1
Andy
MM0FMF
In reply to MM0FMF:
I see what he means, now, the reflector index shows that my post of a couple of minutes ago is an hour ago!
73
Brian G8ADD
In reply to MM0FMF:
The problem is not the actual displayed time, but the time in minutes that a post was posted - i.e you posted this over and hour ago, but actually you did it only minutes ago.
73, Colin
In reply to G8ADD:
Thaks Brian…apologies if I worded it incorrectly and set the hares running.
Russ
M6RGF
In reply to M6RGF:
It’s 13:13 +/- BST as I type this. When I hit post the time will show 12:13 (probably 12:14) as the time is being shown in UTC.
Andy
MM0FMF
In reply to MM0FMF:
Yes, but the index said 60 minutes ago as soon as you posted!
73
Brian G8ADD
In reply to MM0FMF:
Yes thats correct Andy…it now shows you posted it on the reflector 60 minutes ago…apologies if this is how it is meant to be after the clocks change, as you know I am new to the process.
Russ
M6RGF
In reply to M6RGF:
I agree with you guys. Something is not quite right, Andy, as we’re all posting 60 minutes ago. Russ - I’m pretty sure that’s not how it’s supposed to work mate.
Unless every time we post we get abducted by aliens for an hour? That’s the best explanation I have I’m afraid ;))))
Rob G7LAS
In reply to G7LAS:
Well, Rob, my clock says 19:15 BST, so this post ought to be timed at 18:15 GMT
73,
Rod
Obviously my clock is a bit fast.
There must be some code that works out how old a message is from the time it was posted and the current time.
The message posted time is obviously still on UTC, so the time stamp is correct at BST minus one hour.
The index page must be checking this correct ‘time posted’ time in UTC with another reference with it’s time set to BST, thus a message will come out as being 60 mins old when just posted.
73, Colin
In reply to M0CGH:
That’s what I guessed Colin when I finally saw what people were on about. The server time will have autoadjusted itself to BST but the posting time is in UTC. Jon will need to give the server a thump.
I must add that if a programming project will have any issues it will be with time. For such a simple concept it has provided me and many other programmers limitless opportunities to foul up over the last 30 years. When is now? How long is it since then? When is tomorrow? There are so many possible pitfalls. I did a classic last year. The database allows you to look at “the last 12 months”. How hard can it be to work out what the date was 12 months ago if you know the day, month and year for today. Yes you simply subtract 1 from the year to get the date for a year ago. That worked brilliantly until 29th Feb 2012 which gave 12months ago as 29th Feb 2011. Push 29/2/2011 into the SQL engine and you get an date exception as that date isn’t valid. Yes, that caused lots of red ink for database users. The correct solution is to use the time library functions to subtract 365 days from time.now() and use that. But you don’t expect subbing 1 from the year to cause such grief. A classic error!
Andy
MM0FMF
In reply to MM0FMF:
All understood Andy!
I try to stay away from computers as much as I can, I haven’t done any programming for well over 15 years.
Just want to say thanks to all involved for keeping the SOTA facilities up and running.
73, Colin, M0CGH
In reply to MM0FMF:
I remember years ago when displaying graphs in spreadsheets was fairly new someone had the idea of tracking usage on items over the previous 12 Months on something that was quite seasonal (looking to see if the trend was going up or down).
So once the historical data was loaded, they added live updates by summing up the rows in a column until it reached the next occurrence of the same date/month.
For some reason there was a sudden spike every 4 years:)
Colin
M0XSD.
In reply to M0XSD:
For some reason there was a sudden spike every 4 years:)
Guess we can blame the day Tempest Storm was born in 1928. 
Russ
M6RGF