[maero21]

I have a Cgrid mesher and I want to import those meshes to SU2 (I know SU2 IS unstructured, but for the airfoils I am looking at structured is fine and will save me a bunch of time).

So I wrote this simple utility that produces an .su2 mesh file for me. However, whenever I try to read it into SU2 I get the error

 
------------------- Config File Boundary Information --------------------
Euler wall boundary marker(s): airfoil.
Far-field boundary marker(s): farfield.

---------------------- Read Grid File Information -----------------------
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

A (small) mesh file is below (it should follow VTK guidelines):
This is for a mesh with 12 grid points in circumferential direction, and 3 in radial direction.

 % 
 % Problem dimension
 % 
 NDIME = 2
 % 
 % Inter-element connectivity
 % 
 NELEM =           22
 9           1           0          12          13           0
 9           2           1          13          14           1
 9           3           2          14          15           2
 9           4           3          15          16           3
 9           5           4          16          17           4
 9           6           5          17          18           5
 9           7           6          18          19           6
 9           8           7          19          20           7
 9           9           8          20          21           8
 9          10           9          21          22           9
 9          11          10          22          23          10
 9          13          12          24          25          11
 9          14          13          25          26          12
 9          15          14          26          27          13
 9          16          15          27          28          14
 9          17          16          28          29          15
 9          18          17          29          30          16
 9          19          18          30          31          17
 9          20          19          31          32          18
 9          21          20          32          26          19
 9          22          21          26          25          20
 9          23          22          25          24          21
 % 
 % Node coordinates
 % 
 NPOIN =           33
   9.000000000000000000  -7.999999999998841815         0
   1.374561651340881152  -7.999999999998841815         1
   1.000000000000000000  -7.999999999998841815         2
  -0.473651884200968598  -7.985966058817985491         3
  -3.501784764939268157  -7.192878662958192670         4
  -7.282200719538992395  -3.312031503525560527         5
  -7.282200719538993283   3.312031503525558307         6
  -3.501784764939267269   7.192878662958192670         7
  -0.473651884200974704   7.985966058817985491         8
   1.000000000000000000   8.000000000001158185         9
   1.374561651340881152   8.000000000001158185        10
   9.000000000000000000   8.000000000001158185        11
   9.000000000000000000  -0.733156942062543115        12
   1.747606522076315061  -0.484118770069994542        13
   1.576919757980695724  -0.365980135480807434        14
   1.403501101027856413  -0.225935379743087472        15
   1.292376126906428668  -0.074207065000667385        16
   1.276537012110866787   0.034424674229240983        17
   1.307402843892234490   0.144353478783667638        18
   1.365358993969906676   0.246981530474894018        19
   1.478394489094279063   0.366227865480066139        20
   1.630711717212376399   0.475605666037241803        21
   1.786183523867048262   0.564052873633749896        22
   9.000000000000000000   0.834193325300002009        23
   9.000000000000000000   0.000000000001157872        24
   1.374561651340881152   0.000000000001157872        25
   1.000000000000000000   0.000000000001157872        26
   0.621348638645393581  -0.025781478272765931        27
   0.245349582696308660  -0.041969327156491890        28
   0.012408446461356724  -0.017636146643447585        29
   0.019242287627879662   0.025033079434219337        30
   0.274084380099760216   0.077534536736258319        31
   0.635232084930189567   0.058763875711443529        32
 % 
 % Boundary elements
 % 
 NMARK= 2
 MARKER_TAG= airfoil
 MARKER_ELEMS=            7
 3           26          27
 3           27          28
 3           28          29
 3           29          30
 3           30          31
 3           31          32
 3           32          26
 MARKER_TAG= farfield
 MARKER_ELEMS=           15
 3            1           0
 3            2           1
 3            3           2
 3            4           3
 3            5           4
 3            6           5
 3            7           6
 3            8           7
 3            9           8
 3           10           9
 3           11          10
 3            0          12
 3           12          24
 3           11          23
 3           23          24

Note that I actually use a larger mesh when trying to run SU2 (because this mesh is so small some of the nodes are intersecting with the boundary).

Are there any other mesh requirements in order for SU2 to read it in?

[maero21]

Don't mind me, fixed it.

[jvbustelo]

Originally Posted by maero21

Don't mind me, fixed it.

Hello maero21,

I am obtaining the same error when creating a mesh with Salome and exporting it with the ExportSU2File command of cfdmsh. How did you fix it? Do you still remember?

Thank you very much in advance.

[maero21]

For some reason SU2 has some issues handling I/O. What you can see in the example in my mesh above is that there is a space in front of everything (including comments). When you delete that space, everything should work correctly.

[jvbustelo]

Hello maero21,

It was indeed an issue with the .su2 file definition. Specifically, I used a python code that I found on another thread to export from Salome into SU2 format directly. When taking a look at the code I saw that the file exported had many grammatical errors (give element numeration to marker elements and not giving them type).

Thank you very much for your reply anyways.