Re: [guide-user] Incorrect comet Table data

Bill J Gray Feb 24, 2009

Hi Clay, all,

Just got back on-line after a two-day power outage.

33P/Daniel will show up in Guide, but at magnitude 24.4.
Looks as if the magnitude parameters from MPC are a bit weird.
I've never seen a distance parameter of 12, indicating a _really_
sharp decline in magnitude with distance from the sun.

You can use the trick mentioned by Alan Cahill, thereby
ensuring that only the new ones are shown. But as he suggests,
keep the old one around, in case you want to look at some past
comet for which MPC isn't currently providing data.

More generally, the comet issue has been a nuisance for some
years. MPC provides a list of 'currently observable' objects.
The problem is, many people also want to look at currently
unobservable objects (to see where a comet was some time ago,
for example). So Guide has quite a bit of convoluted logic in
it to merge the MPC list with its existing list.

Complicating this is the fact that comets routinely change
names, especially as they get numbered. Hence, you may find
that you have comets P/2005 R2, P/2009 B3, and 213P Van Ness.
They're all the same objects. It got the first moniker when it
was found. Then it was recovered a few years later and got the
second one. Then it got a permanent number when it was realized
that the two objects were one and the same.

Unfortunately, Guide has no way to know which is which.

So Guide may show all three of them. (Or none of them, if you
got Guide and haven't used the Add MPC Comets feature.) Depending
on when the orbits in question were generated, they may be shown
with slightly different coordinates.

More on this later... gotta get some sleep, then catch up on
e-mail tomorrow.

-- Bill