From: Jude DaShiell <jdashiel@panix.com>
To: Michael Heerdegen <michael_heerdegen@web.de>, help-gnu-emacs@gnu.org
Subject: Re: sunrise and sunset times
Date: Fri, 29 Jul 2016 19:05:27 -0400 (EDT) [thread overview]
Message-ID: <alpine.NEB.2.20.1607291904360.2701@panix1.panix.com> (raw)
In-Reply-To: <87twf8bd4n.fsf@web.de>
Documentation states accuracy will be within a minute or two and for the
most part what's what's happened here too.
On Fri, 29 Jul 2016, Michael Heerdegen wrote:
> Date: Fri, 29 Jul 2016 12:52:24
> From: Michael Heerdegen <michael_heerdegen@web.de>
> To: help-gnu-emacs@gnu.org
> Subject: Re: sunrise and sunset times
>
> Conor Matthew <conormatthew@openmailbox.org> writes:
>
>> https://www.gnu.org/software/emacs/manual/html_node/emacs/Sunrise_002fSunset.html
>>
>> For 0N 0W
>>
>> Emacs gives
>> sunrise 0704
>> sunset 1909
>>
>> http://aa.usno.navy.mil/cgi-bin/aa_rstablew.pl?ID=AA&year=2016&task=0&place=&lon_sign=-1&lon_deg=&lon_min=&lat_sign=1&lat_deg=&lat_min=&tz=1&tz_sign=1
>> gives
>> sunrise 0703
>> sunset 1910
>
> I had a quick look at the Emacs code. A difference of one minute isn't
> surprising: AFAIK the Emacs calculation is exact - it respects all
> astronomical effects I know of. But it doesn't try hard to round to
> whole minutes correctly, so the result may differ from the actual event
> by an epsilon, where epsilon < 1 min I think. Maybe epsilon < 30 sec
> for aa.usno.navy.mil if they round "correctly", dunno, I don't know that
> site.
>
>
> Michael.
>
>
>
--
next prev parent reply other threads:[~2016-07-29 23:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 14:34 sunrise and sunset times Conor Matthew
2016-07-29 16:52 ` Michael Heerdegen
2016-07-29 23:05 ` Jude DaShiell [this message]
2016-07-29 17:31 ` Pierpaolo Bernardi
2016-07-29 22:56 ` Jude DaShiell
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=alpine.NEB.2.20.1607291904360.2701@panix1.panix.com \
--to=jdashiel@panix.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
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).