TESS concept page for an automated asteroid tracking network. This page is a planning and education concept, not an automated public impact-warning system.

Asteroid Watch Network

Concept architecture for a distributed planetary-defense network: sky sensors, automated detection, orbit refinement, risk scoring, alerting, and public observatory dashboards.

▸ Asteroid Watch Network Node Blueprint
Planetary Defense Network Boundary FITS / telemetry MPC obs format weather + seeing preprocess detect tracks orbit solve risk score catalog lookup feedback to scheduler event stream alert threshold slew commands Backyard NodesRaspberry Picamera + mountedge capture Partner Scopesschools / clubsremote observatoriesdistributed coverage Sensor Hubcloud / rain / windsky brightnesssafe-to-open Ingest GatewayMQTT / HTTPSchecksum + metadatatime sync validationedge-to-cloud buffer Image Pipelineplate solvingcalibration framesstar subtractionquality gate Detection AImoving-object modeltracklet linkingfalse-positive filtercandidate events Orbit Engineinitial orbit fituncertainty coneephemeris updatefollow-up priority RiskScoringMOIDvelocitysize est.PHA flag Catalog DBMPC / JPL / NEOknown objectscross-match Autonomous Schedulertarget queue + visibility windowsweather-aware taskingfollow-up commands Event BusKafka / NATS / MQTTdetections, alerts, jobsnear real-time stream Alert Coordinatorhuman review gateTelegram / email / sirendo not auto-panic Public Dashboardlive sky statusconfirmed object mapplanetarydefensefoundation.net Analyst Consolecandidate reviewmanual escalationmission control Zero-trust processing zone: signed data, audit trail, role-based access Legend External sensors Processing / AI Risk / security / alerts

Network Mission

  • • Detect moving objects from distributed telescope nodes
  • • Refine orbit estimates with follow-up observations
  • • Separate public education data from sensitive alert workflows
  • • Support backyard observatory sensors and partner stations

Automation Loop

  • • Weather and visibility decide what each node observes
  • • Images are plate-solved, calibrated, and quality-checked
  • • AI links detections into tracklets and compares catalogs
  • • Scheduler retasks telescopes when uncertainty is high

Safety Model

  • • Alerts require confidence thresholds plus human review
  • • All observations are signed and traceable
  • • Public dashboard only publishes confirmed/safe summaries
  • • Escalation routes can notify Telegram, email, and mission ops

Recommended Observatory Node Specifications

The Asteroid Watch Network can start with modest backyard gear, but asteroid and comet hunting depends on repeatable tracking, accurate time stamps, plate solving, calibrated images, and follow-up observations. The specs below are practical planning targets for nodes that can detect moving objects, confirm candidates, and contribute useful follow-up data.

ENTRY NODE

Wide-Field Survey Telescope

  • 80-150 mm refractor, astrograph, or fast Newtonian
  • Fast focal ratio around f/2.8-f/6 for short exposures
  • Approx. 250-750 mm focal length for a wide search field
  • Useful for bright comets, wide-area patrols, and training nodes
CORE NODE

Asteroid Follow-Up Telescope

  • 150-250 mm aperture minimum for serious NEO follow-up
  • Fast Newtonian, RASA/HyperStar, SCT reducer, or corrected astrograph
  • Motorized focuser and stable collimation recommended
  • Goal: repeatable 30-120 second exposures with round stars
ADVANCED NODE

Deep Follow-Up / Faint Object Rig

  • 280-400 mm aperture class for fainter objects
  • High-precision mount, permanent pier, wind shielding, and remote power control
  • Longer focal length acceptable when tracking and plate scale are well managed
  • Best for confirmation, astrometry refinement, and comet morphology imaging
CAMERA

Recommended Camera Specs

  • Monochrome cooled CMOS or CCD strongly preferred for sensitivity
  • Low read noise, high quantum efficiency, 12-16 bit capture
  • Global shutter is helpful but not mandatory for still-frame astrometry
  • Pixel scale target: roughly 1-3 arcsec/pixel for many backyard NEO setups
  • Use FITS output with accurate metadata and UTC time stamps
MOUNT

Mount and Tracking

  • Computer-controlled equatorial mount with ASCOM/INDI support
  • Reliable go-to, plate-solve centering, and sidereal/non-sidereal tracking support
  • Guiding or short-exposure stacking depending on focal length
  • Permanent polar alignment and pier/tripod stability matter more than cosmetics
SENSORS

Safety and Site Sensors

  • Cloud sensor, rain sensor, humidity, wind, and temperature monitoring
  • Sky brightness meter for limiting magnitude estimates
  • GPS or NTP-disciplined time source for reliable observation timing
  • UPS/power monitoring and safe-shutdown automation

Hardware

Minimum Hardware Stack

  • Telescope: 80-150 mm fast wide-field optical tube
  • Camera: cooled monochrome astronomy camera, FITS capable
  • Mount: go-to equatorial mount with computer control
  • Computer: mini PC or Raspberry Pi 4/5 class controller
  • Accessories: electronic focuser, dew control, filter drawer or clear/luminance filter

Recommended Network Node

  • Telescope: 150-250 mm fast astrograph or corrected reflector
  • Camera: cooled mono CMOS with large sensor and high QE
  • Mount: mid/high-capacity EQ mount with plate-solve centering
  • Enclosure: roll-off roof, dome, or weather-safe automated cover
  • Networking: wired Ethernet preferred, Wi-Fi backup acceptable

High-Performance Node

  • Telescope: 280-400 mm aperture with corrected field
  • Camera: large-format mono cooled sensor, 16-bit preferred
  • Mount: observatory-class EQ mount with low periodic error
  • Timing: GPS/NTP disciplined clock and logged exposure start/end time
  • Operations: remote power, all-sky camera, weather station, and fail-safe roof control

Software

Capture and Observatory Control

  • N.I.N.A., KStars/Ekos, Voyager, Sequence Generator Pro, or equivalent
  • ASCOM on Windows or INDI on Linux/Raspberry Pi
  • PHD2 or mount-native guiding when required
  • Automated meridian flip, autofocus, and safe park/shutdown routines

Astrometry and Image Processing

  • ASTAP, astrometry.net, or local plate-solving index files
  • Siril, PixInsight, AstroImageJ, or Python/Astropy workflows for calibration
  • FITS header validation, dark/bias/flat calibration, and star quality checks
  • Astrometrica or equivalent tools for measuring object positions

Moving Object Detection and Reporting

  • Tycho Tracker, Find_Orb, MPChecker, JPL Horizons, and MPC tools
  • Python stack: astropy, photutils, astroquery, numpy, scipy, pandas
  • Scheduler/event bus: MQTT, NATS, or HTTPS API for node telemetry
  • Database: PostgreSQL/SQLite for observations, candidates, and audit logs

Operational note: asteroid/comet candidate reports should be reviewed by an experienced observer before submission or public alerting. Confirmed astrometry should follow Minor Planet Center-style observation practices, with accurate UTC timing, calibrated images, plate solutions, and traceable observer/site metadata.

Concept only: this is a high-level architecture for planning an automated asteroid tracking network. Operational impact warnings should be coordinated with recognized authorities such as MPC/IAWN/NASA/JPL and never auto-published without expert review.

TESS - Planetary Defense Foundation • Asteroid Watch Network