Re: Of many things...

Matt Dawson Aug 25, 2000

By definition the NEOCP only has objects for which no elements are
available. You only have to look at the uncertainty plots to see that
slightly different assumptions produce wildly differing ephemeris
predictions. The MPC (quite rightly) is not going to publish even
preliminary orbits for objects when a fair proportion don't even
exist.These are objects that don't even have a preliminary
designation.I was thinking more along the following lines:
At the beginning of an evening to cut and paste expected positions of
10 objects (at the time I expect to observe them) into a text file.
Guide read this text file as fictitious deep sky objects so I can
load
them in Guide, go 'click, ok, Alt-C' and have the position loaded in
Charon. The fact that the objects move is not a problem as these guys
are often far from the predicted postion any how.
It is probably possible to do this already, I have to admit that Ive
never really explored Guide/Charon beyond its use in minor planet
observing. Galaxies and stars - vermin of the skies :-)
Matt #163 Roeser Observatory



>Unfortunately, the Minor
Planet
> Center does not provide orbital elements for objects on the NEOCP
(for
> those unfamiliar with this: the Near-Earth Object Confirmation
Page
is
> a list MPC provides of newly-found fast-moving objects that they
would
> like people to observe, confirm, and get astrometry for.) For
NEOCP
> objects, you can only get an ephemeris.
>
> I see two ways around this oddity. One, MPC could bite the
bullet
> and provide orbital elements for these objects. I suspect they are
> reluctant to do so because the elements will be very imprecise and
will
> bear no relationship to the final results. Still, we all know the
> score here; none of us expect MPC to produce wonderful orbits from
> not-so-wonderful, preliminary observations. We just need them to
> produce "good enough" orbital elements for finding NEOCP objects.
You
> might attempt to pester MPC on this subject.
>
> Second, I might attempt to write code that computes positions
for
> these objects by interpolating the ephemerides. I dislike this idea
> (compared to just using elements, it's a horrible kludge), but it
may
> be the only option.
>