Skip to content

Native aerosol migration

Migrate supported workflows to the flat native Aerosol, holding ParticleData, full ordered GasData, and EnvironmentData. V0.3.0 removes the legacy APIs and validates the resulting native-only execution boundaries after the v0.3.0 handoff.

See the v0.3.0 closeout record for revision-specific validation and outstanding readiness gates.

  • Construction and replacement: three-container assembly, native initializers, distribution measures, units and ownership.
  • Container access: raw arrays, detached properties, individual and coordinated replacement, and historical API terminology.
  • Dynamics: native batched CPU runnables, explicit species maps, and direct/resident GPU boundaries.
  • Troubleshooting: validation, gas order, normalization, storage replacement and explicit transfer errors.

The executable examples preserve useful initialization and scientific content. Historical facade names are reference material only; wrapping containers in a legacy facade is not a native migration technique.

ParticleData.volume owns represented volume. GasData retains all gas lanes, including nonpartitioning species. EnvironmentData owns per-box temperature and pressure and full gas-order saturation ratios. Activity, surface, vapor-pressure and other physical configuration belong to processes.

The five native CPU dynamics runnables support batched storage through a shared box loop; direct strategy methods remain single-box. Direct Warp and resident execution use explicit preparation and transfer, with their documented process-specific limits. The new prepared runnable workflow connects native aerosols to CUDA and detached CPU snapshots. Published GPU illustrations require actual CUDA; Warp CPU is separately labeled regression evidence.

Start with container foundations for the schema and native access for units. GPU gas restore requires externally retained names for semantic fidelity and drops device-only vapor-pressure state. Checkpoint inspection carriers are lossy; canonical device bytes, not those inspection carriers, govern explicit compatible restart.

The 0.2.13 plan retained both facades and native containers. In v0.3.0, particle, gas species, and atmosphere facades and their obsolete constructors have been removed. Native gas storage uses explicit box/species axes and retains mixed partitioning masks; vapor-pressure strategies belong to processes. Construct validated gas input with GasDataBuilder; negative input is rejected instead of silently clamped. Raw array mutation remains caller-owned and does not provide transactional validation. Direct and prepared GPU steps, CPU-Warp population transfers, and resident lifecycle boundaries now require explicit supported population metadata. Untagged v5 checkpoints reject before setup or upload without inferring their meaning. The closeout records implementation validation; maintainer review and release approval remain pending. Consult that revision-specific record for evidence. No performance qualification or cross-device continuation is implied.