Skip to content

README.md

Latest commit

 

History

History
149 lines (120 loc) · 3.37 KB

README.md

File metadata and controls

149 lines (120 loc) · 3.37 KB

Missile Detection System (C++)

pak

Overview

  • Simulation of a Missile Approach Warning System (MAWS)
  • Processes UV/IR sensor data to detect incoming missile threats
  • Inspired by real-time avionics and defense system design
  • Built for educational and demonstration purposes

Key Features

  • Real-time sensor data processing
  • Missile plume signature detection
  • Multi-target tracking (up to 8 concurrent tracks)
  • Time-to-impact (TTI) estimation
  • Threat confidence classification
  • Simulated cockpit warning and countermeasure triggering

System Architecture

Sensor Input Layer

  • Represents raw hardware sensor output
  • Data fields:
    • timestamp_us (microsecond precision)
    • ir_intensity
    • uv_intensity
    • azimuth_deg
    • elevation_deg
    • delta_intensity
    • sensor_valid

Plume Signature Detection

  • Filters and validates missile-like signatures
  • Detection criteria:
    • Minimum IR threshold
    • Minimum UV threshold
    • UV/IR ratio within defined bounds
    • Minimum intensity growth rate
    • Sun-glint rejection logic
  • Eliminates false positives (e.g. sunlight reflections, flares)

Threat Tracking System

  • Tracks multiple objects simultaneously
  • Key characteristics:
    • Maximum of 8 active tracks
    • Spatial association using angular distance (azimuth/elevation)
    • Track confirmation requires multiple frames
    • Circular buffer for intensity history
  • Prevents false alarms from single-frame noise

Impact Estimation

  • Estimates time-to-impact (TTI)
  • Based on:
    • Intensity growth between consecutive readings
    • Approximation of inverse-square law behavior
  • Output range:
    • Minimum: 1 second
    • Maximum: 99 seconds (fallback/default)

Threat Assessment

  • Produces structured output:
    • Threat detected (boolean)
    • Confidence level:
      • NONE
      • LOW
      • MEDIUM
      • HIGH
      • CERTAIN
    • Direction (azimuth/elevation)
    • Time-to-impact
    • Track ID

Warning & Countermeasure Logic

  • Trigger conditions:
    • HIGH confidence → cockpit warning
    • CERTAIN confidence (TTI < 4s) → automatic flare deployment
  • Simulated actions:
    • Audio alert ("MISSILE WARNING")
    • Visual marker (Helmet Mounted Display)
    • Countermeasure deployment signal

Design Principles

  • Deterministic execution
    • No dynamic memory allocation
    • Fixed-size arrays
  • Real-time safety
    • Predictable timing
    • No exceptions
  • Fault tolerance
    • Sensor health checked before processing
  • Modular architecture
    • Independent components:
      • Detector
      • Tracker
      • Estimator
  • Multi-frame validation
    • Reduces false positives

Constraints & Assumptions

  • Simplified physics model for impact estimation
  • Fixed thresholds (illustrative, not real-world values)
  • No external dependencies (STL avoided for predictability)
  • Maximum 8 simultaneous tracked threats
  • Sensor input assumed at fixed time intervals (~20 ms)

Example Flow

  1. Sensor produces a reading
  2. System validates sensor health
  3. Plume signature detection runs
  4. If valid:
    • Track is updated or created
  5. Track is confirmed across multiple frames
  6. Time-to-impact is estimated
  7. Threat assessment is generated
  8. Warning or countermeasure is triggered (if required)

Build & Run

Requirements

  • C++17 or later
  • Any standard compiler (g++, clang, MSVC)

Compile

g++ -std=c++17 main.cpp -o maws