{"id":463246,"date":"2026-09-03T23:25:46","date_gmt":"2026-09-03T23:25:46","guid":{"rendered":"https:\/\/innovationspace.ansys.com\/forum\/forums\/topic\/r1411-mpp-full-deck-restart-nd3full01-corrupted-thermal-state\/"},"modified":"2026-09-03T23:25:46","modified_gmt":"2026-09-03T23:25:46","slug":"r1411-mpp-full-deck-restart-nd3full01-corrupted-thermal-state","status":"publish","type":"topic","link":"https:\/\/innovationspace.ansys.com\/forum\/forums\/topic\/r1411-mpp-full-deck-restart-nd3full01-corrupted-thermal-state\/","title":{"rendered":"R14.1.1 MPP full-deck restart (n=d3full01): corrupted thermal state"},"content":{"rendered":"
Hi all,<\/div>\n
 <\/div>\n
I am running a repeated-impact simulation chain and I cannot get the<\/div>\n
full-deck restart to work in R14.1.1. I would appreciate any insight into<\/div>\n
whether thermal-state restore on full restart is expected to work for a<\/div>\n
coupled S-ALE multi-material model with a phase-change thermal material,<\/div>\n
and whether the boundary-condition crash described below is a known issue.<\/div>\n
 <\/div>\n
SOLVER \/ ENVIRONMENT<\/div>\n
– ANSYS 2025 R2 (v252): lsdyna_mpp_dp_msmpi.exe and lsdyna_mpp_dp_impi.exe<\/div>\n
– Both report: LS-DYNA MPP double precision, Revision R14.1.1-16-gfadfb49b17<\/div>\n
  (MS MPI V10.0 and Intel MPI builds respectively)<\/div>\n
– Windows 10\/11 x64, 16 MPI processes, double precision<\/div>\n
– Both the initial run and the restart use the same revision and the same<\/div>\n
  number of processes, so the d3full version\/rank-count requirements are met.<\/div>\n
 <\/div>\n
MODEL (initial run, “Impact 01”)<\/div>\n
– 2D axisymmetric S-ALE, coupled structural-thermal:<\/div>\n
    *SECTION_ALE2D (ALEFORM=11, ELFORM=14)<\/div>\n
    *ALE_STRUCTURED_MESH + *ALE_STRUCTURED_MESH_CONTROL_POINTS<\/div>\n
    *ALE_STRUCTURED_MESH_VOLUME_FILLING (ALL \/ BOXCOR \/ ELLIPSOID with<\/div>\n
     velocity vector via VID)<\/div>\n
    *ALE_MULTI-MATERIAL_GROUP (3 AMMGs)<\/div>\n
– Materials:<\/div>\n
    *MAT_JOHNSON_COOK (MAT_015) + *EOS_GRUNEISEN for the HSLA-100 target<\/div>\n
    *MAT_ELASTIC_PLASTIC_HYDRO (MAT_010) + *EOS_GRUNEISEN for the WC<\/div>\n
     projectile (2220 m\/s)<\/div>\n
    *MAT_ALE_VACUUM for the surrounding void<\/div>\n
– Thermal:<\/div>\n
    *MAT_THERMAL_ISOTROPIC_PHASE_CHANGE for the target (T09)<\/div>\n
    *MAT_THERMAL_ISOTROPIC for projectile and vacuum<\/div>\n
    *CONTROL_SOLUTION SOLN=2 (coupled)<\/div>\n
    *CONTROL_THERMAL_SOLVER SOLVER=12, EQHEAT=1, FWORK=0.9<\/div>\n
    *CONTROL_THERMAL_TIMESTEP \/ *CONTROL_THERMAL_NONLINEAR<\/div>\n
    *INITIAL_TEMPERATURE_SET (NSID=0, 296.15 K)<\/div>\n
– Boundary conditions via *BOUNDARY_SALE_MESH_FACE: SYM on the axis face<\/div>\n
  (negx), NONREFL on the posx\/negy\/posy faces.<\/div>\n
– *DATABASE_BINARY_D3DUMP writes d3dump01\/d3full01 at t = 5.3e-5 s.<\/div>\n
– *CONTROL_MPP_DECOMPOSITION_DISTRIBUTE_ALE_ELEMENTS is used.<\/div>\n
 <\/div>\n
The initial run terminates NORMALLY at t = 5.3e-5 s (4845 cycles) with a<\/div>\n
physically sound thermal state (final temperature norm ~1.0e5, nonlinear<\/div>\n
thermal residual norms ~1e4-1e6). d3dump01 and d3full01.0000-0015 are<\/div>\n
written as expected.<\/div>\n
 <\/div>\n
RESTART RUN (“Impact 02”)<\/div>\n
Full-deck restart deck = full model + *STRESS_INITIALIZATION (PIDO=10,<\/div>\n
PIDN=0, the S-ALE mesh part) + a new *ALE_STRUCTURED_MESH_VOLUME_FILLING<\/div>\n
(ELLIPSOID, with VID) introducing a second projectile. Executed with:<\/div>\n
    mpiexec -np 16 lsdyna_mpp_dp_xxxmpi.exe i=restart.k n=d3full01 memory=200m<\/div>\n
The restart reads the dump correctly (problem time 5.3000e-5, cycle 4845,<\/div>\n
“material 10 in restart file initializes”), but then fails at the very<\/div>\n
first cycle in TWO distinct ways:<\/div>\n
 <\/div>\n
FAILURE 1 – thermal solver divergence, Error 40359 (SOL+359):<\/div>\n
    “the minimum time step has been reached and the maximum temperature<\/div>\n
     change is greater than specified”<\/div>\n
    solution time 5.3000e-5, node 6234 (inside the previously impacted,<\/div>\n
    hot region of the target), temperature change 5.2976e+12.<\/div>\n
  The first thermal solve after restart has an initial residual norm of<\/div>\n
  7.4432e+22, i.e. 18 orders of magnitude larger than any thermal solve in<\/div>\n
  the healthy initial run (~1e4-1e6). During the Newton iterations the<\/div>\n
  trial temperatures drop to ~112 K in material that ended the initial run<\/div>\n
  hot. The residual is bit-identical whether or not the restart deck<\/div>\n
  contains *INITIAL_TEMPERATURE_SET, so the initial-temperature card is not<\/div>\n
  the cause – the thermal state after the restore appears inconsistent\/<\/div>\n
  corrupted regardless of the deck.<\/div>\n
 <\/div>\n
FAILURE 2 – access violation in the 2D ALE non-reflecting boundary:<\/div>\n
  When the NONREFL *BOUNDARY_SALE_MESH_FACE card is active, the run instead<\/div>\n
  crashes at the first mechanical cycle with<\/div>\n
    forrtl: severe (157): Program Exception – access violation<\/div>\n
    NRBCALE2D (dyn60.F, line 36922) <- APPLY_LOADS <- FEM3D <- SOLTN<\/div>\n
  With the NONREFL card commented out, this crash disappears (the run then<\/div>\n
  reaches Failure 1 instead). The identical NONREFL setup runs without any<\/div>\n
  problem in the initial (non-restart) run.<\/div>\n
 <\/div>\n
QUESTIONS<\/div>\n
1. On a full-deck restart with *STRESS_INITIALIZATION + n=d3full01, is the<\/div>\n
   nodal temperature field (and phase-change history) of a coupled<\/div>\n
   structural\/thermal S-ALE model supposed to be restored from the dump?<\/div>\n
   Any known limitations for MAT_THERMAL_ISOTROPIC_PHASE_CHANGE on restart?<\/div>\n
2. Is the NRBCALE2D access violation on the restart path a known issue for<\/div>\n
   2D S-ALE non-reflecting boundaries? (I noticed the R14.1.0 release note<\/div>\n
   about an incorrect shear modulus in 2D S-ALE non-reflecting boundary<\/div>\n
   elements, and the R14.0.0 fix to *BOUNDARY_NON_REFLECTING_2D for<\/div>\n
   discontinuous boundary lines.)<\/div>\n
3. Is there a documented workaround other than abandoning the restart and<\/div>\n
   running both impacts as one continuous simulation (which is my current<\/div>\n
   fallback)?<\/div>\n
 <\/div>\n
For context: under R16.1.1 the same model family crashes at cycle 0 with an<\/div>\n
access violation inside *MAT_THERMAL_ISOTROPIC_PHASE_CHANGE (already<\/div>\n
reported separately), which is why this chain was migrated to R14.1.1.<\/div>\n
 <\/div>\n
I can provide the keyword decks, d3hsp\/mes files, and (if useful) the<\/div>\n
d3full01 family as a reproducer.<\/div>\n
 <\/div>\n
Thanks in advance,<\/div>\n
Amrith<\/div>\n

 <\/p>\n","protected":false},"template":"","class_list":["post-463246","topic","type-topic","status-publish","hentry","topic-tag-lsdyna","topic-tag-restart-analysis-1"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t