CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > SU2

Interface boundary condition

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

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   September 21, 2017, 01:11
Default Interface boundary condition
  #1
New Member
 
Yeongmin Jo
Join Date: Dec 2013
Posts: 10
Rep Power: 12
Yminjo is on a distinguished road
Hi, all.

As I know, the interface boundary condition in SU2 is just for postpocessing, and it does not affect any solution.
In my case, the solution diverges when I used the B.C..
Does anyone have the same problem with me?

Thank you.
Yminjo is offline   Reply With Quote

Old   September 25, 2017, 10:09
Default
  #2
Super Moderator
 
Tim Albring
Join Date: Sep 2015
Posts: 195
Rep Power: 10
talbring is on a distinguished road
Hi Yeongmin,

you are right, the interface should not affect the solution. First of all make sure that you provide only one side of the interface in your mesh file, the other side is automatically constructed.

If that does not solve your problem, provide me the mesh file and config so that I can have a look at the problem.

Tim
talbring is offline   Reply With Quote

Old   September 25, 2017, 13:00
Default
  #3
New Member
 
Yeongmin Jo
Join Date: Dec 2013
Posts: 10
Rep Power: 12
Yminjo is on a distinguished road
Quote:
Originally Posted by talbring View Post
Hi Yeongmin,

you are right, the interface should not affect the solution. First of all make sure that you provide only one side of the interface in your mesh file, the other side is automatically constructed.

If that does not solve your problem, provide me the mesh file and config so that I can have a look at the problem.

Tim

Dear Albring

Thank you for your reply so much.
I attached my mesh and configure files in the following URL because of its large size:

https://drive.google.com/file/d/0BxY...I2VWlLZE0/view

The zip file includes three mesh files with and without interface markers.

1. 2C_no_interface.su2 does not have any interface marker.
2. 2C_with_inter1_inter2.su2 has a pair of interface markers of inward 'inter1' and outward 'inter2'.
3. 2C_with_inter2_only.su2 has only the outward 'inter2' marker.
4. comp.cfg is the cofig file.

Also, the definition of markers is shown in the attached figure 'Markers.jpg'.

The mesh has very small domain size for testing the interface feature, but the computation converges well using '2C_no_interface.su2' file.
Because the three mesh files are exactly same excluding the marker definition, the computation using '2C_with_inter2_only.su2' must converge too,
However the computation diverges.

Could you please tell me what the current problem is?

Thank you for your effort in advance.

Sincerely,

Yeongmin
Attached Images
File Type: jpg Markers.jpg (105.8 KB, 32 views)
Yminjo is offline   Reply With Quote

Old   September 26, 2017, 06:01
Default
  #4
Super Moderator
 
Tim Albring
Join Date: Sep 2015
Posts: 195
Rep Power: 10
talbring is on a distinguished road
Hi Yeongmin,

I think the problem is that the interface shares a point with the wall (airfoil). Can you try to increase the distance a little bit and try it again ?
__________________
Developer Director @ SU2 Foundation

Get involved:
talbring is offline   Reply With Quote

Old   September 26, 2017, 06:25
Default
  #5
New Member
 
Yeongmin Jo
Join Date: Dec 2013
Posts: 10
Rep Power: 12
Yminjo is on a distinguished road
Quote:
Originally Posted by talbring View Post
Hi Yeongmin,

I think the problem is that the interface shares a point with the wall (airfoil). Can you try to increase the distance a little bit and try it again ?

Dear Albring

Thank you for your reply.
Actually, I think I found what the problem is.
The problem was not in SU2, but in the connectivity written in the mesh file.
For the interface boundary condition, I made the inner 'inter1' and outer 'inter2' boundaries using connectors in Pointwise.
I attached a figure to explain that situation: green connector for 'inter1' and blue connector for 'inter2'.
In my experience, I have to select a pair of inner and outer connectors in Pointwise whichever they are assigned as boundary conditions together or separately.

Anyway, I think that the way generates wrong connectivity information.
After generating a mesh file without the interface boundary in Pointwise, I made a new marker with connectivity manually in the mesh file.
Then, the solution converges well, and the interface feature works well.

Now, I'm trying to find a way to avoid the problem in Pointwise.
If you don't mind, could you please tell me your way to make the interface marker?

Thank you, again.

Sincerely,

Yeongmin
Attached Images
File Type: jpg aa.jpg (90.5 KB, 24 views)
Yminjo is offline   Reply With Quote

Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
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 Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
My radial inflow turbine Abo Anas CFX 27 May 11, 2018 02:44
Error - Solar absorber - Solar Thermal Radiation MichaelK CFX 12 September 1, 2016 06:15
Question about heat transfer coefficient setting for CFX Anna Tian CFX 1 June 16, 2013 07:28
Low Mixing time Problem Mavier CFX 5 April 29, 2013 01:00
Problem with Interface Boundary Condition tos FLUENT 0 April 4, 2010 09:11


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