AEROSIM-TS-34
Verify rendered and collision elevation parity
Representative probes demonstrate that rendered and collision elevations remain within the documented tolerance across the terrain fixture.
- Verified flow state
- Done
- Owner
- AeroSim Architecture and Delivery
- Feature
- AEROSIM-FT-47
- Component
- Web Application and shared flight-core — terrain parity tests
- Repository
- corp-v1-aerosim/corp-v1-aerosim
Delivery scope
Compare the renderer sampleHeight and Rapier collisionHeightAt functions at named flat, slope, peak, valley, edge, and bilinear interior probes on ridge-5x5, using an explicit 1e-4 world-unit elevation tolerance. Primary files: tests/integration/terrain/elevation-parity.test.ts, tests/integration/terrain/terrain-probes.ts, packages/flight-core/tests/fixtures/ridge-5x5.json.
Implementation contract
Implementation artifacts
- tests/integration/terrain/elevation-parity.test.ts
- tests/integration/terrain/terrain-probes.ts
- packages/flight-core/tests/fixtures/ridge-5x5.json
Inputs
- Named TerrainProbe records {name,x,z,expectedClass} over ridge-5x5
- Rendered and collision elevation samplers created from the identical NormalizedHeightData object
Outputs
- Per-probe ElevationParityResult {visual,collision,delta,withinTolerance}
- Repeatable parity summary with maximum delta and probe name
Failure boundaries
- Fail if either sampler returns non-finite or out-of-bounds data for an in-bounds probe.
- Fail when delta exceeds 1e-4 and report coordinate plus both coordinate transforms.
Excluded scope
- Pixel comparison, artistic terrain appearance, geospatial accuracy, and contact dynamics beyond surface elevation are excluded.
Verification steps
- pnpm test:integration -- elevation-parity.test.ts
- Run probes in forward and reversed order three times; assert the same maximum delta and no mutation of normalized samples.
Traceability
Dependencies
- AEROSIM-TS-33Canonical ID: TASK-0033
UI/UX applicability
non_visual
This Task owns technical or behavioral acceptance and does not claim direct visual conformance to the approved UI/UX package.
Acceptance evidence
Verified delivery: initial application PR #68 reviewed head 28da6592ab66f6e27c48cbc0a06c2b43042dd9ba, exact-head required validation tasks 2191 and 2193 succeeded, and merged as 16845882557025df3bf4abfaadf5dd9761c7cab6. Updated-gate repair PR #111 reviewed head f971228348865cc2e103f937c8d182e920dfe1fd passed exact-head pull-request tasks 3004, 3005, 3006, 3007, 3008, 3009, and 3010; merged as db4c92a68c157b7bbca7bbd9cb3fe51ae1a16f61; integrated application head db4c92a68c157b7bbca7bbd9cb3fe51ae1a16f61 passed required-validation task 3011, validate task 3012, build-images task 3013, and publish-images task 3014. Release completion verified on product 1.0.0.0 at GitOps revision 5d3712d89dfbf7dacd993348e55f497d126c7bf9 with Argo Synced/Healthy, exact image digests, authenticated API/database access, and three-world configured-flight acceptance.
Current evidence boundary
No current implementation, acceptance, release, or deployment evidence is claimed for this planned Task. Any prior implementation may be used only as prototype and discovery evidence.