|
[Sponsors] |
Error while solving turbulent combustion using rhoreactingfoam |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
January 23, 2019, 08:58 |
Error while solving turbulent combustion using rhoreactingfoam
|
#1 |
New Member
Nikhil Bollimuntha
Join Date: Oct 2018
Posts: 11
Rep Power: 8 |
Hello,
I have been receiving this error while trying to execute the case file for turbulent combustion using the rhoReactingFoam solver. Screenshot 2019-01-11 at 9.27.08 PM.jpg Here's the link to the case file: https://drive.google.com/open?id=1gs...rXX_wkV1GdbGlu |
|
January 23, 2019, 17:10 |
|
#2 |
Senior Member
Join Date: Aug 2015
Posts: 494
Rep Power: 15 |
The output shows you have a problem computing nut (at the boundaries -- line that starts with "#3"). Check your nut boundary conditions.
Caelan |
|
January 24, 2019, 08:35 |
|
#3 |
New Member
Nikhil Bollimuntha
Join Date: Oct 2018
Posts: 11
Rep Power: 8 |
Sir, were you able to have a look at the case files? Because, to the best of my knowledge the boundary conditions I have set are correct.
|
|
January 24, 2019, 15:28 |
|
#4 |
Senior Member
Join Date: Aug 2015
Posts: 494
Rep Power: 15 |
I tried to suggest an answer before downloading someone else's case. How about posting your nut text here? Have you compared it to other tutorials that use rans?
Caelan |
|
January 25, 2019, 10:12 |
|
#5 |
New Member
Nikhil Bollimuntha
Join Date: Oct 2018
Posts: 11
Rep Power: 8 |
Here is the nut file sir:
/*--------------------------------*- C++ -*----------------------------------*\ ========= | \\ / F ield | OpenFOAM: The Open Source CFD Toolbox \\ / O peration | Website: https://openfoam.org \\ / A nd | Version: 6 \\/ M anipulation | \*---------------------------------------------------------------------------*/ FoamFile { version 2.0; format ascii; class volScalarField; location "0"; object nut; } // * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * // dimensions [0 2 -1 0 0 0 0]; internalField uniform 0; boundaryField { fuel-inlet { type calculated; value uniform 0; } air-inlet { type calculated; value uniform 0; } outlet { type calculated; value uniform 0; } upperwall { type calculated; value uniform 0; } lowerwall { type fixedValue; value uniform 0; } frontandback { type empty; } } And to answer your second question, yes sir, I have compared it and to most extent used values from the tutorial cases. |
|
January 25, 2019, 13:31 |
|
#6 |
Senior Member
Join Date: Aug 2015
Posts: 494
Rep Power: 15 |
The error you posted indicated it was a problem with a wall function calculation. However, you are not using wall functions. Did you change it, or are you using wall functions elsewhere?
Caelan |
|
January 25, 2019, 23:27 |
|
#7 |
New Member
Nikhil Bollimuntha
Join Date: Oct 2018
Posts: 11
Rep Power: 8 |
I have used the qRWallFunctionk in the k file and epsilonWallFunction in the epsilon file.
|
|
January 26, 2019, 00:07 |
|
#8 |
Senior Member
Join Date: Aug 2015
Posts: 494
Rep Power: 15 |
Not totally sure, but I'd hazard a guess that using those wall functions necessitates using a wall function for nut as well.
Caelan |
|
January 26, 2019, 06:18 |
|
#9 |
New Member
Nikhil Bollimuntha
Join Date: Oct 2018
Posts: 11
Rep Power: 8 |
Just executed the same case by adding wall function to the nut file as well, same error.
|
|
January 26, 2019, 19:46 |
|
#10 |
Senior Member
Join Date: Aug 2015
Posts: 494
Rep Power: 15 |
Ok so we've erased one possibility. Given that the simulation immediately crashes, this suspects your initial conditions. Have you tried other values for k and epsilon? Where did you get your current ones?
Caelan |
|
January 26, 2019, 22:25 |
|
#11 |
New Member
Nikhil Bollimuntha
Join Date: Oct 2018
Posts: 11
Rep Power: 8 |
So since you suggested the problem might be with the initial conditions and given that the error indicates that it is with the wall functions, I substituted the wall functions with constant values and now I'm getting another kind of error (attached below)
|
|
January 26, 2019, 22:36 |
|
#12 |
Senior Member
Join Date: Aug 2015
Posts: 494
Rep Power: 15 |
It's still a segfault -- looks like a division error. This is often due to division by zero. You can try initializing turbulent fields as very small (but not zero) numbers. Have you looked at the RANS reactingFoam tutorials (https://github.com/OpenFOAM/OpenFOAM...AS/SandiaD_LTS)? For future reference, it's easier to view the code/error if you attach it with the code tags.
Caelan |
|
January 26, 2019, 22:38 |
|
#13 |
New Member
Nikhil Bollimuntha
Join Date: Oct 2018
Posts: 11
Rep Power: 8 |
I'll look into it, and I don't have a RANS reactingFoam tutorial in my tutorials directory, could you please specify which one?
|
|
January 26, 2019, 23:12 |
|
#14 |
Senior Member
Join Date: Aug 2015
Posts: 494
Rep Power: 15 |
The link I included is the tutorial. It must have been added for recent OpenFOAM versions.
Caelan |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
problem with Min/max rho | tH3f0rC3 | OpenFOAM | 8 | July 31, 2019 10:48 |
Segmentation fault when using reactingFOAM for Fluids | Tommy Floessner | OpenFOAM Running, Solving & CFD | 4 | April 22, 2018 13:30 |
HeatSource BC to the whole region in chtMultiRegionHeater | xsa | OpenFOAM Running, Solving & CFD | 3 | November 7, 2016 06:07 |
calculation stops after few time steps | sivakumar | OpenFOAM Running, Solving & CFD | 7 | March 17, 2013 07:37 |
IcoFoam parallel woes | msrinath80 | OpenFOAM Running, Solving & CFD | 9 | July 22, 2007 03:58 |