开云体育

The jupiter.1020 bdl file is now out of date so the values are being computed using Meeus copyright 1982. The GRS has migrated several degrees away from the model built at that time.

Greetings, Using the "official" JUPOS value I was unable to get accurate transit times (compared with S&T predictions, etc.). There seems to be an "offset", since using ~29° (instead of the current

Thanks for the information. The key turned out to be installation of the base INDI package so that I could run indi_getprop to see the names of the relevant configuration parameters. I need to do a

Hello, Please see section 5.8 of the XEphem Reference Manual. <https://xephem.github.io/XEphem/Site/help/xephem.html#mozTocId365647> I will paraphrase here. The INDI Control Panel doesn't "know"

I have an Ubuntu-20 system running INDIGO server connected to a Losmandy GM8/Gemini mount. INDIGO provides legacy support for INDI devices, and XEphem connects to the emulated server at localhost:7624

Hi, Attached are 2 plots of the same trail, one with the old elements, one with the new fixed ones (ie perihelion epoch, and n) diff --git a/libastro/plans.c b/libastro/plans.c index

Happily, these elements sit in the raw C code, which is impervious to any whitespace sensitivity. So they should not be haunted by any format problems. I am reverting the recent commit and restoring

Ouuups ... I think you are on the good way ! Reference done from my early troubles of Chebichev coeff of planets 2020-2040 : All the format aspect (columns, width, precision,

Good morning, XEphem folks! It came to my attention that the free “GitHub Actions” build service, which can be configured to run each time there’s a new commit, now supports macOS. I’ve just

Hi, If i am not mistaken there is a confusion in the new code between elements reference epoch and perihelion epoch. Plus, daily motion truncated to 2 significant digits is probably

Dear friends, Indeed, 2247/10/1 is the date the jump occurs for me. I am impressed that you found out so quickly! Another basic question: is there an easy way to activate the Inertial frame by

Many thanks for your research, Brandon. Since 2248 uses the new elements and this date produces wildly incorrect positions, I would suggest reverting back to the older elements. For reference, I ran

[email protected]> wrote: I have just tested and can confirm that the above-linked commit is the one that introduced the discontinuity. Apparently this new elliptical orbit for Pluto does not

wrote: Back in July, someone offered to update the Pluto orbital elements: https://github.com/XEphem/XEphem/issues/2#issuecomment-887460576 Here's the code update they

Hello Maxime, Two comments: 1. I confirm your report using XEphem 4.0.1 but I can also report the?jumping does NOT happen with my legacy 3.7.6 so *SOMEBODY BROKE SOMETHING*. 5/16/2247 00:00 UTC?

Dear friends of XEphem, I am very happy that the improving pandemic situation has enabled me to resume my practical courses with XEphem in a real room with real Bachelor students... I haven however,

that worked for 10.5.8 and xephem 4.1.0 thanks elwood

You need -lXp, just as in my post: Now I will say no more.

CFLAGS = $(LIBINC) $(CLDFLAGS) -O2 -Wall -I$(MOTIFI) -I/opt/X11/include < LDFLAGS = $(LIBLNK) $(CLDFLAGS) -L$(MOTIFL) -L/opt/X11/lib < XLIBS = -lXm -lXt -lXext -lXmu -lX11 the above part has no value

Try using the changes I showed in my diff, you're still not doing it the way I did.