View Issue Details

IDProjectCategoryView StatusLast Update
0002379OpenFOAMBugpublic2016-12-12 07:57
Reporterhesamft Assigned Tohenry  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
PlatformGNU/LinuxOSUbuntuOS Version14.04
Summary0002379: reactingFoam produce WRONG results in OF4.1 compare to OF2.4
DescriptionHi,

I had a case which I run with reactingFoam in OF2.4. I run the same case in OF4.1. The only differences are:
in fvScheme I added the following line:
    div(((rho*nuEff)*dev2(T(grad(U))))) Gauss linear;
in constant/thermophysicalProperties I added:
CHEMKINTransportFile "$FOAM_CASE/chemkin/transportProperties";
and the transportProperties files from the tutorial was also added to chemking folder.
Before I started the reaction, I wanted to reach steady state in nonreacting condition. The results of OF4.1 are very different from OF2.4 and clearly wrong. As I used exactly the same case, I assume that should be a bug. I looked at the following report:
http://bugs.openfoam.org/view.php?id=2172
which is reporting the same problem between OF3 and OF4. The solution was to exclude the relation factor.
relaxationFactors
{
    fields
    {
        //p 0.3;
        //pFinal 1;
      Yi 0.2;
      YiFinal 1;
    }
}
Since I don't use any relaxation factors, I don't think that's an issue here. Any ideas?

Thanks,
Hesam
Steps To ReproduceI attached a case which works on both OFs. Just run reactingFoam
Additional InformationThere are some pictures comparing the final results from both OFs
TagsNo tags attached.

Activities

hesamft

2016-12-08 13:09

reporter  

bugReport.tar.gz (3,492,166 bytes)

hesamft

2016-12-11 21:43

reporter   ~0007455

Hi,

I think I found the source of the error and it is not a bug! It's coming from the new transport properties dictionary that should be added to the chemkin folder. I copied the file from tutorial chemFoam. Since there is no transport in chemFoam, the transport dictionary assigned zero to all the constants. By correcting the constants, the results will be fixed. I'm running the case again and it seems it's giving the same results as OF2.4.

/Hesam

Issue History

Date Modified Username Field Change
2016-12-08 13:09 hesamft New Issue
2016-12-08 13:09 hesamft File Added: bugReport.tar.gz
2016-12-11 21:43 hesamft Note Added: 0007455
2016-12-12 07:57 henry Assigned To => henry
2016-12-12 07:57 henry Status new => closed
2016-12-12 07:57 henry Resolution open => no change required