CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > STAR-CCM+

What to do about this warning?

Register Blogs Members List Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
Old   March 19, 2012, 17:29
Default What to do about this warning?
  #1
Member
 
Join Date: Dec 2011
Location: State College, PA
Posts: 87
Rep Power: 5
rks171 is on a distinguished road
During my simulation, after every iteration, I get this warning:

Code:
Temperature corrections limited in 175 cells in region Body 1
The number of cells changes each time. It goes up and down. One iteration it was as high as 1,500 cells. There was a jump up in the energy and z-momentum residuals that iteration. What exactly does this warning mean and do I need to worry about it or take action to fix the problem? I can't find info about it in the starccm+ manual or online.

FYI, I'm using a segregated flow and segregated energy solution.
rks171 is offline   Reply With Quote

Old   March 20, 2012, 09:55
Default
  #2
Super Moderator
 
Ryne Whitehill
Join Date: Aug 2009
Posts: 313
Rep Power: 10
rwryne is on a distinguished road
Quote:
Originally Posted by rks171 View Post
During my simulation, after every iteration, I get this warning:

Code:
Temperature corrections limited in 175 cells in region Body 1
The number of cells changes each time. It goes up and down. One iteration it was as high as 1,500 cells. There was a jump up in the energy and z-momentum residuals that iteration. What exactly does this warning mean and do I need to worry about it or take action to fix the problem? I can't find info about it in the starccm+ manual or online.

FYI, I'm using a segregated flow and segregated energy solution.
Typically this means you have some bad cells in your mesh. Create a cell set to visualize these:

Go to Representations->Volume Mesh->Right click on Cell Sets->New->Threshold->Set it to Temperature -> hit Query.

you are wanting to find if they are min temps or max temps. Depending on that, create a min or max threshold and type a number below the value. You can then highlight this cell set in a scene to visualize
rwryne is offline   Reply With Quote

Old   March 20, 2012, 10:38
Default
  #3
Member
 
Join Date: Dec 2011
Location: State College, PA
Posts: 87
Rep Power: 5
rks171 is on a distinguished road
I took your advice. It is a max temp problem. I have temperatures up to 1500 K. I set a threshold of 700 K. The problem cells are all in a part of the geometry where two surfaces get very close together and contact each other, causing a region that probably has very low flow. Here's a 3D representation of the problem region with the max temp cells shown in pink:



Here's the same shot from above the region with the mesh shown. Note that the solid curved surface running across the top of the picture is the heated surface. The other curved surface going across the bottom that meets up with the top surface is not heated.



Here's the same picture of the mesh with the max temp cells highlighted in pink:



Can you advise me what to do about this problem? If the solution is to make a new mesh, what should the mesh look like in those tight regions? What kind of settings do I need to use for the prism mesher or trim mesher to acheive a good mesh in those regions?

Last edited by rks171; March 20, 2012 at 11:10.
rks171 is offline   Reply With Quote

Old   March 20, 2012, 12:10
Default
  #4
Super Moderator
 
Ryne Whitehill
Join Date: Aug 2009
Posts: 313
Rep Power: 10
rwryne is on a distinguished road
Well, to get the prism layer to work better in there I would try:

1) try setting your near wall boundary layer a bit smaller (i.e. add more layers, or change stretching raito). The more layers it has, the easier it is for it to chop off. I.e. if you had a prism layer with 2 equally spaced, you have to chop off 50% at a time. If you had same thickness but with 10 layers, you can remove in 10% increments.

then
All under Continuum->Mesh->Models->Prism Layer Mesher
2) Set minimum thickness percentage to a really low value. 1% may be a good starting place, but you can go to .1 I believe.
3) Set layer reduction percentage to high value. 95% is agood starting place, but you can go up to 99%
rwryne is offline   Reply With Quote

Old   March 20, 2012, 12:31
Default
  #5
Member
 
Join Date: Dec 2011
Location: State College, PA
Posts: 87
Rep Power: 5
rks171 is on a distinguished road
So, you're saying that I want to get the prism layers thinner so that I can get them further into that crevice? My original thinking was that I should try and just get one big cell to take care of that whole crevice region because I didn't think it was that important what was going on in that one spot. Plus, I was worried about computational resources, which are already stretched thin. The case that I just showed you took 9 hours to run 130 iterations using 30 cores. Cases I ran using coarser meshes took 4000 iterations to converge. Granted, I initialized this refined mesh case to the solution of the coarse mesh case to try and speed up the solution, but the residuals, velocities, and temperatures are pretty much all over the place at 130 iterations so I'm assuming this is still going to take a lot more iterations, if it does converge at all.
rks171 is offline   Reply With Quote

Old   March 20, 2012, 12:38
Default
  #6
Super Moderator
 
Ryne Whitehill
Join Date: Aug 2009
Posts: 313
Rep Power: 10
rwryne is on a distinguished road
Quote:
Originally Posted by rks171 View Post
So, you're saying that I want to get the prism layers thinner so that I can get them further into that crevice? My original thinking was that I should try and just get one big cell to take care of that whole crevice region because I didn't think it was that important what was going on in that one spot. Plus, I was worried about computational resources, which are already stretched thin. The case that I just showed you took 9 hours to run 130 iterations using 30 cores. Cases I ran using coarser meshes took 4000 iterations to converge. Granted, I initialized this refined mesh case to the solution of the coarse mesh case to try and speed up the solution, but the residuals, velocities, and temperatures are pretty much all over the place at 130 iterations so I'm assuming this is still going to take a lot more iterations, if it does converge at all.

Well, I have had issues with poor solutions in geometry similar to this that were fixed by getting my prism into the crevice.

If you are wanting to avoid global prism changes, maybe try separating out the feature curve defining that gap and setting a smaller mesh size on it? This would create a finer mesh only in that region.

If you are trying to avoid increasing the mesh size at all, you might try modifying the gemoetry slightly to get rid of that gap. I.e. fill it across with a flat face. If there is little flow in the region, it shouldnt affect the solution too much.
rwryne is offline   Reply With Quote

Old   March 20, 2012, 12:43
Default
  #7
Member
 
Join Date: Dec 2011
Location: State College, PA
Posts: 87
Rep Power: 5
rks171 is on a distinguished road
I'm thinking about this problem a little more. You said the problem is either min or max temps, but I didn't get any warnings about the temperature being limited by the min or max limits like I did in previous runs. And, even though the max temp in my mesh was 1500 K, the max limit set under 'physics' is 5000 K. So it seems to me like the 'temperature correction' which is being limited is something different. I checked the coarse mesh case that I told you about and that only gave me seldom errors about the temperature correction being limited and only in one cell; however, that coarse mesh had the same problems with high fluid temperatures in those tight crevices as I saw in the refined mesh. And that still converged. Are these high temperatures in those spots a problem?

Either way, I think I'll give it a try to get the prism layer into the crevice to see if I still get the warnings or not. Thanks for your suggestions.
rks171 is offline   Reply With Quote

Old   March 21, 2012, 07:13
Default
  #8
Senior Member
 
Join Date: Oct 2009
Location: Germany
Posts: 637
Rep Power: 12
abdul099 is on a distinguished road
Cells having a sharp edge like yours are usually bad. It's better to cut the cells so the triangular cross sectional shape becomes a trapezoid.
abdul099 is offline   Reply With Quote

Old   March 21, 2012, 10:47
Default
  #9
Member
 
Join Date: Dec 2011
Location: State College, PA
Posts: 87
Rep Power: 5
rks171 is on a distinguished road
Unfortunately, I don't think I'll have the time to re-mesh and run again because if I'm going to get results from this case, I need to get them very soon, so I'll just see where this case goes. I will keep your tips in mind though for when I generate new meshes and keep an eye on the angles of those prism layers and cells in those tight crevices. To update, I have now run for about 320 iterations and the residuals are looking good. The velocities and temperatures seem to be settling down to more consistent values with respect to the iteration count. Also, I'm getting much less of these 'temperature correction limited' warnings. I'm getting warnings for about 50 cells every iteration as compared to 300-400 cells at the beginning of the simulation.
rks171 is offline   Reply With Quote

Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
BlockMesh FOAM warning gaottino OpenFOAM Native Meshers: blockMesh 7 July 19, 2010 14:11
latest OpenFOAM-1.6.x from git failed to compile phsieh2005 OpenFOAM Bugs 25 February 9, 2010 05:37
Compilation errors in ThirdPartymallochoard feng_w OpenFOAM Installation 1 January 25, 2009 07:59
Can anybody help me to solve the list errors while compiling Openfoam 15 on Opensuse 103 32bit coompressor OpenFOAM Installation 0 November 12, 2008 20:53
Axisymmetrical mesh Rasmus Gjesing (Gjesing) OpenFOAM Native Meshers: blockMesh 10 April 2, 2007 14:00


All times are GMT -4. The time now is 19:40.