From 941476150c628c9d08f68f03434c566dbeaa4872 Mon Sep 17 00:00:00 2001 From: deamonkai <26585050+deamonkai@users.noreply.github.com> Date: Sat, 28 Mar 2026 11:46:12 -0500 Subject: [PATCH] Document atmosphere model requirements --- MEMORY.md | 11 +++++++++-- README.md | 15 ++++++++++++--- 2 files changed, 21 insertions(+), 5 deletions(-) diff --git a/MEMORY.md b/MEMORY.md index 9e612ea..287065a 100644 --- a/MEMORY.md +++ b/MEMORY.md @@ -13,10 +13,11 @@ Be direct about scope creep — if a "quick fix" is turning into a multi-file re ## Guardrails -- Treat `/docs` as authoritative for assignment requirements and parameter values. +- Treat `/docs` and direct instructor clarifications as authoritative for assignment requirements and parameter values. - Do not invent missile or target thrust, mass, drag, or geometry tables. Transcribe them from the source packet and note what was extracted. - Preserve SI units unless a document explicitly states otherwise. - Keep [`code/Interceptor_3DOF.m`](./code/Interceptor_3DOF.m) as the primary entry point unless there is an intentional repo-wide refactor. +- When implementing the atmosphere helper, include the stratosphere branch for altitude `> 11 km`. - Do not describe the model as runnable until all `XX` placeholders are replaced and `getRho.m` exists. - Record every meaningful assumption, extracted constant, unresolved issue, and verification result here. - Use exact dates in status notes. @@ -30,6 +31,10 @@ Be direct about scope creep — if a "quick fix" is turning into a multi-file re - `docs/AERO 3220 3DOF Information Spring 26.pdf` - `docs/Atmosphere Model SI Units.pdf` - `docs/Missile and Target Data for 3DOF Spring 26.pdf` +- Instructor clarification documented on `2026-03-28`: + - The atmosphere model must be written and integrated into the simulation. + - The atmosphere implementation must include the stratosphere model for altitude `> 11 km`. + - The code will not run until the missing `XX` values are replaced with real numbers. - Assignment baseline confirmed from the handout: - Velocity pursuit guidance gain = `0.5` - Blind range = `2 m` @@ -51,12 +56,13 @@ Be direct about scope creep — if a "quick fix" is turning into a multi-file re - [`code/Interceptor_3DOF.m`](./code/Interceptor_3DOF.m) drives the integration loop, plotting, and CSV export. - [`code/T3dxdt.m`](./code/T3dxdt.m), [`code/M3dxdt.m`](./code/M3dxdt.m), and [`code/getGuidance.m`](./code/getGuidance.m) still contain `XX` placeholders. - `getRho.m` is referenced by the driver and both dynamics functions, but the file is missing. +- Because `getRho.m` does not exist yet, neither the lower-atmosphere branch nor the required stratosphere branch for `z > 11 km` is implemented in the repo. - [`code/getMD.m`](./code/getMD.m) exists and computes miss distance at the point of closest approach. - The missile/target data PDF appears image-based; a future agent should log the extraction method used when those tables are transcribed. ## Next Actions -1. Implement `getRho.m` from the atmosphere-model PDF. +1. Implement `getRho.m` and integrate it into the simulation, including the required stratosphere branch for altitude `> 11 km`. 2. Transcribe missile and target geometry, thrust, mass, and drag data from the missile/target packet. 3. Replace all remaining `XX` placeholders with sourced values. 4. Run the MATLAB model and verify the required plots and CSV outputs. @@ -73,3 +79,4 @@ After any meaningful change, update: ## Change Log - `2026-03-28`: Created `README.md` and `MEMORY.md` from the `/docs` PDFs and current MATLAB code. Confirmed the repo is still an incomplete assignment skeleton with unresolved placeholders and a missing `getRho.m`. +- `2026-03-28`: Documented professor guidance that the atmosphere model must be integrated into the simulation, must include the stratosphere branch for altitude `> 11 km`, and will not run until the `XX` placeholders are replaced. diff --git a/README.md b/README.md index 021054c..eddc4bc 100644 --- a/README.md +++ b/README.md @@ -5,9 +5,17 @@ Hayden Project is a MATLAB 3DOF interceptor-versus-target engagement simulation ## What The Docs Define - [`docs/AERO 3220 3DOF Information Spring 26.pdf`](./docs/AERO%203220%203DOF%20Information%20Spring%2026.pdf) defines the assignment, required plots, and evaluation settings. -- [`docs/Atmosphere Model SI Units.pdf`](./docs/Atmosphere%20Model%20SI%20Units.pdf) provides the SI-unit atmosphere equations for temperature, pressure, density, acoustic speed, and Mach number. +- [`docs/Atmosphere Model SI Units.pdf`](./docs/Atmosphere%20Model%20SI%20Units.pdf) provides the SI-unit atmosphere equations for temperature, pressure, density, acoustic speed, and Mach number for the lower-atmosphere branch shown in the handout. - [`docs/Missile and Target Data for 3DOF Spring 26.pdf`](./docs/Missile%20and%20Target%20Data%20for%203DOF%20Spring%2026.pdf) is the source packet for the missile and target geometry, propulsion, and drag data that must be transcribed into the simulation. +## Instructor Clarification + +Per professor guidance documented on `2026-03-28`: + +- The atmosphere model must be written and integrated into the 3DOF simulation. +- The final atmosphere implementation must include the stratosphere model for altitudes above `11 km`. +- The source files are intentionally incomplete until the missing `XX` values are replaced with real numbers from the assignment material. + ## Assignment Baseline The course handout specifies these evaluation values: @@ -39,13 +47,14 @@ The required outputs are: At the moment, the repository is a partially completed assignment skeleton rather than a finished simulation: - Multiple required values are still marked as `XX`. -- `getRho.m` is referenced by the code but is not present in the repository. +- `getRho.m` is referenced by the code but is not present in the repository, so the atmosphere model has not been integrated yet. +- When `getRho.m` is added, it must support both the lower-atmosphere branch and the required stratosphere branch for `z > 11 km`. - The missile/target data packet still needs to be fully transcribed into MATLAB arrays and constants. ## Working Expectations - Keep units in SI unless a source document explicitly states otherwise. -- Treat `/docs` as the authoritative source for assignment requirements and parameter values. +- Treat `/docs` and direct instructor clarifications as authoritative for assignment requirements and parameter values. - Record assumptions, extracted tables, unresolved issues, and verification status in [`MEMORY.md`](./MEMORY.md). ## For AI Agents