Section 11Simulation Runtime

Environment System requirements

Defines gravity, atmosphere, wind, precipitation, terrain, environmental fields, and their engineering effects.

Section relationships
IDNamePriorityRequirementVerification
ENV-001Environment field contractMVPAn environment field SHALL return a typed, unit-bearing value for a specified position and virtual time and SHALL declare its spatial and temporal domain.Test
ENV-002Deterministic field samplingMVPA deterministic environment configuration SHALL return equivalent samples for equivalent position, time, configuration, and seed.Test
ENV-003Uniform gravityMVPA world SHALL support a configurable uniform gravity vector.Test
ENV-004Spatial gravityFutureA world MAY support position- and time-dependent gravity fields.Analysis
ENV-005Atmosphere stateMVPA world SHALL support air density, pressure, temperature, and humidity as explicit environment properties.Test
ENV-006Uniform windMVPA world SHALL support a configurable uniform wind-velocity vector.Test
ENV-007Wind gustMVPA world SHALL support deterministic or seeded time-varying wind gusts.Test
ENV-008Spatial windBetaA world SHALL support a sampled three-dimensional wind field with interpolation metadata.Test
ENV-009Turbulence modelBetaA world SHOULD support at least one documented stochastic turbulence model with parameter provenance.Analysis
ENV-010Aerodynamic load approximationMVPThe Environment System SHALL compute a documented aerodynamic wrench from local air-relative velocity, sampled wind and air density, reference area, coefficient frame, coefficients, and center of pressure and SHALL apply it at a declared body frame and point.Analysis
ENV-011Aerodynamic surface modelBetaA model SHALL support surface-specific drag and lift parameters over a documented validity envelope.Analysis
ENV-012Rotor aerodynamic modelFutureBeforeMetal MAY support blade-element, momentum, wake, or externally coupled rotor models.Analysis
ENV-013Precipitation rateMVPA world SHALL represent rain using a typed precipitation-rate field.Test
ENV-014Surface wetnessMVPIn the reference weather workflow, surface wetness SHALL evolve from precipitation flux through a bounded exposure, accumulation, and drying model; direct wetness input SHALL be recorded as an explicit approximation.Test
ENV-015Wet contact effectMVPThe active contact model SHALL derive material-pair friction from surface wetness using a documented relationship and validity range.Analysis
ENV-016Visibility effectMVPPrecipitation and atmosphere models SHALL be able to expose visibility or attenuation inputs to supported sensors and rendering.Test
ENV-017Sensor weather queryMVPA sensor SHALL query environment properties through the same committed field state used by other subsystems.Test
ENV-018Weather timelineMVPAn experiment SHALL support scheduled changes in supported weather parameters.Test
ENV-019Weather randomizationBetaWeather parameters and field seeds SHALL be eligible for declared experiment distributions.Test
ENV-020Terrain geometryMVPA world SHALL support static plane, mesh, and documented height-field terrain representations.Test
ENV-021Terrain material regionsMVPTerrain SHALL support spatial regions with distinct engineering surface materials.Test
ENV-022Terrain slope and obstacle supportMVPThe reference rover world SHALL support slopes, steps, and rigid obstacles.Demonstration
ENV-023Surface temperatureBetaTerrain and exposed bodies SHALL be able to query or carry a simplified surface-temperature state.Test
ENV-024Thermal convection inputBetaAtmosphere and wind fields SHALL expose inputs required by supported convective-cooling approximations.Analysis
ENV-025Magnetic fieldBetaA world SHALL support a configurable magnetic-field vector for magnetometer simulation.Test
ENV-026Illumination stateBetaA world SHALL expose illumination state required by camera and light-sensitive sensor models.Test
ENV-027Water and puddlesFutureBeforeMetal MAY support standing water, buoyancy, added mass, drag, and free-surface effects through explicit fidelity levels.Analysis
ENV-028Ingress and corrosionFutureBeforeMetal MAY support calibrated moisture ingress, corrosion, and environment-driven failure models.Analysis
ENV-029External CFD fieldExternalBeforeMetal SHALL permit a precomputed or live external flow field to be sampled through an optional adapter.Demonstration
ENV-030Environment capability reportMVPEvery environment model SHALL report its outputs, rates, stochastic behavior, validity range, and required inputs.Inspection
ENV-031Precipitation occlusionBetaGeometry SHALL be able to shield surfaces and supported sensors from precipitation under a documented exposure model.Analysis
ENV-032Rain mechanical loadBetaConfigured exposed surfaces SHALL support a documented aggregate momentum-transfer model for rainfall.Analysis
ENV-033Fog and aerosol fieldBetaA world SHALL support a concentration or extinction field for documented fog, dust, smoke, or aerosol sensor effects.Analysis
ENV-034Snow and ice stateFutureA surface MAY carry snow or ice accumulation, traction, thermal, and melting state through explicit models.Analysis
ENV-035Vacuum and planetary atmosphereFutureA world MAY select vacuum, rarefied, or non-Earth atmosphere properties without changing canonical unit and field contracts.Analysis
ENV-036Radiative environmentFutureA world MAY expose solar, infrared, and other declared radiative fluxes to supported thermal, material, and sensor models.Analysis
ENV-037Environment provenanceMVPImported terrain, weather, and field data SHALL retain source, timestamp or epoch where applicable, spatial reference, resolution, and transformation metadata.Inspection
ENV-038World georeferenceBetaA world SHALL support a declared geodetic reference, origin, and mapping to the canonical local frame.Test
ENV-039Weather dataset importBetaBeforeMetal SHALL import time-series or gridded weather data through a documented schema with unit, time, and spatial validation.Test
ENV-040Field sampling policyMVPEvery sampled environment field SHALL declare resolution, interpolation, extrapolation, missing-data, boundary, and out-of-domain behavior.Inspection

Generated from the canonical specification. Edit section metadata or prose in docs/requirements.md; the website rebuilds this page and its relationships automatically.