mpirun error on CFDEM coupling cfdemSolverPisoScalar

Submitted by rahulsoni on Tue, 07/20/2021 - 15:23

Hello, I have modified the packedBedTemp case of the cfdemSolverPisoScalar solver. In the modified case particles are pre-fed (in.liggghts_init) on one side of a cylindrical furnace rotating on horizontal axis. The inlet, outlet face, wall and interior of the cylinder have predefined temperatures (as set in CFD and DEM files). The target of the simulation is to obtain the temperature profile of the particles. A typical simulation animation (change extension to .avi) is shown in the attachment. The in.liggghts_init, in.liggghts_run scripts and complete case folder are also attached for the reference.

When I run the simulation, every-time I get the following error at Time = 0.19 sec.
Can someone please tell me what is causing the issue.


Coupling...
Starting up LIGGGHTS
Executing command: 'run 1000 pre no post no'
run 1000 pre no post no
Step Atoms mass_tot KinEng rke heattran Volume
367001 41736 0.046907537 0.0023892784 0.00065939169 24717.801 5308.9139
CFD Coupling established at step 367100
CFD Coupling established at step 367200
CFD Coupling established at step 367300
CFD Coupling established at step 367400
CFD Coupling established at step 367500
CFD Coupling established at step 367600
CFD Coupling established at step 367700
CFD Coupling established at step 367800
CFD Coupling established at step 367900
CFD Coupling established at step 368000
368000 41736 0.046907537 0.0024379209 0.00066690319 24720.181 5387.2632
368001 41736 0.046907537 0.0024379615 0.00066690608 24720.183 5387.2632
Loop time of 203.242 on 32 procs for 1000 steps with 41736 atoms
Max time of 203.243 on 32 procs for 1000 steps with 41736 atoms
LIGGGHTS finished


timeStepFraction() = 1
update Ksl.internalField()
TotalForceExp: (0 0 0)
TotalForceImp: (0.332108 0.118807 -0.0586181)
total convective particle-fluid heat flux [W] (Eulerian) = -240.547
DILUPBiCG: Solving for T, Initial residual = 0.00187881, Final residual = 7.44572e-07, No Iterations 2
DILUPBiCG: Solving for Ux, Initial residual = 0.000653354, Final residual = 1.92097e-06, No Iterations 2
DILUPBiCG: Solving for Uy, Initial residual = 0.0235748, Final residual = 1.63724e-07, No Iterations 5
DILUPBiCG: Solving for Uz, Initial residual = 0.000627134, Final residual = 1.25039e-06, No Iterations 2
suppressing ddt(voidfraction)
DICPCG: Solving for p, Initial residual = 0.0168534, Final residual = 0.00162401, No Iterations 157
time step continuity errors : sum local = 8.35887e-06, global = -1.14775e-07, cumulative = 5.44252e-05
suppressing ddt(voidfraction)
DICPCG: Solving for p, Initial residual = 0.00731656, Final residual = 0.000693868, No Iterations 156
time step continuity errors : sum local = 5.57225e-06, global = -1.10138e-07, cumulative = 5.4315e-05
suppressing ddt(voidfraction)
DICPCG: Solving for p, Initial residual = 0.00204617, Final residual = 0.000183773, No Iterations 48
time step continuity errors : sum local = 4.05648e-06, global = -1.60139e-07, cumulative = 5.41549e-05
suppressing ddt(voidfraction)
DICPCG: Solving for p, Initial residual = 0.000573938, Final residual = 8.89116e-07, No Iterations 183
time step continuity errors : sum local = 3.51541e-06, global = -4.30493e-08, cumulative = 5.41119e-05
ExecutionTime = 19209.6 s ClockTime = 19291 s


Time = 1.19


Courant Number mean: 0.135687 max: 0.500766


Coupling...
Starting up LIGGGHTS
Executing command: 'run 1000 pre no post no'
run 1000 pre no post no
Step Atoms mass_tot KinEng rke heattran Volume
368001 41736 0.046907537 0.0024379615 0.00066690608 24720.183 5387.2632
--------------------------------------------------------------------------
Primary job terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
mpirun noticed that process rank 16 with PID 146133 on node immthpccn4 exited on signal 9 (Killed).
--------------------------------------------------------------------------

rahulsoni | Fri, 07/23/2021 - 06:18

Somehow I tried with different settings and at the end the solution continued when I changed the writeInterval settings from 0.1 to 0.01 in CFD/system/controlDict. It is surprising to see how this setting changed the whole scenario. I believed that writeInterval setting just manages the CFD output frequency. May be CFD itself reads the contents of previously wrote time folders and then proceeds.

--
Regards

Rahul Kumar Soni
Scientist, CSIR - IMMT, India