Skip to content

Native migration troubleshooting

Set distribution_type through a native initializer/builder or explicit ParticleData construction. Choose the physical measure deliberately:

  • discrete: bin number density, m⁻³, at exactly unit volume.
  • continuous_pdf: radius dN/dr, m⁻⁴, with a positive increasing radius grid and exactly unit volume. Integrate over radius; do not sum nodes.
  • particle_resolved: represented counts at positive physical volume. Density input must be multiplied by volume once; density output divides once.

An untagged legacy carrier is not native. Facade wrapping or stripping a tag is not a workaround. For initializers, concentration_units="count" preserves weights; explicit density units convert to counts using represented volume.

Particle masses use (B,N,P), counts/weights and charge (B,N), density (P,) and volume (B,). Full gas concentration and environment saturation ratios use (B,G). Temperature and pressure use (B,); molar mass and gas flags use (G,). Particle and gas species widths may differ. Keep every gas lane, including inert species.

Individual assignments validate against held peers. To change a gas width and its matching environment width together, use aerosol.replace_data with all three candidate containers. Rejection preserves held identities and candidate state. Construction/replacement validates structure and representation, not all later physical requirements or an unnamed permutation of chemistry. See the executable replacement checks.

A process rejects state after successful construction

Section titled “A process rejects state after successful construction”

Raw arrays are writable; direct edits may introduce negative/nonfinite values. Processes revalidate their own physical domain and full expected gas order. Reordering or replacing gas does not update old process configuration. Recreate its explicit mapping only when the new order is intentional. Do not catch the error and retry with a facade.

Resolved coagulation requires equal positive active counts. Fractional counts are valid storage but that does not imply every process supports arbitrary weights. Binned coagulation also retains method-specific composition limits. Consult the process documentation instead of changing conservation tolerances.

Multi-box execution requires the runnable boundary

Section titled “Multi-box execution requires the runnable boundary”

The five native dynamics runnables iterate boxes transactionally. Direct strategy methods remain single-box. Supply CPUExecutionContext(root_seed, box_ids) for stochastic multi-box calls, with one stable logical ID per box. Each batch retains one population label and shared process configuration. Equilibria remains a separately documented native-data migration gap. See dynamics migration.

Native condensation and nucleation bindings pin the exact carriers, arrays, devices, population metadata and complete gas-name provenance. Prepare them explicitly after conversion. Replacing CPU containers does not change existing device state; replacing Warp storage or restarting a resident session needs fresh explicit preparation. Radius-PDF particle upload is unsupported.

Direct condensation requires thermodynamics=. Supply either environment= or both direct temperature/pressure inputs, never both forms. Direct arrays must have shape (B,), positive finite values and the active device. Configuration, scratch and diagnostic arrays must match their documented per-material, full-gas or per-box shapes and dtypes; equal widths are not a species map.

WarpGasData does not own gas names. Pass the saved full ordered names to from_warp_gas_data; otherwise placeholders are produced. CPU GasData has no vapor-pressure field, so this device-only derived state is dropped on restore. Normal condensation refreshes it from current temperature and thermodynamics. Synchronize before host observation, or use the conversion helper’s documented synchronization mode.

Checkpoint CPU inspection carriers are also lossy. Explicit restart consumes canonical schema-v5 bytes on an exactly compatible device; it does not rebuild continuation from inspection data or silently migrate an old schema.

Run the published scripts and their owning examples_tests suites from the repository checkout. Published GPU figures require CUDA; portable regression helpers may explicitly use Warp CPU. Optional generic CUDA tests skip when unavailable, while strict GPU qualification rejects missing execution. Capture has no CPU fallback. A no-Warp result must report that no kernel ran, not claim physics parity. See focused reproduction commands.