[DineshMyilsamy]

Hi everyone,
I am performing an underventilated compartment fire simulation using fireFoam based on the tutorial "compartmentFire" in OpenFOAM v1812.
The difference between tutorial and my case are compartment geometry size, fuel and fuel mass flow rate.

I used propane fuel for my case and the mass flow rate was according to the experiment.

When I performed the simulation with propane fuel according to my mass flow rate condition my simulation was ended in print stack error. For your detailed information, I have added the error message at the bottom of this message.

When I checked the log file ambient temperature was decreased to 50 K from 292.15 K.

Then I tried to simulate my case according to tutorial mass flow rate for propane fuel. When I performed the simulation for the tutorial mass flow rate condition the simulation was completed successfully without any error.

Actually in tutorial maximum mass flow rate is 0.00015 kg/s and In my case, the maximum mass flow rate is 0.006 kg/s


I request you, people, to help me to sort out this problem and I would like to know why minimum temperature decreased to 50K from 292.15 K and why I get this print stack error when I use my mass flow rate condition.

=======================================
Error Message that I got
======================================

[0] #0 Foam::error:rintStack(Foam::Ostream&) at ??:?
[0] #1 Foam::sigFpe::sigHandler(int) at ??:?
[0] #2 ? in /lib64/libc.so.6
[0] #3 Foam::hePsiThermo<Foam:siReactionThermo, Foam::SpecieMixture<Foam::singleStepReactingMixtur e<Foam::sutherlandTransport<Foam::species::thermo< Foam::janafThermo<Foam:erfectGas<Foam::specie> >, Foam::sensibleEnthalpy> > > > >::calculate(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh>&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh>&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh>&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh>&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh>&, bool) at ??:?
[0] #4 Foam::hePsiThermo<Foam:siReactionThermo, Foam::SpecieMixture<Foam::singleStepReactingMixtur e<Foam::sutherlandTransport<Foam::species::thermo< Foam::janafThermo<Foam:erfectGas<Foam::specie> >, Foam::sensibleEnthalpy> > > > >::correct() at ??:?
[0] #5 ? at ??:?
[0] #6 __libc_start_main in /lib64/libc.so.6
[0] #7 ? at ??:?
[gnode1:175238] *** Process received signal ***
[gnode1:175238] Signal: Floating point exception (8)
[gnode1:175238] Signal code: (-6)
[gnode1:175238] Failing at address: 0x3e90002ac86
[gnode1:175238] [ 0] /lib64/libc.so.6(+0x35670)[0x2ad06d518670]
[gnode1:175238] [ 1] /lib64/libc.so.6(gsignal+0x37)[0x2ad06d5185f7]
[gnode1:175238] [ 2] /lib64/libc.so.6(+0x35670)[0x2ad06d518670]
[gnode1:175238] [ 3] /opt/OpenFOAM/OpenFOAM-v1812/platforms/linux64GccDPInt32Opt/lib/libreactionThermophysicalModels.so(_ZN4Foam11hePsi ThermoINS_17psiReactionThermoENS_13SpecieMixtureIN S_25singleStepReactingMixtureINS_19sutherlandTrans portINS_7species6thermoINS_11janafThermoINS_10perf ectGasINS_6specieEEEEENS_16sensibleEnthalpyEEEEEEE EEE9calculateERKNS_14GeometricFieldIdNS_12fvPatchF ieldENS_7volMeshEEERSL_SO_SO_SO_SO_b+0x7ce)[0x2ad0686fe27e]
[gnode1:175238] [ 4] /opt/OpenFOAM/OpenFOAM-v1812/platforms/linux64GccDPInt32Opt/lib/libreactionThermophysicalModels.so(_ZN4Foam11hePsi ThermoINS_17psiReactionThermoENS_13SpecieMixtureIN S_25singleStepReactingMixtureINS_19sutherlandTrans portINS_7species6thermoINS_11janafThermoINS_10perf ectGasINS_6specieEEEEENS_16sensibleEnthalpyEEEEEEE EEE7correctEv+0x59)[0x2ad0686fe5f9]
[gnode1:175238] [ 5] fireFoam[0x43a53b]
[gnode1:175238] [ 6] /lib64/libc.so.6(__libc_start_main+0xf5)[0x2ad06d504b15]
[gnode1:175238] [ 7] fireFoam[0x43e5e5]
[gnode1:175238] *** End of error message ***
--------------------------------------------------------------------------
Primary job terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
An MPI communication peer process has unexpectedly disconnected. This
usually indicates a failure in the peer process (e.g., a crash or
otherwise exiting without calling MPI_FINALIZE first).

Although this local MPI process will likely now behave unpredictably
(it may even hang or crash), the root cause of this problem is the
failure of the peer -- that is what you need to investigate. For
example, there may be a core file that you can examine. More
generally: such peer hangups are frequently caused by application bugs
or other external events.

Local host: gnode3
Local PID: 105619
Peer host: gnode1
--------------------------------------------------------------------------
--------------------------------------------------------------------------
mpirun noticed that process rank 0 with PID 0 on node gnode1 exited on signal 8 (Floating point exception).
--------------------------------------------------------------------------
[gnode1:175230] 1 more process has sent help message help-mpi-btl-tcp.txt / peer hung up
[gnode1:175230] Set MCA parameter "orte_base_help_aggregate" to 0 to see all help / error messages
/home/users/dinesh/.profile: line 2: /opt/intel/impi/4.1.1.036/mic/bin/mpivars.sh: No such file or directory
-----------------------------------------------------------------------------
It seems that there is no lamd running on the host gnode1.

This indicates that the LAM/MPI runtime environment is not operating.
The LAM/MPI runtime environment is necessary for the "mpirun" command.

Please run the "lamboot" command the start the LAM/MPI runtime
environment. See the LAM/MPI documentation for how to invoke
"lamboot" across multiple machines.
-----------------------------------------------------------------------------