View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001174OpenFOAMBugpublic2014-02-21 01:192014-02-26 13:48
Reporteruser664Assigned Touser2 
PriorityhighSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
PlatformLinuxOSUbuntuOS Version12.04
Summary0001174: lowWeightCorrection for AMI patches crashes simulations with turbulence modeling
DescriptionUsing the lowWeightCorrection keyword for both AMI patches combined with a turbulence model (kOmegaSST in this case) gives the following error:

---------------------------------------------------------------------------------
--> FOAM FATAL ERROR:
Employing default values when sum of weights falls below 0.2 but supplied default field size is not equal to target patch size
    default values = 0
    source patch = 54328
---------------------------------------------------------------------------------

By switching to "simulationType laminar;" the error does not occur and the simulation runs.
Additional InformationTested on sHM grids generated with both 2.2.x and 2.3.x; same behavior in both cases.
TagsNo tags attached.

Activities

user664

2014-02-21 01:52

  ~0002878

This error seems to be tied into the kOmegaSST model. I tried both kOmega and kEpsilon and both of those work without producing the error above.

user857

2014-02-21 02:53

  ~0002879

I can confirm this error. Running my simulation with potentialFoam works. Running simpleFoam with the laminar model works. Running simpleFoam with the kOmega turbulence model works. However, running with the kOmegaSST model will produce this same error.

user2

2014-02-21 08:57

  ~0002881

Can you provide a small test case which demonstrates the problem?

user664

2014-02-21 13:40

  ~0002884

Andy, here is the 2.3.x propeller tutorial case switched to kOmegaSST:

https://www.dropbox.com/s/qng4k4264spjqln/propAMI_kOmegaSST.tgz

I added 0/omega and changed RANSProperties.

user2

2014-02-21 14:29

  ~0002886

Thanks for the case - I can see the problem and will work on a fix.

user857

2014-02-21 16:16

  ~0002887

I've also noticed this bug occurs while post-processing with yPlusRAS after running with the kOmega model.

user2

2014-02-26 13:48

  ~0002906

Thanks for the report - resolved by commit 8fa487c

Issue History

Date Modified Username Field Change
2014-02-21 01:19 user664 New Issue
2014-02-21 01:52 user664 Note Added: 0002878
2014-02-21 02:53 user857 Note Added: 0002879
2014-02-21 08:57 user2 Note Added: 0002881
2014-02-21 13:40 user664 Note Added: 0002884
2014-02-21 14:29 user2 Note Added: 0002886
2014-02-21 16:16 user857 Note Added: 0002887
2014-02-26 13:48 user2 Note Added: 0002906
2014-02-26 13:48 user2 Status new => resolved
2014-02-26 13:48 user2 Fixed in Version => 2.3.x
2014-02-26 13:48 user2 Resolution open => fixed
2014-02-26 13:48 user2 Assigned To => user2