GD_xPRIMEray: Curved Ray Transport Engine for GRIN Fields¶
A research-grade ray propagation framework for Godot, combining gradient-index (GRIN) optics with symbolic + numerical ray integration.
Positioned as both a scientific research toolkit and an open-source GPU/CPU optical transport engine.
Overview¶
GD_xPRIMEray is a hybrid symbolic-numeric ray transport system built on Godot Engine. It augments Godotβs renderer with curved ray physics β enabling simulation of graded refractive media, advanced optical phenomena, and non-Euclidean propagation domains.
Rather than tracing straight rays through space, GD_xPRIMEray integrates rays through fields defined by continuous curvature functions, enabling higher-fidelity modeling of refractive and metric-driven transport.
Documentation Hub¶
Start here¶
- System Architecture β compact pipeline summary
- Architecture Overview β renderer structure and subsystem boundaries
- Architecture Review β deeper review of renderer behavior and architecture constraints
- Code Map (Big 12) β contributor-facing code map
- Validation Framework β validation modes and verification context
- Boundary Layer Fixtures β validation fixtures for BoundaryLayerVolume crossing behavior, policies, and nested shell ordering
- Specification Index β full spec map, current vs legacy, and support docs
- Architecture Charter (Current) β current working charter
Physics and transport references¶
- Metric Null Geodesic Parameter Map
- Next-Generation Metric Transport Roadmap
- BlackHole Fast Compare (GRIN vs Metric)
- Property Surface
- RenderStep Gate Hierarchy Snapshot
Current / revised specifications¶
- SceneSnapshot Data Layout (Revised)
- Field System (GRIN Evaluation) β Revised
- FieldSource3D Canonical Params + Legacy Compatibility
- Metric Models (GRIN vs Gordon / Transport Tier Roadmap) β Revised
- Field Extraction Rules (Godot β SceneSnapshot) β Revised
- Curved Ray Segment Integration β Revised
- BVH Acceleration System β Revised
- Scheduler & Task Graph β Revised
- Rendering Backends
- Telemetry, Debug, and Diagnostics
- Ray Transport & Portability Interfaces
- Research Mode
- Wormhole Multi-Scene System
Legacy baseline specifications¶
These are still useful for historical context and design evolution comparison.
- SceneSnapshot Data Layout (Legacy)
- Field System (GRIN Evaluation) β Legacy
- Metric Models (GRIN vs Gordon Metric / Gravity Mode) β Legacy
- Field Extraction Rules (Legacy)
- Curved Ray Chunk Integration (Legacy)
- BVH Acceleration System (Legacy)
- Scheduler & Task Graph (Legacy)
Calibration roadmap patch logs¶
- C1.0 g.1 β Parse/export canonical signature fields
- C1.7 g.X β AutoCal weak-signal FieldHeavy delta-aware stopgap
π¬ Research & Experimental Frameworks¶
- Fixture Research Note Pattern β shared note/template guidance, including canonical analysis basis declarations for future fixtures
- Fixture 001: Radial GRIN Baseline β baseline note for the A2 scheduler-clean run plus the first fully verified control-surface characterization pass
- Fixture 002: Linear Transport Baseline β next sub-canonical / xZeno-canonical characterization fixture using the same hardened pipeline with a simpler single-row control surface
- Fixture 003: Offset Field Baseline β first spatial-regime shift after Fixture 002, keeping the single-row topology while moving the field center off-axis to create a clean asymmetry baseline
- Fixture 004: Dual Attractor Baseline β first multi-attractor characterization fixture, keeping the Fixture 003 operating style while replacing the single field center with two controlled horizontal attractors
Symmetric fixtures usually map cleanly to image-center analysis because the effective field center and image center remain aligned. Asymmetric fixtures should prefer field-relative analysis as the primary basis, while keeping image-center artifacts as companion diagnostics for screen-space interpretation.
Archive¶
- _arch_charter_MASTER_v0-Chat52
- _arch_charter_MASTER_v1-Alt-RESEARCHMODE
- _arch_charter_MASTER_v1-Alt-otherUpdated
- _arch_charter_MASTER_v1-Baseline-Gravity
- _arch_charter_MASTER_v2-Chat52
- _xPRIMEray_arch_charter_MASTER_v3-ChatClaudeCoherencePass1
- _xPRIMEray_arch_charter_v2-Claude45
- _xPRIMEray_arch_charter_v2-Claude46
Notes¶
- The MkDocs configuration should set
docs_dir: Docsso GitHub Actions builds from the correct capitalized folder. - The current navigation treats
_1spec files as the active revised versions, while the non-_1files are retained as legacy baselines. - The current
index.mdintentionally avoids linking to non-existent assets likeicon.webpor missing screenshot paths.