Hi Gerhard, Lawrence,

Gerhard Dangl wrote:

> I have the same result as Lawrence.

Gerhard, by this do you mean: "the update fixed the problem
briefly, but now the bright asteroids are back?" Or in your case,
was the bug never fixed even temporarily?

> But may be this can help to determine the error source. All of the wrong
> displayed MPs have designations of the year 2010. No one wrong visible
> from another year.

That confirms that the error involves the objects found by WISE,
which found a huge batch of asteroids in 2010. (Then it ran out of
coolant -- as expected -- which is why you aren't seeing a lot of
2011 or 2012 objects with this problem.)

WISE, being a Wide-field _Infrared_ Satellite Explorer, got
infrared photometry for the objects it found. That IR photometry
wasn't reported to MPC, though, so we had the unusual situation
of lots of new objects being discovered with no magnitude data given
at all. Normally, mpcorb.dat gives an absolute magnitude (H) and
slope parameter (G) for every object; but it can't do that for the
WISE guys. 2010 DK71, the object that was first noted to be much
too bright, was definitely observed only by WISE and has no H or G
given in mpcorb.dat.

I _thought_ the update I posted fixed this issue. And it appears
that in Lawrence's case, and perhaps yours, it did so, but only
temporarily... which is truly baffling!

-- Bill