[cpinz]

Hello everyone,

from tutorials and videos it'not clear to me how boundary conditions, in a Pointwise mesh file, are exported SU2. In particular the relation between b.c. in Pointwise and "markers" in SU2 *cfg.file.

Are the b.c. names defined in Pointwise to be the same of markers ? That is, "inlet" or "pressure outlet " or "wall" in Pointwise are automatically recognized by SU2 , once I have defined "Marker_INLET=inlet" , "Marker_WALL = wall" ans so on... ?

Thank you in advance
cpinz

[kmandar]

Hi,

the relation between b.c. in Pointwise and "markers" in SU2 *cfg.file.

All the information about mesh and markers is in the *.su2 mesh file. The marker tag in this file identifies the boundaries. After using Pointwise to generate the mesh, and outputting it in .su2 format, I would open that file in a text editor and make sure that the marker tags are for the boundaries as I want.

You can look at more information here.

-Mandar

[cpinz]

Hi kmandar,

you are referring to the mesh file, while I'm referring to *.cfg file where I find the section as the following (taken from SU2 tutorials ):

% -------------------- BOUNDARY CONDITION DEFINITION --------------------------%
%
% Navier-Stokes wall boundary marker(s) (NONE = no marker)
MARKER_HEATFLUX= ( airfoil, 0.0 )
%
% Farfield boundary marker(s) (NONE = no marker)
MARKER_FAR= ( farfield )
%
% Marker(s) of the surface to be plotted or designed
MARKER_PLOTTING= ( airfoil )
%
% Marker(s) of the surface where the functional (Cd, Cl, etc.) will be evaluated
MARKER_MONITORING= ( airfoil )




In Pointwise I create boundary condition assigning a give "type" b.c. to different part of domain, each one with its name , e.g:


name type
wing wall
inlet inlet
outlet outlet
upper domain symmetry
lower symmetry


After that I export the mesh in SU2. In order to run the analysis, I have to
fill up the SU2 *.cfg file with all data, and among them those described above relative to b.c. section.


Now my question: how have I to modify ( if I have to do it..) such section in order to match Pointwise and SU2 data correctly ?


Thank you in advance for any advice.


Cpinz

[kmandar]

Hi Cpinz,

I am guessing that the "name" of the boundary you specify in Pointwise should be the marker tag. To make sure it is so, you will have to check the .su2 file. After that it's simple- you specify the corresponding markers tags in the configuration file. SU2 will identify the boundary elements / nodes based on this marker tag and apply the corresponding boundary condition.

The options for different boundary conditions are shown in the template file.


Hope this helps,
Mandar

[cpinz]

KMandar,

I will check it.

Thank you

cpinz

[cpinz]

Hi kmandar,

your advice work. I have now another problem: my domain boundaries are composed by one farfield and two walls (represented by a main wing and a flap) . At first attempt I tried to declare the b.c. as:

%
MARKER_HEATFLUX= ( main,0 )
MARKER_HEATFLUX= ( flap,0 )
MARKER_far= ( farfield )

but I incurred in an error ( " marker_heatflux option declared twice")

then I tried wth:



MARKER_HEATFLUX= ( main,0 )
MARKER_isothermal= ( flap,298 )
MARKER_far= ( farfield )

and it seemd could work, even if I'm not sure it's the correct way ( no errors but other adjustment to make in the config. file ).

My question: which marker have I to use in the case of many "wall" boundaries ( more than two)? I didn't find any tutorial dealing with such option....

Thank you in advance

[kmandar]

Hi cpinz,

To clarify, I understand that you have two different physical boundaries (wing and flap) to which same boundary condition (heatflux) has to be applied.

I would try making the same marker tags for both the boundaries in the .SU2 file, and then specify the boundary condition just once in the config file. For example, go the SU2 file and change the marker tags for both the boundaries as 'heatflux' and then in the config file, specify

MARKER_HEATFLUX= ( heatflux )

Hope this helps,
Mandar