Hi Bill....
I download the neatod.dat file every morning into Guide; then I copy and rename that file
mpcorb.dat and keep both files in Guide; that allows me to use the same data for both
Charon and for Guide telescope control.

When something is found or announced that same day that is not on the list and I need to
try to catch it the coming night, I simply pull up the one line elements for Guide from
MPC Ephemeris and load THAT file via the Extras/Add MPC.....

Once the new neatod.dat file comes out that actually CONTAINS that object in its listing,
there will be a duplicate listing for that object until I manually remove via
Edit.....this is absolutely no problem at all for me.

My problem is the Comets file which seems to build up and up; I am using the Soft02 file
from MPC each time it is update for that. Some comes long gone simply never disappear off
the list it seems.

It is actually not that big a deal I suppose....I can live with it.

Clay
_____
Dr. P. Clay Sherrod
Arkansas Sky Observatories
MPC H45 - Petit Jean Mountain South
MPC H41 - Petit Jean Mountain
MPC H43 - Conway West
http://www.arksky.org/

----- Original Message -----
From: "Bill J Gray" <pluto@...>
To: <guide-user@yahoogroups.com>
Sent: Thursday, February 26, 2009 9:52 AM
Subject: Re: [guide-user] Re: Incorrect comet Table data


> Hi Clay, Dave,
>
> For several reasons, I've been _STRONGLY_ discouraging use
> of the 'Add Critical-List Objects', 'Add Distant Objects', and
> 'Add Unusual Objects (mostly NEOs)' features in the Add MPC
> Comets/Asteroids function. In fact, I'm very tempted just to
> remove those options; they cause little but trouble.
>
> For asteroids, the best thing to do is to use MPCORB,
> then _never_ add asteroids from Add MPC Comets/Asteroids again.
> Just use that latter function to get comets.
>
> There are two problems with this, though, and if I recall
> correctly, you run into both of them. MPCORB is a big download
> (over 20 MBytes), no fun when on dialup. And as Clay mentions,
> you can get daily update files from MPC and get some objects that
> haven't made it into 'mpcorb.dat' yet.
>
> I _thought_ the duplicate asteroid problem had been effectively
> clobbered, as of some time ago. (Though I'd still expect to see
> problems if, for example, you have an older 'mpcorb.dat' file,
> where the object is unnumbered, and attempt to add in data for the
> numbered object. In such cases, Guide would usually not be able
> to tell that the two objects were really the same... essentially,
> the same sort of designation issue I mentioned with comets.)
>
> Clay, when you say you "load new NEOs that have been reported
> daily", do you mean you use 'Add Unusual Objects (mostly NEOs)'?
>
> I'll do a bit of experimenting here and see if maybe something
> I fixed got broken. Or if something was broken that I didn't catch.
>
> -- Bill
>
>
> ------------------------------------
>
> To unsubscribe from this group, send an empty email to:
> guide-user-unsubscribe@egroups.comYahoo! Groups Links
>
>
>