The Scout Alert Broker doesn't seem usable in its current state.

[jchate6]

Scout pulls interesting objects from the Minor Planet Center’s Near-Earth Object Confirmation Page (NEOCP).

It then updates the objects as they are updated on the MPC providing a lot of useful information that could be relevant for a NEO observer to determine if they wold like to follow up on any potentially hazardous or interesting NEO Candidates.

Essentially none of this useful information is ingested by the TOM. Instead a SIDEREAL target is made using the most recent RA/DEC (which is usually rounded to the nearest DEGREE) and the PHA Score is recorded in the alert.

If we want to incorporate Scout, I believe we need to completely overhaul how we use it:

• Possibly making a separate module to automatically update target data as they are updated on the NEOCP and upgrading or removing targets when they leave the page.
• The Tom Toolkit is not set up to handle poorly known moving objects that do not have defined MPC orbits. A new target class of moving object with complex, erratic, changing, or unknown orbits would allow for the TOM to include newly discovered objects, natural and artificial satellites, Spacecraft, and interstellar interlopers that are currently outside our capability.

[jchate6]

Re-evaluate after #832