OF 1.6-ext setFields does not keep patch values

Arnoldinho · June 24, 2011, 10:42

I'm nut sure if this is a bug or a normal procedure: Using setFields with OF 1.6-ext doesn't keep the original defined values at the boundary patches. This is not the case in 1.7.x, which I have used before.

An example: In U.org I set fixedValue uniform (0 0 0) for patch walls. The internal fields of part of the mesh are then set to (0.15 0 0) using setFields (regions, boxToCell). In the updated U file, values for patch walls are then also set to (0.15 0 0), which is wrong, as it serves as a boundary condition for the whole simulation.

Is there something like keetPatches in funkySetFields?

Arne

jdiorio · May 2, 2012, 13:06

Same issue - any resolution on this?

Arnoldinho · May 8, 2012, 07:28

Sorry no, at least not from my side.
I'm avoiding this by first setting the specific patch values to zeroGradient, and after setFields, giving back fixedValues. But this is just an ugly workaround.

cosimobianchini · May 9, 2012, 03:58

Here is another "ugly" workaround: simply avoid the loop on the faces.
I wrote an utility called setFieldsPreservePatch baset on setFields from 1.6-ext where I just removed lines from 86 to 91.
You find it in the attachement, please let me know if you encounter any problem.

June 24, 2011, 10:42	OF 1.6-ext setFields does not keep patch values	#1
Arnoldinho Senior Member Arne Stahlmann Join Date: Nov 2009 Location: Hanover, Germany Posts: 209 Rep Power: 17	I'm nut sure if this is a bug or a normal procedure: Using setFields with OF 1.6-ext doesn't keep the original defined values at the boundary patches. This is not the case in 1.7.x, which I have used before. An example: In U.org I set fixedValue uniform (0 0 0) for patch walls. The internal fields of part of the mesh are then set to (0.15 0 0) using setFields (regions, boxToCell). In the updated U file, values for patch walls are then also set to (0.15 0 0), which is wrong, as it serves as a boundary condition for the whole simulation. Is there something like keetPatches in funkySetFields? Arne Last edited by Arnoldinho; June 25, 2011 at 04:51.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Commercial meshers] Using starToFoam	clo	OpenFOAM Meshing & Mesh Conversion	33	September 26, 2012 04:04
[Other] StarToFoam error	Kart	OpenFOAM Meshing & Mesh Conversion	1	February 4, 2010 04:38
CheckMeshbs errors	ivanyao	OpenFOAM Running, Solving & CFD	2	March 11, 2009 02:34
[Gmsh] Import gmsh msh to Foam	adorean	OpenFOAM Meshing & Mesh Conversion	24	April 27, 2005 08:19
Multicomponent fluid	Andrea	CFX	2	October 11, 2004 05:12

May 2, 2012, 13:06		#2
jdiorio New Member Join Date: Jan 2010 Posts: 23 Rep Power: 16	Same issue - any resolution on this?

May 8, 2012, 07:28		#3
Arnoldinho Senior Member Arne Stahlmann Join Date: Nov 2009 Location: Hanover, Germany Posts: 209 Rep Power: 17	Sorry no, at least not from my side. I'm avoiding this by first setting the specific patch values to zeroGradient, and after setFields, giving back fixedValues. But this is just an ugly workaround.