From: "Mattias Engdegård" <mattiase@acm.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 45818@debbugs.gnu.org
Subject: bug#45818: 28.0.50; Test solar-sunrise-sunset fails
Date: Tue, 12 Jan 2021 19:50:33 +0100 [thread overview]
Message-ID: <28AECF36-B916-427E-A0EC-633AED7CB9BF@acm.org> (raw)
In-Reply-To: <871reqp1ax.fsf@tcd.ie>
12 jan. 2021 kl. 17.28 skrev Basil L. Contovounesios <contovob@tcd.ie>:
> At that point, sunrise-sunset has the following value:
>
> ((6.266666667535901 #1="IST") (16.716666667722166 #1#) "10:26")
On my machines (sitting in CET) it is
((7.2666666666045785 "IST") (17.716666666790843 "IST") "10:26")
and the time zone names don't seem to matter for the numerical results today, but maybe it depends on when it's run. In any case we should probably use something less ambiguous than IST (which is apparently also used for Israeli standard time).
I've been unable to reproduce your results but am not sure how to go about doing so exactly; running with TZ=GMT does not alter the results.
Could you try tracking down the origin of those numbers? Here is a trace of some of the relevant functions on my machines:
1 -> (solar-sunrise-sunset (12 30 2020))
| 2 -> (solar-exact-local-noon (12 30 2020))
| | 3 -> (solar-julian-ut-centuries (12 30 2020))
| | 3 <- solar-julian-ut-centuries: 0.2099520876112252
| 2 <- solar-exact-local-noon: ((12 30 2020) 6.9905251059993585)
| 2 -> (solar-julian-ut-centuries (12 30 2020))
| 2 <- solar-julian-ut-centuries: 0.2099520876112252
| 2 -> (solar-sidereal-time 0.2099520876112252)
| 2 <- solar-sidereal-time: 6.592887211896198
| 2 -> (solar-sunrise-and-sunset (0.2099520876112252 6.9905251059993585) 1.0 75.8 0)
| 2 <- solar-sunrise-and-sunset: (6.5198219809993585 18.46122823099936 11.941406250000002)
| 2 -> (solar-sunrise-and-sunset (0.2099520876112252 6.9905251059993585) 26.9 75.8 -0.61)
| 2 <- solar-sunrise-and-sunset: (7.2698219809993585 17.71122823099936 10.441406250000002)
| 2 -> (dst-adjust-time (12 30 2020) 7.2698219809993585)
| 2 <- dst-adjust-time: ((12 30 2020) 7.2666666666045785 "IST")
| 2 -> (dst-adjust-time (12 30 2020) 17.71122823099936)
| 2 <- dst-adjust-time: ((12 30 2020) 17.716666666790843 "IST")
| 2 -> (calendar-date-equal (12 30 2020) (12 30 2020))
| 2 <- calendar-date-equal: t
| 2 -> (calendar-date-equal (12 30 2020) (12 30 2020))
| 2 <- calendar-date-equal: t
1 <- solar-sunrise-sunset: ((7.2666666666045785 #1="IST") (17.716666666790843 #1#) "10:26")
next prev parent reply other threads:[~2021-01-12 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 16:28 bug#45818: 28.0.50; Test solar-sunrise-sunset fails Basil L. Contovounesios
2021-01-12 18:50 ` Mattias Engdegård [this message]
2021-01-12 20:06 ` Basil L. Contovounesios
2021-01-12 21:02 ` Mattias Engdegård
2021-01-12 22:09 ` Basil L. Contovounesios
2021-01-13 12:12 ` Mattias Engdegård
2021-01-13 13:04 ` Stefan Kangas
2021-01-13 13:29 ` Mattias Engdegård
2021-01-13 19:03 ` Basil L. Contovounesios
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28AECF36-B916-427E-A0EC-633AED7CB9BF@acm.org \
--to=mattiase@acm.org \
--cc=45818@debbugs.gnu.org \
--cc=contovob@tcd.ie \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).