|
[Sponsors] |
Liquid Volume Error when VOF + Deforming Mesh Used |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
June 5, 2012, 11:14 |
Liquid Volume Error when VOF + Deforming Mesh Used
|
#1 |
Member
Nick Cleveland
Join Date: Mar 2012
Posts: 35
Rep Power: 14 |
I am writing to post a type of error I found with VOF and deforming moving mesh used in conjunction. What happens is that the mesh elements change volume with the moving mesh, but the VOF vol frac in each element stays the same, as if the mesh wasn't moving and the volume not decreasing overall. The result is that the liquid inside each cell gets "compressed" with the cell/element artificially, implying that the total mass of liquid in the domain is decreasing when it should stay completely constant.
Has anyone come across this error also in your work? I am now trying to find a way around it. possibly CFX doesn't have one and only FLUENT does? I'll post a video and picture also to clarify my explanation. Can't post a video though I'm posting just to say that if anyone has strange fluid loss errors when using moving mesh that this could be the cause. |
|
June 5, 2012, 20:43 |
|
#2 |
Super Moderator
Glenn Horrocks
Join Date: Mar 2009
Location: Sydney, Australia
Posts: 17,871
Rep Power: 144 |
Which version of CFX are you using?
Before anything else you should check whether you simply need tighter convergence or smaller time steps. Check whether you still get the effect with far tighter convergence and/or tighter convergence. Then test some other options, such as coupled versus segregated VF. The first implementation of the coupled VF solver had some conservation issues but I think it was resolved in later releases of CFX. |
|
June 6, 2012, 08:53 |
|
#3 | |
Member
Nick Cleveland
Join Date: Mar 2012
Posts: 35
Rep Power: 14 |
Quote:
I'm using the CFX 12.1 version that comes with ANSYS 12.1. Do you know by any chance if the convergence can be tightened by reducing the "residual target" value under "convergence criteria" in the solver controls? (I'll just try that to test for result). I already tested the effect of smaller timestep. The effect was negligible on this error. Also, I coincidentally already experimented with the coupled/segregated VOF multiphase settings to no avail. I'll try that convergence criteria tightening now. |
||
June 6, 2012, 09:01 |
|
#4 | |
Super Moderator
Glenn Horrocks
Join Date: Mar 2009
Location: Sydney, Australia
Posts: 17,871
Rep Power: 144 |
You should consider upgrading to the current version. I think they made some big improvements to the coupled VF solver in V13. I remember V12 had problems with VF conservation - which is exactly what you are seeing.
Quote:
And forget about reporting it as a bug if you are on V12. No point fixing a bug on an old version which is probably already fixed anyway. (Get my drift? Using old versions of the software means you may well be wasting your time on a problem which is already fixed.) |
||
June 6, 2012, 12:52 |
|
#5 |
Member
Nick Cleveland
Join Date: Mar 2012
Posts: 35
Rep Power: 14 |
Gaining experience by the minute. Thanks, I'll try 13
|
|
June 6, 2012, 19:56 |
|
#6 |
Super Moderator
Glenn Horrocks
Join Date: Mar 2009
Location: Sydney, Australia
Posts: 17,871
Rep Power: 144 |
Why not try V14?
|
|
June 7, 2012, 11:01 |
|
#7 |
Member
Nick Cleveland
Join Date: Mar 2012
Posts: 35
Rep Power: 14 |
Ok, got another amateur question: If I run a model in CFX solver 13 that I setup in CFX-pre 12.1, shouldn't that solution have the newer VF coupling corrrectness? I'm pretty sure it should, but I just did that (ran a 12.1 setup in 13 solver) and it had the same exact mass conservation issue, no improvement.
I ran it again with a much tighter conservation target and the same exact solution was produced. Even if I could get access to v14, not sure if it would be any better. Going to try Fluent v13 now. |
|
June 7, 2012, 19:53 |
|
#8 |
Super Moderator
Glenn Horrocks
Join Date: Mar 2009
Location: Sydney, Australia
Posts: 17,871
Rep Power: 144 |
It is starting to look like you have found a bug in VF conservation in moving meshes. But forget about doing anything about it unless you run in the current version, V14. If it also happens in V14 then I would report it as a bug and hopefully you can get it fixed.
|
|
June 8, 2012, 14:07 |
|
#9 |
Member
Nick Cleveland
Join Date: Mar 2012
Posts: 35
Rep Power: 14 |
Ok, got it. The ANSYS technical support said that the surface tension model causes problems at this small a scale (sub-micron). When I turned it off, there was less, but still some, mass loss.
|
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
how to set periodic boundary conditions | Ganesh | FLUENT | 15 | November 18, 2020 07:09 |
[ICEM] surface mesh merging problem | everest | ANSYS Meshing & Geometry | 44 | April 14, 2016 07:41 |
3D Hybrid Mesh Errors | DarrenC | ANSYS Meshing & Geometry | 11 | August 5, 2013 07:42 |
[blockMesh] BlockMesh FOAM warning | gaottino | OpenFOAM Meshing & Mesh Conversion | 7 | July 19, 2010 15:11 |
Convergence moving mesh | lr103476 | OpenFOAM Running, Solving & CFD | 30 | November 19, 2007 15:09 |