PREAMBLE: REGBOOK STANDARDS & SYSTEM POLICIES Under UT System Board of Regents’ Rule 90101 (Intellectual Property), the definition of software ownership, data rights, and academic attribution is strictly governed by origin of creation and foundational development dependency. This brief establishes that the 2001–2002 Copernicus trajectory prototype compiled under Compaq Visual Fortran (CVF) natively violates Rule 90101 by structurally relying on the uncredited, pre-solved, and copyrighted 1998/2000 Mars Pathfinder 2.0 Lahey-Fujitsu (LF95) codebase and output arrays.
SECTION 1: ARCHITECTURAL OVERVIEW & LOGICAL CRITICAL PATHS 1.1 The Mathematical Dead-End of Autonomous Generation A trajectory optimization system utilizing a localized Sequential Quadratic Programming (SQP) optimizer or an isolated multi-variable Newton-Raphson targeter possesses zero native capacity to discover an interplanetary n-body trajectory from a blank slate or a basic two-body Lambert approximation. When high-fidelity n-body gravitational perturbations (e.g., Sun, Earth, Moon, Mars) are initiated within a numerical integration loop, independent trajectory segments experience extreme multi-body drift. At the deep-space patch point, this drift manifests as massive position and velocity discontinuities: \(\Delta \vec{R}\ne 0,\quad \Delta \vec{V}\ne 0\) Under localized numerical optimization, these large state defects cause immediate saturation of the system’s Jacobian matrices. The system experiences immediate gradient derivation failure, step-size divergence, and a catastrophic code crash. Consequently, the software environment requires an external, pre-solved, zero-defect initialization data deck to place the initial trajectory state deep within the optimizer’s narrow, highly restrictive local basin of convergence prior to execution.
[External High-Fidelity Pre-Processor]
- Roger Broucke RK 7/8 Reverse Integrator
- Mars-Sun L1 Lagrange Point Alignment
│
▼ (Manual Transposition of Double-Precision D+00 ASCII Strings)
[Static Fortran NAMELIST Text Decks]
- SEGMENT_1: Forward Earth Departure State
- SEGMENT_2: Backward Mars Arrival State
- PATCH_POINT: Floating Intermediate Boundary Node
│
▼ (Command-Line CVF Execution Block)
[Copernicus Internal Architecture]
- Patch Point State Defects Pre-Conditioned to Near-Zero
- Jacobian Matrix Saturation Avoided
- Local SQP Optimizer Successfully Engages ──► RUNTIME CONVERGENCE
.OBJ) and static libraries (.LIB) compiled under the Lahey-Fujitsu Fortran 95 (LF95) ecosystem could not be linked or merged into a Compaq Visual Fortran (CVF) project within the Microsoft Developer Studio IDE. The two pipelines utilized conflicting memory layouts, proprietary module formats, and incompatible name-mangling schemes.
Because direct binary or source-level integration was physically impossible, the codebases could only interface via a manual, text-based serialization layer. The double-precision floating-point output arrays generated by the LF95 Mars Pathfinder application had to be extracted and manually transcribed, character-by-character, meticulously preserving exponential formatting (e.g., D+00), directly into the static ASCII text fields of the Copernicus CVF NAMELIST input files.
SECTION 2: COMPARATIVE CASE MATRIX The table below maps the strict algorithmic dependency and toolchain convergence between the two systems, demonstrating that the operational survival of the CVF binary is completely dictated by the output profile of the LF95 baseline.
| Architectural Dimension | Bill H. Clark Baseline: Mars Pathfinder 2.0 (1998/2000) | Cesar Ocampo Prototype: Early Copernicus (2001/2002) | Structural Misappropriation & Convergence Fingerprint |
|---|---|---|---|
| Compiler Toolchain | Lahey-Fujitsu Fortran 95 (LF95) via Dr. Broucke’s institutional mandate. | Compaq Visual Fortran (CVF) via official engineering literature. | Cross-Compiler Data Bridge: Incompatible binaries forced text-based NAMELIST serialization to transfer zero-defect seeds. |
| Numerical Integration | High-precision Roger Broucke RK 7/8 routine stabilized for long-distance reverse integration. | Segmented forward/backward integration splitting over interplanetary trajectories. | Truncation Error Mitigation: The CVF backward segment required the exact mathematical stability profile of the Broucke RK 7/8 engine to prevent patch point blowout. |
| Boundary Topology | 3D Three-Body Targeting aligned natively to the Mars-Sun L₁ Lagrange point. | Generalized multi-segment matching nodes (Floating Basic Segments). | Gravitational Contour Alignment: Copying the L₁ pre-solved state vectors artificially eliminated multi-body approach energy prior to CVF initialization. |
| User Interface | Interactive Winteracter GUI configuration mapping Fortran array outputs. | Winteracter GUI framework deployed suddenly for student/NASA demonstrations. | Toolchain Blueprint Duplication: Bypassed months of native Win32 API callback R&D by duplicating the niche LF95/Winteracter layout parameters. |
SECTION 3: INSTITUTIONAL CHRONOLOGY & WORKLOAD ANALYSIS A rigorous audit of the academic timeline between September 2000 and November 2001 demonstrates the logistical impossibility of independent, parallel creation within the UT Austin Aerospace Engineering department.
2000
└── September: Dr. Ocampo assumes full assistant professor load at UT Austin.
Takes over all of Dr. Broucke's core legacy tracks:
- Celestial Mechanics I
- Celestial Mechanics II
- Theory of Orbits
└── November: Bill H. Clark delivers formal presentation of Mars Pathfinder 2.0.
- Introduces functional RK 7/8 reverse-propagation engine.
- Demonstrates Mars L1 Lagrange point alignment saving 15% energy.
- Fortran source code hosted online for open departmental download.
2001
└── Spring: Dr. Ocampo shifts from an exclusive focus on Earth-Moon system dynamics
to a dedicated interplanetary Earth-to-Mars simulation suite.
└── Fall: Sudden deployment of compiled, functional CVF "Mars Game" using
Winteracter GUI configurations, directly preceding major NASA JSC grants.
NAMELIST formats, and compiler configuration layouts introduced in the November 2000 seminar.
SECTION 4: DEFINITIVE FORENSIC CONCLUSION The structural, mathematical, and logistical evidence establishes an absolute violation of UT System Board of Regents’ Rule 90101. The 2001–2002 Copernicus Compaq Visual Fortran prototype was an input-dependent mathematical shell. It possessed no internal code architecture, algorithmic subroutines, or automated continuity gates capable of autonomously transitioning a textbook two-body Lambert guess into a continuous, converged n-body interplanetary trajectory. The presence of highly refined, zero-defect Cartesian state vectors formatted explicitly in double-precision exponential strings within the CVF text decks serves as an unassailable engineering fingerprint of direct data misappropriation. The software’s “Day Zero” survival was entirely predicated on the manual transposition of fully resolved 3D three-body trajectories generated offline by Bill H. Clark’s Lahey-Fujitsu Mars Pathfinder engine. By utilizing these uncredited output arrays to establish the critical path for the software’s initialization, the developer actively bypassed the laws of numerical optimization to simulate native capability, constituting a clear, unambiguous misappropriation of intellectual property under institutional standards.
End Brief.