Re:What Time Is It on the International Space Station? (2013)
by tzs on Sunday March 11, 2018 @11:31PM
(#16566040)
There are probably better choices than Iceland, if Android supports them. Iceland doesn't do DST now, but has in the past (1917-1918, and 1939-1968). The farther North a place is, the stronger the case for DST, so I wouldn't count on Iceland changing not their mind someday.
I'd pick someplace reasonably close to the equator. Then there is little difference in sunrise and sunset times throughout the year, and there is pretty much no case to be made for DST on sunlight grounds.
Some good choices, if whatever you are trying to set supports any of them:
• Liberia. City of Monrovia if you have to specify by city. There's only 0:43 difference between the longest and shortest daylight periods of the year there.
• Guinea, city of Conakry.
• Togo, city of Lomé.
There are a few other countries in the general area of these three that are on UTC+0 but these three have never had DST so are probably more likely to stay that way.
Re:What Time Is It on the International Space Station? (2013)
by seanmcdirmid on Monday March 12, 2018 @12:09AM
(#16566161)
> The farther North a place is, the stronger the case for DST
I disagree. If you get to the north pole or anywhere near the Arctic Circle (where Iceland is), it can still be dark at noon in the winter and light at midnight in the summer. You can't nearly compensate for that with a mere hour change, so why bother?
Re:What Time Is It on the International Space Station? (2013)
by __s on Sunday March 11, 2018 @07:48PM
(#16565359)
I don't have a phone, boss wants me to get one, & I'll be setting it to UTC if I end up with one
I've had my own devices set to UTC for the past few years. It made sense for coordinating when my friends are in whichever places of time, especially for online PvP gaming. It worked well when I was working remotely
Re:What Time Is It on the International Space Station? (2013)
by juststeve on Sunday March 11, 2018 @06:41PM
(#16565125)
i read somewhere that some people may not like referring to britain as the default 'reference point' for timezones due to political/cultural reasons of their country. personally i dont have an issue with it, and i'm not saying that's the case here, maybe the author just likes iceland?
Re:What Time Is It on the International Space Station? (2013)
by jcranmer on Sunday March 11, 2018 @11:02PM
(#16565965)
To be slightly more accurate: in the 1880s, the British Empire had the preeminent navy and thus the preeminent naval charts. While other countries (including the US) maintained more local meridians for doing geodetic surveys of their own countries, it was the Greenwich Meridian that tended to dominate naval charts, which meant that it was more or less a de facto standard anyways by the Meridian Conference.
Re:What Time Is It on the International Space Station? (2013)
by clamprecht on Sunday March 11, 2018 @09:29PM
(#16565652)
I think they actually have a separate time called OBT (maybe it stands for Orbit).
I was at the Johnson Space Center in Houston recently, where we got a tour of the live Mission Control room for the International Space Station. I noticed two clocks at the top of one of the screens. One was GMT, the other was "OBT", and the OBT clock was around 17 seconds ahead of GMT. I think it has to do with relativity, and the fact that the space station is moving relatively faster than the earth. Maybe someone can confirm.
I got a photo of this mission control monitor if anyone is interested.
Re:What Time Is It on the International Space Station? (2013)
by userbinator on Sunday March 11, 2018 @10:27PM
(#16565854)
+17s would not be due to time dilation, neither in magnitude nor sign; references I could find show that time on the ISS is slower than on Earth by around 14ms per year, and the ISS has been on orbit for less than 20 years.
Re:What Time Is It on the International Space Station? (2013)
by sxcurry on Sunday March 11, 2018 @07:01PM
(#16565195)
Technically, UTC is a time standard, and GMT is a time zone, so the two, although equal, are not really the same thing. Also, you can set your iPhone to UTC in the World Clock, which I do as an amateur astronomer.
Re:What Time Is It on the International Space Station? (2013)
by rocqua on Sunday March 11, 2018 @07:20PM
(#16565256)
I thought UTC the same, doesn't that mean that GMT+0 is essentially wrong? I thought GMT was essentially UTC+0, and all other time zones (ignoring DST) are defined as offsets to UTC, not GMT.
Re:What Time Is It on the International Space Station? (2013)
by TheSoftwareGuy on Sunday March 11, 2018 @11:53PM
(#16566105)
Your example with pointers actually wouldn't compile, and I think the analogy you are trying to make is not accurate. On the second line you are assigning the target address of `GMT` to be the value pointed to by UTC. In other words you are trying to assign a value of type "Time" to an object to type "Pointer-to-Time".
If, however you meant for that line to be:
Time *GMT = UTC;
it would compile fine, but then your second comparison would evaluate to true, and the whole analogy be rather pointless.
Re:What Time Is It on the International Space Station? (2013)
by JazzProgrammer on Sunday March 11, 2018 @07:35PM
(#16565314)
We spent a lot of time at Yeshiva discussing when a Jew in space, or on Mars, or on a planet orbiting Alpha Centauri (for example) would have to light Shabbos candles or celebrate Yom Kippur.
This issue has already come up with Jewish astronauts on the Space Station.
Re:What Time Is It on the International Space Station? (2013)
by peeters on Monday March 12, 2018 @12:08AM
(#16566153)
This kind of makes me want to make a site that will show the current solar time of the ISS. i.e. when the ISS is between the Earth and Sun it's 12:00, on the opposite side it's midnight. And show what time sunrise and sunset are. The minutes would obviously be much shorter (as a day is only ~90 minutes long), but it'd be interesting to see.
Re:What Time Is It on the International Space Station? (2013)
by rocqua on Sunday March 11, 2018 @07:38PM
(#16565324)
If you are going to design something using a time code the most obvious solution is probably to choose your own zone.
When you realize that doesn't apply to anyone else, UTC is the next option. Especially because it means you don't need to deal with user configuration.
As for ISO8601, that probably results from people looking for some standard to help with compatibility.
If you just mean YYYY-DD-MM HH:MM that is just nicely ordered. Actual ISO8601 would yield something like: 2018-03-11T22:53:40+00:00
I personally really hate that T in ISO8601, but it is actually a standard aimed at being both human and machine readable.
All that aside, I think we can all agree that MM-DD-YYYY is just incongruous and stupid.
Re:What Time Is It on the International Space Station? (2013)
by ygra on Sunday March 11, 2018 @11:21PM
(#16566021)
Well, the T can be omitted if reading and writing parties agree: »NOTE: By mutual agreement of the partners in information interchange, the character [T] may be omitted in applications where there is no risk of confusing a date and time of day representation with others defined in this International Standard.«
And I think SpaceX wouldn't even have the obvious option of using their own time zone. AFAIK mission control and launch are in different time zones anyway, so UTC is really the only sane option to make sure everyone refers to the same time.
Re:What Time Is It on the International Space Station? (2013)
by tyldum on Monday March 12, 2018 @05:26AM
(#16566950)
I work in the space industry and UTC is the only things we use for anything operational. Most also use it for meeting coordination.
Many missions also use a Mission Elapsed Time which is based on launch time. Usually only used during launch and early phase in case there are launch delays.
[0] https://greenwichmeantime.com/uk/time/british-summer-time/
Android still doesn’t support UTC time zone, and need to use Iceland as hack. Which depends on Iceland not changing their time zone.
I'd pick someplace reasonably close to the equator. Then there is little difference in sunrise and sunset times throughout the year, and there is pretty much no case to be made for DST on sunlight grounds.
Some good choices, if whatever you are trying to set supports any of them:
• Liberia. City of Monrovia if you have to specify by city. There's only 0:43 difference between the longest and shortest daylight periods of the year there.
• Guinea, city of Conakry.
• Togo, city of Lomé.
There are a few other countries in the general area of these three that are on UTC+0 but these three have never had DST so are probably more likely to stay that way.
I disagree. If you get to the north pole or anywhere near the Arctic Circle (where Iceland is), it can still be dark at noon in the winter and light at midnight in the summer. You can't nearly compensate for that with a mere hour change, so why bother?
I've had my own devices set to UTC for the past few years. It made sense for coordinating when my friends are in whichever places of time, especially for online PvP gaming. It worked well when I was working remotely
https://en.wikipedia.org/wiki/International_Meridian_Confere...
I was at the Johnson Space Center in Houston recently, where we got a tour of the live Mission Control room for the International Space Station. I noticed two clocks at the top of one of the screens. One was GMT, the other was "OBT", and the OBT clock was around 17 seconds ahead of GMT. I think it has to do with relativity, and the fact that the space station is moving relatively faster than the earth. Maybe someone can confirm.
I got a photo of this mission control monitor if anyone is interested.
If, however you meant for that line to be: Time *GMT = UTC;
it would compile fine, but then your second comparison would evaluate to true, and the whole analogy be rather pointless.
Sure, C wouldn't work that way, but it's just supposed to be pseudocode anyway.
https://www.youtube.com/watch?v=-5wpm-gesOY
This issue has already come up with Jewish astronauts on the Space Station.
Edit: and usually in ISO8601-ish format
As for ISO8601, that probably results from people looking for some standard to help with compatibility. If you just mean YYYY-DD-MM HH:MM that is just nicely ordered. Actual ISO8601 would yield something like: 2018-03-11T22:53:40+00:00 I personally really hate that T in ISO8601, but it is actually a standard aimed at being both human and machine readable.
All that aside, I think we can all agree that MM-DD-YYYY is just incongruous and stupid.
And I think SpaceX wouldn't even have the obvious option of using their own time zone. AFAIK mission control and launch are in different time zones anyway, so UTC is really the only sane option to make sure everyone refers to the same time.
But it does do UTC.