Matt, Bob's suggestion (that you add the MPC report when you load the
image, not when you blink it) is almost certainly the way to go. In
truth, I hadn't really expected anyone to try adding reports from the
blinked files (though I should have), and I'd worry a bit about data
generated in this way. For one thing, Charon handles blinking by
re-sampling the 'blink' images (!). This is fine if you're just looking
for moving objects and comparing images, but it means that astrometry done
on the 'blink' images loses a bit of precision.

This may not be true forever. I have some thoughts of revising Charon
to 'blink' two images by using the fact that it can turn an RA/dec into
a pixel value in both images. At that time, I'll fix the 'report time'
problem and MPC reports generated from the 'blink' image(s) will be as
valid as any other. But right now... best to do it as Bob suggests.

Re R. Mark Elowitz' comment about Find_Orb showing the MOID for an
orbit... I've been contemplating doing this, and I must admit that it's
not really in answer to an overwhelming bunch of requests for it. It's
more that I once figured out a mathematically interesting way to do it,
the only semi-practical physics problem I've ever seen where being able
to solve a quartic equation (i.e., finding x if

x^4 + ax^3 + bx^2 + cx + d = 0

would be useful. So I may add it, even though not many people are
really interested in it <grin>, simply because the problem and
solution are of interest to _me_.

(Note to curious non-asteroid-hunters: MOID = Minimum Orbital
Intersection Distance, the minimum distance in space separating the
orbits of two objects, usually taken to be the Earth and an asteroid.
If the MOID is low enough, then there's a chance the objects might
someday collide, and you may have a PHA = Potentially Hazardous
Asteroid. The MOID is usually found by the "method of Sitarski".
I may have found a faster and more accurate algorithm.)

-- Bill