|
[Sponsors] |
January 10, 2023, 07:12 |
Monitoring/Sampling points
|
#1 |
New Member
VladJ
Join Date: Feb 2012
Location: Belgium
Posts: 18
Rep Power: 14 |
Dear all,
I was wondering if it is possible to define sampling/monitoring points within the volume and sample field variables at those points in time. I am doing IDDES simulations with a 20 million points grid and it is a bit irrational to save the whole volume at every time step, then extract time evolution of a field variable at some point, just to be able to perform 2-point correlation to calculate integral length scale. There must be some convenient approach for this task, I am clueless though. Thanks in advance! |
|
January 10, 2023, 17:56 |
|
#2 |
Senior Member
bigfoot
Join Date: Dec 2011
Location: Netherlands
Posts: 615
Rep Power: 18 |
There is currently no way to save point data. However, you can save surface data.
What you can do is define an internal surface and write the information on that surface to a file. First, you define an internal surface, and the easiest way to define it is by using existing mesh points. This surface can be for instance a face of an existing cell in the domain or any points that define a triangle or a quadrilateral. Some meshing tools allow adding an internal face, in that case you just need to make sure that the face is very small and that the surface mesh consists of only one cell. Else you need to find the ID of some existing points in the mesh. If you are manually adding the internal face to the su2 file, then simply increase the nr of markers by 1 and add a marker. For a quadrilateral, the surface type is "9", followed by the ID of the 4 points, for a triangle it is "5" followed by the ID of the 3 points: Code:
NMARK= 10 // increase this number MARKER_TAG= internal MARKER_ELEMS= 1 9 8 230 3980 357 // 9 p1 p2 p3 p4 ... Then, you add this to your config file: Code:
MARKER_PLOTTING= ( internal ) // name(s) of the surfaces OUTPUT_FILES= SURFACE_CSV // type of file SURFACE_FILENAME= monitorsurface // filename WRT_SURFACE_OVERWRITE= NO // do not overwrite the file, you will get a file for every OUTPUT_WRT_FREQ iteration OUTPUT_WRT_FREQ= 1 // writing frequency Last edited by bigfootedrockmidget; February 1, 2023 at 17:35. Reason: clarification |
|
January 12, 2023, 04:45 |
|
#3 |
New Member
VladJ
Join Date: Feb 2012
Location: Belgium
Posts: 18
Rep Power: 14 |
Thank you for the reply. I will try this approach with internal sampling face again, although I did try it in the past and, I might have made some mistake though, it did not work because I think SU2 sees internal face as a wall (the internal face was defined as a two-sided infinitely thin surface). My mesh is in 3D and if this approach works, then great!!! That also means that I can use internal face around solid body to sample unsteady pressure for aeroacoustic post-processing.
Will be back to this post soon. Cheers! |
|
February 2, 2023, 05:04 |
|
#4 |
New Member
Dónal McCaughey
Join Date: Sep 2021
Posts: 9
Rep Power: 5 |
Thanks for your quick reply (to LES post processing in SU2 - statistically steady state), this exactly what I was looking for. I'm replying here just to keep this discussion together for anyone who comes looking for the same thing.
Will the internal marker definitely not have any effect on the flow? Last edited by Dónal; February 2, 2023 at 05:20. Reason: Added link |
|
February 2, 2023, 05:12 |
|
#5 | |
New Member
VladJ
Join Date: Feb 2012
Location: Belgium
Posts: 18
Rep Power: 14 |
Quote:
Will keep you posted. |
||
February 2, 2023, 07:24 |
|
#6 |
Senior Member
bigfoot
Join Date: Dec 2011
Location: Netherlands
Posts: 615
Rep Power: 18 |
Internal markers are ignored as boundary conditions.
The main challenge is to find an existing cell face that is close to the location that you would like to monitor. If you need exact point locations, you need to define the faces of the cell containing your actual point of interest as internal markers. You can then determine the information at the point location by bilinear interpolation. |
|
February 4, 2023, 22:57 |
|
#7 |
Senior Member
Pedro Gomes
Join Date: Dec 2017
Posts: 466
Rep Power: 13 |
I've implemented point probes here https://github.com/su2code/SU2/pull/1909
They will be in the next release of SU2 |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[snappyHexMesh] stringing of feature edges | Hr_kules | OpenFOAM Meshing & Mesh Conversion | 0 | July 22, 2022 08:30 |
[snappyHexMesh] Invalid Normals for source face to target face while making AMI? | Sorabh | OpenFOAM Meshing & Mesh Conversion | 1 | August 3, 2021 06:35 |
SU2-7.0.1 on ubuntu 18.04 | hyunko | SU2 Installation | 7 | March 16, 2020 04:37 |
[snappyHexMesh] layer not added | Rasmusiwersen | OpenFOAM Meshing & Mesh Conversion | 1 | January 2, 2020 09:43 |
[blockMesh] BlockMeshmergePatchPairs | hjasak | OpenFOAM Meshing & Mesh Conversion | 11 | August 15, 2008 07:36 |