CFD Online Discussion Forums

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   CFX (https://www.cfd-online.com/Forums/cfx/)
-   -   Discontinuous contour at interface (https://www.cfd-online.com/Forums/cfx/145319-discontinuous-contour-interface.html)

swtbkim December 2, 2014 22:20

Discontinuous contour at interface
 
3 Attachment(s)
Hi all.

I attached my simulation results.
As you can see, there is some unreasonable contour at interface.

Does anyone know about this phenomenon?


I used meshing tool, Pointwise
and GGI interface.

Thank you in advance.

Opaque December 3, 2014 00:11

What kind of domain interface ? Frame change model used ?

Can you show mesh density on both sides of the interfaces ?

Are you plotting hybrid, or conservative values ?

swtbkim December 3, 2014 01:51

3 Attachment(s)
Quote:

Originally Posted by Opaque (Post 522202)
What kind of domain interface ? Frame change model used ?

Can you show mesh density on both sides of the interfaces ?

Are you plotting hybrid, or conservative values ?


Thank you for reply!


I don't use frozen rotor or something; so frame does not change.
I have to make subdomain for momentum source, that is the reason why I made multi block grid and interface is needed.

Hybrid is used.
Actually I don't know about this option.. hybrid vs. conservative
Hybrid is default, and I just used it.

I attached about mesh.

ghorrocks December 3, 2014 04:47

Which post processor did you draw this with?

JuPa December 3, 2014 05:10

Is the mesh adequate for your problem? I don't know the full details of your mesh, but it looks poorly formed.

swtbkim December 3, 2014 05:18

Quote:

Originally Posted by ghorrocks (Post 522245)
Which post processor did you draw this with?


All figures are drawn with CFD-POST.

swtbkim December 3, 2014 05:29

1 Attachment(s)
Quote:

Originally Posted by RicochetJ (Post 522253)
Is the mesh adequate for your problem? I don't know the full details of your mesh, but it looks poorly formed.


I agree with you..
This is one of several versions of mesh. Not well-made grid.

You mean, mesh quality is important in this case?
I thought that this is an issue about interpolation inside each grid cell, not mesh quality.


I attached view of mesh at large.
Flow is induced from left to right(i.e. from opening into pipe)
Opening is one block, and Inside the pipe is one block.
So the inlet of the pipe is specified as interface between two blocks.

And I made an inflation layer at that interface.
It's pretty weird treatment, but I thought it was not important.

diamondx December 3, 2014 10:29

mesh quality is poor, extend your prism to other boundary at lest. I personnaly don't like transitions from 10 layers to 0 layer

Thomas MADELEINE December 3, 2014 11:07

Just another question about the mesh...
Why did you use some inflation layout on the interface ?
In my point of view it is only usefull close to wall (with no slip option) to catch the layer (big gradient of the velocity in small area) so it should be on the walls but not on the interface.

There, the flow will have to pass through multiple cells from one domain to another.

However I am not sure of all of this but I have never saw this problem before using this method...

I hope this can help.
Regards,
Thomas MADELEINE

Opaque December 3, 2014 11:27

Could you share the same plot using Conservative values ?

You should probably have a look at the documentation about what Hybrid values are, and the known issues with them. Interpret what they are in the context of the mesh you have shown plus the fact that it may be coarse, mismatched and the fact that interpolation must be used to create the plot.

I did not understand the reasoning for creating an interface. Definitely, the fact that you need a subdomain to include sources is not enough reason to justify an interface. Subdomains do not have to cover all of the domain.

If your physics is the same everywhere (except for the source), and there is no frame change, they only reason left for an interface is that you meshed the volumes separately, the faces do not match at those common surfaces; therefore, you must manually stitch them.

ghorrocks December 3, 2014 16:49

Have you had a look at the non-overlap fraction? Does the velocity field look correct in the area? The GGI might not be joining these faces together properly and so these bits of the mesh might not be connected. This should be seen in the non-overlap fraction and a obvious kink in the velocity field.

swtbkim December 3, 2014 21:28

Quote:

Originally Posted by Thomas MADELEINE (Post 522334)
Just another question about the mesh...
Why did you use some inflation layout on the interface ?
In my point of view it is only usefull close to wall (with no slip option) to catch the layer (big gradient of the velocity in small area) so it should be on the walls but not on the interface.

There, the flow will have to pass through multiple cells from one domain to another.

However I am not sure of all of this but I have never saw this problem before using this method...

I hope this can help.
Regards,
Thomas MADELEINE



It was just my curiosity that there is also a big gradient of velocity at the inlet of pipe, so if there is an inflation, then it may increase the accuracy or not?

swtbkim December 3, 2014 21:29

Quote:

Originally Posted by diamondx (Post 522322)
mesh quality is poor, extend your prism to other boundary at lest. I personnaly don't like transitions from 10 layers to 0 layer

You mean, make inflation at all walls?

swtbkim December 3, 2014 21:40

3 Attachment(s)
Quote:

Originally Posted by Opaque (Post 522336)
Could you share the same plot using Conservative values ?

You should probably have a look at the documentation about what Hybrid values are, and the known issues with them. Interpret what they are in the context of the mesh you have shown plus the fact that it may be coarse, mismatched and the fact that interpolation must be used to create the plot.

I did not understand the reasoning for creating an interface. Definitely, the fact that you need a subdomain to include sources is not enough reason to justify an interface. Subdomains do not have to cover all of the domain.

If your physics is the same everywhere (except for the source), and there is no frame change, they only reason left for an interface is that you meshed the volumes separately, the faces do not match at those common surfaces; therefore, you must manually stitch them.



Thank you. I'm going to check the hybrid value issue.

Then, interfaces are always exactly matched to each other??
How can it be done automatically?


first image is conservative values
blue region became red(..)


second and third image are about another mesh. It is also not good, but not that much than previous mesh.
Grid cell is not matched, GGI interfaces are used, and discontinuous contour is made.
How can I fix this??
Should I make exactly matched surface mesh at interface?

swtbkim December 3, 2014 21:49

1 Attachment(s)
Quote:

Originally Posted by ghorrocks (Post 522364)
Have you had a look at the non-overlap fraction? Does the velocity field look correct in the area? The GGI might not be joining these faces together properly and so these bits of the mesh might not be connected. This should be seen in the non-overlap fraction and a obvious kink in the velocity field.


I don't know what is nonoverlap fraction. I'm going to study about it..
When I make contour of it, all I see is this image.
Blue one is edges of whole domain; opening boundary condition quite far from pipe.


Mean flow looks good and reasonable.

ghorrocks December 3, 2014 22:12

Nonoverlap fraction applies to interface boundaries and is the proportion of the element face which does not overlap with an element on the other side of the interface. If you see a high nonoverlap fraction in a region of GGI which should be part of the mesh connection then you have a problem with your GGI interface as it has not correctly identified faces on either side of the boundary to match up.

This can occur on GGI interfaces when you have either big changes in mesh size over the interface, or high aspect ratio elements at the interface. In both these cases the default GGI settings do occasionally miss elements on interfaces.

You have now shown that when you use a mesh with an aspect ratio closer to 1 the interface works properly. You have high aspect ratio elements on the interface you first posted as you put inflation mesh on the interface boundary faces so I suspect you are getting this non-overlap problem.

swtbkim December 4, 2014 00:53

Quote:

Originally Posted by ghorrocks (Post 522384)
Nonoverlap fraction applies to interface boundaries and is the proportion of the element face which does not overlap with an element on the other side of the interface. If you see a high nonoverlap fraction in a region of GGI which should be part of the mesh connection then you have a problem with your GGI interface as it has not correctly identified faces on either side of the boundary to match up.

This can occur on GGI interfaces when you have either big changes in mesh size over the interface, or high aspect ratio elements at the interface. In both these cases the default GGI settings do occasionally miss elements on interfaces.

You have now shown that when you use a mesh with an aspect ratio closer to 1 the interface works properly. You have high aspect ratio elements on the interface you first posted as you put inflation mesh on the interface boundary faces so I suspect you are getting this non-overlap problem.



Thank you for careful reply, Glenn.

Then, do you think that interface I secondary posted is good enough?
But there is a discontinuous region yet.
You just meant that this is not about non-overlap fraction issue, but another one?

ghorrocks December 4, 2014 03:53

You are never going to get a perfectly continuous contour at a GGI. The contour drawing gizmo inside CFD-Post only draws contours based on the values inside that domain, so it cannot do continuous contours across GGI interfaces as that spans multiple domains. The best you can do is get contours which are close. Your post #14 has contours which are close enough that I suspect the GGI is working correctly, but post #1 and #3 show contours which clearly are wrong and therefore are likely to have the non-overlap problem.

swtbkim December 4, 2014 04:40

Quote:

Originally Posted by ghorrocks (Post 522415)
You are never going to get a perfectly continuous contour at a GGI. The contour drawing gizmo inside CFD-Post only draws contours based on the values inside that domain, so it cannot do continuous contours across GGI interfaces as that spans multiple domains. The best you can do is get contours which are close. Your post #14 has contours which are close enough that I suspect the GGI is working correctly, but post #1 and #3 show contours which clearly are wrong and therefore are likely to have the non-overlap problem.


Then it is a limitation of CFD-POST and I should satisfy with it, and make finer grid if I want more smooth contour.



Thank you all very much

rolloblues December 4, 2014 06:41

Quote:

Originally Posted by swtbkim (Post 522428)
make finer grid if I want more smooth contour.

I will reiterate what other members correctly already pointed out:
I'm afraid that a finer mesh won't resolve your problems.
You should re-think your meshing approach without growing prisms from the interface.


All times are GMT -4. The time now is 02:46.