Rings

Ring navigation models render the predicted appearance of a planet’s ring system and emit either per-edge polylines (the “edges resolve” path) or a per-planet annulus template (the “edges compress” path). Concrete subclasses derive from NavModelRingsBase, which carries shared annotation helpers (per-edge polyline + label rendering).

Registered concrete subclasses:

• NavModelRings — catalog-driven ring navigation; one instance per planet whose ring system has any radius inside the extended FOV. Documented at Ring Navigation Model.

• NavModelRingsSimulated — simulated-image GUI variant; emits a single RING_ANNULUS feature carrying the rendered template. Documented at Simulated Ring Navigation Model.

The nav.nav_model.rings subpackage holds the catalog-driven ring data model — validation, filtering, and rendering are separated so each concern can be tested in isolation (ring_types, ring_feature, ring_filter, ring_math, ring_render_context, ring_render_result).

• Ring Navigation Model
  • Overview
  • Theory
    • Edge rendering
    • Per-edge feature filtering
    • Curvature classification
    • Per-vertex covariance
    • Annulus template
    • Restrictions and assumptions
    • Sources of uncertainty
  • Configuration
    • rings block
    • Per-planet ring catalogue
    • Module-level emission constants
    • Per-instrument overrides
  • Implementation
    • Annotation helpers
    • Per-image metadata
    • Call path
  • Examples
• Simulated Ring Navigation Model
  • Overview
  • Theory
    • Restrictions and assumptions
    • Sources of uncertainty
  • Configuration
  • Implementation
    • Call path
  • Examples