[immortality]

in groovyBC contrib there are some definitions that i have some questions about.
1)is internalField of a field the value of that fiels at neighbour of the patch of boundary condition?
2)how can use Cn tool?does for instance Cn(p) gives us the value at neighbor or it just shows the place of neighbor?
3)what does coupled patch mean?then whats neighbourField?

Cn 
neighbour cell centers of the patch
delta 
Return cell-centre to face-centre vector
weights 
Return patch weighting factors
3.5 Functions that need another field are:
snGrad 
Gradient of that field
internalField 
internal values of that field
neighbourField 
neighbour values for a coupled patch

[immortality]

no answers yet?

[immortality]

nobody can explain a bit about those?

[immortality]

Mr.Gschaider could you guide me about post 1?

[gschaider]

Originally Posted by immortality

Mr.Gschaider could you guide me about post 1?

To explain that more thoroughly than it already is explained would take me more time than I currently have

[immortality]

all answers on it whenever is appreciated(sooner is better).

[immortality]

one who asks a question is a fool for five minutes,one who does not ask a question remains a fool forever
Chinese proverb

[wyldckat]

Hi Ehsan,

Quoting from wikipedia, on a topic from a favourite book of mine: http://en.wikipedia.org/wiki/Answer_...thing_.2842.29

[...] a group of hyper-intelligent pan-dimensional beings demand to learn the Answer to the Ultimate Question of Life, The Universe, and Everything from the supercomputer, Deep Thought, specially built for this purpose. It takes Deep Thought 7½ million years to compute and check the answer, which turns out to be 42. The Ultimate Question itself is unknown.

Basically, even if one asks a question, the quality of the answer will depend on the quality of the question.

And when it comes to Computational Fluid Dynamics it becomes even more true and complex, because simply asking what is "x" in "A*x=B", usually is not enough


OK, but mathematical existentialism aside, your questions on this thread will require you to help us help you. In essence, please prepare and share one or more simple test cases, where you and anyone else can help you figure out what each one of these functions/capabilities are.
The reason I ask you is rather simple: setting up cases usually takes longer than figuring out what each function really does!

So, I suggest you do the following steps:

1. Create a simple cube shaped test case. It can be the tutorial "incompressible/icoFoam/cavity", modified to work in 3D. It can still be prepared to work with icoFoam, which is a rather simple case and has a low count of cells. potentialFoam is another good candidate, because it's fast and extremely simple.
2. Create a few variants of this case:
   1. Remove the top moving wall patch. Add one outlet patch and an inlet patch. Doesn't matter much where the they are located, but keep in mind that opposite patches are good for some tests and perpendicular patches are good for other cases.
      Another detail is to keep all 6 sides of the cube assigned to a specific patch name, to make it easier to switch patches to walls and vice-versa.
   2. Based on 2.1, change the inlet patch for use groovyBC with a known expression that should work. Something like fixed value or height based. This will be used for figuring out each feature that groovyBC has got.
   3. Another one based on 2.1 or 2.2, but this time using the icoFoam with temperature, as described at http://openfoamwiki.net/index.php/Ho...ure_to_icoFoam . The reason here is because it will make it easier to use the T field as "the other field" or perhaps the T field to be based on p or U.
3. Share the cases here on this thread, in a state before generating the mesh. It's easy to clean up a tutorial, simply by running:
   

   foamCleanTutorials

Having access to these simple test cases will make it rather easy to then do some trial-and-error tests. It will also make it easy to know what the values stand for, because the cases are so simple that values can be calculated by hand.

Best regards,
Bruno