.cfg issues

mhollander · June 24, 2019, 15:52

Hi All,

I'm having some trouble with running a SU2 (6.2) simulation with a mesh generated with gmsh.

I have attached the .cfg (in .txt format as this forum won't let me upload anything with a .cfg extension) file here.

Whenever I try to run SU2, I end up getting the following:

...

Error in "short unsigned int CConfig::GetMarker_CfgFile_TagBound(std::__cxx11:: string)":
-------------------------------------------------------------------------
The configuration file doesn't have any definition for marker inlet
------------------------------ Error Exit -------------------------------

Has anyone else had this issue?

wallym · June 24, 2019, 16:50

Hello,

I took a look at your cfg file and it seems there is corresponding boundary conditions for the inlet of your geometry. From what I can gather, you should have have something along the lines of MARKER_INLET(inlet,x,x,x,x).

mhollander · June 24, 2019, 17:06

Quote:

Originally Posted by wallym

Hello,

I took a look at your cfg file and it seems there is corresponding boundary conditions for the inlet of your geometry. From what I can gather, you should have have something along the lines of MARKER_INLET(inlet,x,x,x,x).

Can you give a slightly more 'fleshed out' example?

I'm a little new to the SU2 and gmsh game

wallym · June 24, 2019, 17:26

Absolutely.

SU2 defines its boundary conditions using markers that are in the mesh.

For example, the config file you sent (fairing.txt) has MARKER_HEATFLUX(airfoil,0.0) and MARKER_FAR=(farfield).

This means SU2 will look for a tag within mesh called "airfoil" and assign the heatflux boundary condition to those cell. The same happens with the farfield tag.

Your error is saying that in your mesh file, you have a tag that is set to inlet. However, that portion of the boundary has no boundary assigned to it.

In this case, you can set your inlet condition with either MARKER_INLET=(inlet, total_temperature,t_pressure, dir_x,dir_y,dir_z). Or, depending on your inlet, using the MARKER_SUPERSONIC_INLET(inlet, temp, press,v_x,v_y,v_z).

You can see the options for boundary conditions in the config_template on github at https://github.com/su2code/SU2/blob/...g_template.cfg.

Please let me know if this helps, or if you have any more questions.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
chtMultiRegionSimpleFoam issues - non-conformal meshes & residual handling...	manalis	OpenFOAM Running, Solving & CFD	3	October 10, 2018 18:53
Convergence issues for Flat plate with sharp edge	rajnarayang	FLUENT	3	June 20, 2017 12:02
[ANSYS Meshing] Multizone issues (on my project)	crenaudo	ANSYS Meshing & Geometry	8	April 13, 2016 02:59
Multigrid Stability Issues	ThomasHermann	SU2	1	November 5, 2014 16:18
[General] Some Paraview Issues I can not solve	MR_Chicho	ParaView	1	September 24, 2012 05:03

June 24, 2019, 16:50		#2
wallym Senior Member Wally Maier Join Date: Apr 2019 Posts: 123 Rep Power: 7	Hello, I took a look at your cfg file and it seems there is corresponding boundary conditions for the inlet of your geometry. From what I can gather, you should have have something along the lines of MARKER_INLET(inlet,x,x,x,x).

June 24, 2019, 17:26		#4
wallym Senior Member Wally Maier Join Date: Apr 2019 Posts: 123 Rep Power: 7	Absolutely. SU2 defines its boundary conditions using markers that are in the mesh. For example, the config file you sent (fairing.txt) has MARKER_HEATFLUX(airfoil,0.0) and MARKER_FAR=(farfield). This means SU2 will look for a tag within mesh called "airfoil" and assign the heatflux boundary condition to those cell. The same happens with the farfield tag. Your error is saying that in your mesh file, you have a tag that is set to inlet. However, that portion of the boundary has no boundary assigned to it. In this case, you can set your inlet condition with either MARKER_INLET=(inlet, total_temperature,t_pressure, dir_x,dir_y,dir_z). Or, depending on your inlet, using the MARKER_SUPERSONIC_INLET(inlet, temp, press,v_x,v_y,v_z). You can see the options for boundary conditions in the config_template on github at https://github.com/su2code/SU2/blob/...g_template.cfg. Please let me know if this helps, or if you have any more questions.