From: "Alan E. Davis" <lngndvs@gmail.com>
To: org-mode <emacs-orgmode@gnu.org>
Subject: Re: Solar orbit statistics and your agenda
Date: Tue, 27 Nov 2018 23:08:49 -0800 [thread overview]
Message-ID: <CAF-1L2Qq3xC+tj0q9qkKw+jqOXJuag1iAtMD0LMxBG5tAfP5bA@mail.gmail.com> (raw)
In-Reply-To: <CAF-1L2T03vBa1juLXE3hfi9E-_dQcYa7FifBC2S4_DHL3=esPw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2151 bytes --]
Eric:
I was able to access the API docs (requiring, with my Firefox, to accept a
security exception.)
https://aa.usno.navy.mil/data/docs/api.php
I have to move on. I have found that XEphem's Moon declination output is
excellent, so I only have to convert the time format.
Thank you for your help,
Alan
On Wed, Nov 21, 2018 at 11:04 AM Alan E. Davis <lngndvs@gmail.com> wrote:
> Hello, Eric:
>
> Since I don't need to automate anything or directly pipe the data into any
> other processes, I have taken a leap of faith and used the JPL Horizons
> Ephemeris Web interface to generate an ephemeris for the Moon's (they say
> "Luna"---nice!) declination. This I can edit wtih Emacs to get the data I
> need.
>
> Had I time enough, it would be cool to interface that in a more
> interesting way.
>
> Thank you for the advice.
>
> Alan
>
> On Wed, Nov 21, 2018 at 2:55 AM Eric S Fraga <esflists@gmail.com> wrote:
>
>> On Wednesday, 21 Nov 2018 at 01:24, Alan E. Davis wrote:
>> > Meanwhile, I was able to use a part of the script to get sun
>> information,
>> > but nothing for the moon?
>>
>> I did not see anything related to lunar data. Maybe elsewhere on the
>> site?
>> --
>> Eric S Fraga via Emacs 27.0.50, Org release_9.1.14-1034-gafcb1d
>>
>
>
> --
> [Fill in the blanks]
>
> The use of corrupt manipulations and blatant rhetorical ploys ...---
> outright lying, flagwaving, personal attacks, setting up phony
> alternatives, misdirection, jargon-mongering, evading key issues, feigning
> disinterested objectivity, willful misunderstanding of other points of
> view---suggests that ... lacks both credibility and evidence.
>
> ---- Edward Tufte (in context of making presentations)
>
>
>
--
[Fill in the blanks]
The use of corrupt manipulations and blatant rhetorical ploys ...---
outright lying, flagwaving, personal attacks, setting up phony
alternatives, misdirection, jargon-mongering, evading key issues, feigning
disinterested objectivity, willful misunderstanding of other points of
view---suggests that ... lacks both credibility and evidence.
---- Edward Tufte (in context of making presentations)
[-- Attachment #2: Type: text/html, Size: 3987 bytes --]
next prev parent reply other threads:[~2018-11-28 7:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 13:58 Solar orbit statistics and your agenda Eric S Fraga
2018-11-20 19:12 ` Alan E. Davis
2018-11-21 6:41 ` Eric S Fraga
2018-11-21 9:24 ` Alan E. Davis
2018-11-21 10:55 ` Eric S Fraga
2018-11-21 19:04 ` Alan E. Davis
2018-11-28 7:08 ` Alan E. Davis [this message]
2018-11-28 15:12 ` Eric S Fraga
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAF-1L2Qq3xC+tj0q9qkKw+jqOXJuag1iAtMD0LMxBG5tAfP5bA@mail.gmail.com \
--to=lngndvs@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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/org-mode.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).