Physical setup
The blast problem evolves an initially localized energy deposition with coupled gas and radiation. Its useful diagnostics include shock position, gas and radiation temperatures, density, and outward radiation flux.
Ensman's original problem is a spherical shell from 1012 to 1013 cm with ρ(r) = 10−6(r/1012 cm)−7 g/cm³. The shell is initially in radiative equilibrium with luminosity 1034 erg/s. An energy of 1047 erg is deposited in the innermost zone, followed by zero inner luminosity and velocity. The opacity uses the electron-scattering coefficient as pure absorption. This stratified spherical setup is distinct from a uniform-medium Cartesian thermal bomb.
Spherical blast on a Cartesian mesh. The initial density, gas and radiation temperatures, radiation flux, and Gaussian energy deposition depend only on radius. The computational box spans ±1013 cm and contains a filled core of radius R0 = 1012 cm. Density is 10−6[max(r,R0)/R0]−7 g/cm³. The 1047 erg gas-energy deposition is a Gaussian of width R0. Exact error-function cell integrals and finite-box normalization preserve its total at every uniform-grid resolution. The initial radiation field uses an LTE diffusion envelope based on luminosity 1034 erg/s and outer E = L/(4πcRout²), with a regularized core. A streaming floor E ≥ (1 + 10−12)|F|/c keeps the approximate atmosphere realizable while preserving its radial flux. The central luminosity is removed when evolution starts. The default duration is 22000 s.
The filled core, Gaussian deposition width, Cartesian grid, M1 closure, streaming floor, and approximate LTE diffusion initialization are deliberate adaptations. They differ from the original hollow shell, innermost Lagrangian-zone deposition, and radiation-transfer relaxation.
These cases enable gas dynamics and radiation coupling on a Cartesian grid; gravity is disabled. Uniform runs are the default; adaptive runs are identified in their recorded setup. Each completed run records its actual configuration, time, units, and executable hash below. The configured finest equivalent cells per side are N = INX × 2level.
Comparison and interpretation
This problem is available for M1 RK1 only in the current runner. No FLD result is claimed.
No analytic radiative blast profile is supplied. Ensman (1994), Figures 17–22, follows the original numerical solution from energy deposition through radiative breakout and later shell formation.
What the Sedov–Taylor limit can tell us
For an energy-conserving point explosion into a cold, uniform medium with negligible radiative losses, the spherical similarity solution gives
This is a useful separate adiabatic benchmark. It is not an analytic solution of the present radiating blast: the finite Gaussian deposition, filled core, steep r−7 envelope, initial radiation field, and escaping luminosity introduce different scales and energy transport. Substituting the envelope exponent into a simple power-law Sedov formula does not provide a valid reference for this truncated atmosphere. Quantitative validation here requires conservation and resolution studies plus an independent radiation-hydrodynamics solution with the same setup.
What this test measures
Track the shock and radiation precursor separately, together with energy exchange and boundary losses. In Ensman's original calculation the precursor breaks out near 5800 s and the luminosity peaks near 9600 s. These times depend on that paper's shell and boundary conditions; they are not pass/fail thresholds for an adapted setup.
All resolutions
No completed run is available for this problem in this batch. Its description is available above; results will appear here as runs finish.
Unsupported by the stationary FLD backend; no FLD run is planned for this problem.
Reading the numerical profiles
Gas and radiation temperatures are distinct diagnostics; the radiation temperature is defined by E = arTr4. The central ray lies at y = z = Δx/2 and is offset from the exact origin by half a cell in each transverse direction. The two-dimensional plane is z = Δx/2.
Check positivity, radiation realizability |F| ≤ cE, conservation with the appropriate boundary budget, thermal equilibration, shock speed and precursor structure, and sensitivity to resolution and timestep. A finite, positive short run is an implementation check, not evidence that a subcritical or supercritical state has developed. Comparisons to published figures also require matching geometry, opacities, boundaries, and physical time.
Where this problem comes from
Ensman (1994), ApJ 424, 275, §5.3, pp. 286–290, Figures 17–22; original paper PDF. Published profiles are numerical evidence, not an analytic reference. The local runs retain their actual numerical parameters and elapsed physical time.
Radiation method context
M1 RK1 evolves radiation energy and flux moments with the retained first-order radiation update. FLD evolves radiation energy and stationary material thermal energy with a coupled backward-Euler solve; its flux F = −D∇E is reconstructed from energy with the Levermore–Pomraning limiter. The scalar implicit transport solve uses composite-grid multigrid and an iterative linear solver. Both time integrators are first order.
The FLD runner currently supports the stationary Gaussian scattering pulse and Marshak heating test on the CPU at physical light speed. Streaming wave/front, equilibrium sphere, and moving radiation hydrodynamics are unsupported for FLD. Flux diagnostics in FLD are not independently evolved M1 moments and have no separate M1 momentum conservation test. A difference between paired M1 and FLD solutions is a model comparison, not an analytic error. ADER2 has been removed from the current solver; historical result files retain their original provenance.
Skinner & Ostriker (2013) and Hanawa & Audit (2014) provide context for the M1 equations. The implementation and saved executable/source hashes identify the actual numerical methods used in this batch.
Reproducing this batch
Descriptions document the reviewed source implementation. Older or edited solver versions can use different profile constants or averaging rules; these are not all encoded in run.ini. Use the run metadata, executable hash, and saved batch source hashes to identify the implementation behind a result. A source path or descriptive formula alone is not proof of the executable's contents.