Get the python script to remesh for RAE2822

[calumy]

• [x] Get script to copy original .geo file and gmsh.exe to mesh folder
• [x] Get script to mesh original .geo file
• [x] Get script to calculate gradient fields for both mach and pressure
• [x] Get script to calculate flow fields for both mach and pressure
• [x] Get script to add gradient values to original mesh
• [x] Get script to add flow field values to original mesh
• [x] Get script to remesh for one iteration
• [x] Get script to remesh for more than one iteration

[calumy]

Current error: "IOError: [Errno 2] No such file or directory: 'MachGradient.csv'"

This error comes from this section of code:

gradFields = [] for f, fieldName in enumerate(remeshingInfo.gradientQuantities): gradFields.append([])

firstDataCol = 0
with open(fieldName + 'Gradient.csv', 'rb') as csvfile:
  nodeDataReader = csv.reader(csvfile, delimiter=',')
  row1 = next(nodeDataReader)
  for colCnt, c in enumerate(row1):
    if fieldName + 'Gradient:0' in c:
      firstDataCol = colCnt
      break

with open(fieldName + 'Gradient.csv', 'rb') as csvfile:
  nodeDataReader = csv.reader(csvfile, delimiter=',')
  next(nodeDataReader)
  for row in nodeDataReader:
    gradFields[f].append(mag([float(c) for c in row[firstDataCol:firstDataCol+3]])) # magnitude of the gradient

There is no mention of the 'MachGradients.csv' before this point in the script. At this point, Run0 has been compleated and the following files have been output in the run folder:

• convergence.vtk
• forces_breakdown.dat
• soln_volume.vtk
• solution_flow.dat
• surface_flow.csv
• surface_flow.vtk

As well as the files used to configure and run the simulation.

The 'solution_flow.dat' holds information on

• PointID
• x
• y
• Conservative_1
• Conservative_2
• Conservative_3
• Conservative_4
• Pressure
• Temperature
• Pressure_Coefficient
• Mach

Will look into how to convert this to the correct fromat that can be read by the python script.

[calumy]

'ComputeGradients.py' was run using pvpython to compute 'MachGradient.csv' and 'PressureGradient.csv'.

Both files have been attached as '.xlsx' files as '.csv' files are not supported by GitHub.

It was interesting to note that there was no data for 'MachGradient:2', 'PressureGradient:2' and 'Points:2' on both files. Will investigate further.

MachGradient.xlsx

PressureGradient.xlsx

[calumy]

Noticed that the inputs for RAE2822 do not have any flow fields. This means that the program has not been calculating them.

The 3D case has a flow quantity defined as Mach.

[calumy]

Successfully managed to remesh for one iteration.

Original mesh and remeshed mesh images and files attached. Files are in '.txt' format at '.msh' is not supported.

Origional mesh:

Remeshed mesh:

RAE2822_v0.txt RAE2822_v1.txt

[calumy]

Gradients for original mesh are:

Mach Gradients:

Pressure Gradients:

It can be seen that the mach and pressure gradients are greatest at the shock that occurs on the upper surface of the aerofoil.

The images below show the mach and pressure for the original run:

Mach Plot:

Pressure Plot:

[calumy]

There appears to have been an error when the mach and pressure gradients were calculated for the second run.

Mach Gradients:

In this image, the blue background should not be visible.

Pressure Gradients:

Like the mach gradients, the blue background should not be visible.

When the next itteration was run, this caused the error: 'Info : No scalar element found containing point' as gmsh could not find data for each node.

[calumy]

Flow field 'mach' added.

[calumy]

Changed the way that the run folder was created and this has solved the gradients issue above. Before a .su2 file was copied from the base directory for every run. Now the .su2 file that is created for each mesh is copied to each run folder.

Mach Plot: Run 0:

Run 1:

Run 2:

Run 3:

It can be seen that the position of the shock on the top surface of the aerofoil becomes more defined and the position of where it interacts with the top surface moves towards the back of the aerofoil.

Mesh: Run 0:

Run 1:

Run 2:

Run 3:

It can be seen that the mesh density increased from run 0 to run 3, specifically around the location of the shock on the top edge.

Mesh Details Run Nodes Elements 0 2006 4012 1 6458 12916 2 6222 12444 3 9575 19514