Hi, as I understand, in Julia we have Date (with 1d resolution, and an “epoch” of Rata Dei 0001-01-01 with the good old proleptic Gregorian calendar), DateTime (with 1 ms resolution, and the same “epoch”, able to cover +/-200 m years), as well as Time (with 1 ns resolution). I’m looking for a Date…

Base’s time is in UT1, modulo time zones You’re right, it’s been documented as UT1 since the DateTime module was first merged before version 0.4. Using UT1 is a good choice for time points and it simplifies the underlying date time arithmetic considerably. It does have the interesting side effe…

UTC itself does not ignore leap seconds, 2016-12-31T23:59:59.314Z is a valid UTC time according to ISO 8601. Almost all software systems (databases, etc.) cannot handle the leap seconds and assume that each day has 86400 s. Julia is not worse in this respect, but I have ideas how to make it better w…

@stephancb , did you see the various packages mentioned earlier in the thread? Chronos.jl, AstronomicalTime.jl?

UTC itself does not ignore leap seconds, 2016-12-31T23:59:59.314Z is a valid UTC time according to ISO 8601. Leap seconds only exist in UTC – they are a feature of how it bridges UT and TAI. Almost all software systems (databases, etc.) cannot handle the leap seconds and assume that each day ha…

Great discussion here; a few notes from when we originally developed and merged the Dates module into Base Julia There was originally support for leap seconds, meaning DateTime originally supported UTC, but after lengthy consideration & debate (similar to this one), it was decided that the majori…

[image] StefanKarpinski: Leap seconds only exist in UTC – they are a feature of how it bridges UT and TAI. Not really. With each leap second the difference between UTC and TAI increases, it is now exactly 37 s. The leap seconds are inserted into UTC in order to keep the difference between UT1…

[image] stephancb: In 99.9 % of all cases, the time stamp that is to be entered into the Julia system is meant to be UTC I wonder where you get this number from. My expectation would be that the majority of users just don’t know enough about the intricacies of leap seconds and time standards,…

A possible review of the Date and Time documention : Delete “…on the UT second [1].” including the complete footnote and replace by “…on UTC [1].” and the footnote [1] Since 1972 UTC is the worldwide time standard. UTC advances at the same rate as TAI (Temps Atomique International) which itself is …

For suggested revisions to the manual, you should simply open a pull request against https://github.com/JuliaLang/julia/blob/master/doc/src/manual/dates.md . That will allow all the specific changes to be discussed within the github system.

AstronomicalTime.md seems to be pretty empty right now, so I cannot say much about it. Chronos.jl looks fine, but I cannot see that it has anything about UT1, which is the issue here. /Stephan

Higher resolution DateTime/TimeStamp

Internals & Design

yakir12 February 6, 2019, 10:00am 45

angtft

Timestamp String with one-second resolution: fastest implementation?

Topic		Replies	Views
Universal Time vs UTC Time in Dates General Usage dates	11	1755	August 26, 2023
`DateTime` arithmetic on `Microsecond` (or smaller) scale Internals & Design dates , datetime	100	4285	August 26, 2023
TimesDates.jl dev for v2 Specific Domains dates , time , internals	44	2506	September 14, 2023
[ANN] TimesDates.jl: times & zones with nanoseconds Community package , announcement , dates	3	1274	April 18, 2022
Why do time quantities have to be integers? Internals & Design question	56	5339	February 5, 2018

Higher resolution DateTime/TimeStamp

Related topics