epoch Prime

[Dieter]

(01-05-2018 08:07 PM)salvomic Wrote:  EDIT: following your idea to use Julian Day, I tried this:
• julianday({1970,1,1}) -> 2440587.5

Please note that the Julian day number as it is used in astronomy refers to noon (12:00) for integer values, not midnight.

But why don't you simply try DDAYS(1970.0101, 2018.0105) to get the number of days since then (=17536), multiply this by 86400 (=1515110400) and finally add the seconds of the current time (3600*hours + 60*minutes + seconds)? It's really as simple as that. ;-)

And forget about times zones now. You can add that later once the calculation is finished.

(01-05-2018 08:07 PM)salvomic Wrote:  • julianday(listnow) -> 2458124.38559 :: in the same time I started the Bill's program (EPOCH) on my HP-41CX, calculated for my time zone (+1h) with 3600 in 00 register and it returned epoch = 1515183311

That's 72911 seconds more than 1515110400, so this looks like 20:15 and 11 seconds.

(01-05-2018 08:07 PM)salvomic Wrote:  last result is 3603.98 secs greater that EPOCH program: something went wrong: about 1 hour, and this should be the GMT difference.

Maybe this difference of 4 s is related to leap seconds between 1970 and today? But no... this should be more than just four.

Edit: I had another idea, but then I saw that you had one of the numbers wrong (17536.8559 instead of 17536.38559) so I deleted this again.

But what about a defined test case now? You didn't say for what date and exact time you want to calculate the epoch. Is it today 20:15.11 or something different?

BTW, when you quote a post: take a look at the "dateline" value in the editor. ;-)

Dieter