[mhd_mrt]

Dear SU2 Developers/ Users,

I am simulating an unsteady moving normal shock in a tube with an extremely fine mesh which makes each one of my solution file size in the order of gigabyte (GB). As you can see in the image bellow, I only need the pressure and time at particular points in my domain and would like to write out these two variables into a SINGLE text file (similar to history.vtk) so that I can just plot them quickly, instead of having to wait a long time on PARAVIEW to load these files and plot over time the pressure at those particular locations. I have the location (coordinate in (x,y)) of the points I want to extract the pressure from.


Any advice, suggestions, similar experience would be highly appreciated as I am a new learner of SU2.

Best regards,
Mehdi

[omdemircan]

Hi Mehdi,

I have recently been trying to find a solution to this matter as well. I wanted to retrieve pressure data at specific points in the numerical field as the URANS simulation is running, a similar case to what you have in mind. Sadly, I couldn't define any points so I found the solution to be defining a surface where the points I want the data from are on, this way I could make use of the surface_flow output instead of the flow output of the solver. As you can imagine surface_flow files can be much more smaller in size compared with the flow files since they only store information on that surface instead of the whole numerical domain.
Anyways, you could try making use of the surface definition in the configuration file but again, this won't help you monitor the data during the simulation.

[mhd_mrt]

Originally Posted by omdemircan

Hi Mehdi,

I have recently been trying to find a solution to this matter as well. I wanted to retrieve pressure data at speficic points in the numerical field as the URANS simulation is running, a similar case to what you have in mind. Sadly, I couldn't define any points so I found the solution to be defining a surface where the points I want the data from are on, this way I could make use of the surface_flow output instead of the flow output of the solver. As you can imagine surface_flow files can be much more smaller in size compared with the flow files since they only store information on that surface instead of the whole numerical domain.
Anyways, you could try making use of the surface definition in the configuration file but again, this won't help you monitor the data during the simulation.

Dear Omdemircan,

I actually thought about doing that exactly like you mentioned by writing a MATLAB code which searches through the .csv files (which are much smaller in size) and take pressure out from each file. What I am wondering now is that, is it only possible to define a wall or an edge in the outer domain as MARKER_PLOTTING (for example you can see from the image above: T9 and T12) or if I have a point which is literally inside the domain (as you can see above in my image for example: T1, T2, T3) can I name multiple small edges in my mesh and then define them in my .cfg file as MARKET_INTERNAL ? because technically, according to config_template.cfg it says the following:

% Internal boundary marker(s) e.g. no boundary condition (NONE = no marker)
MARKER_INTERNAL= ( NONE )


Thanks!
Mehdi

[omdemircan]

Personally, I needed only pressure data on walls so I haven't tried the MARKER_INTERNAL option. However, you could create a surface in your mesh which includes the points you need and define it as internal in the configuration file as you said. I think it should work as long as your surface exists in your mesh and it has a name.

[mhd_mrt]

Dear SU2 developers,

As I am trying to make direct comparison of pressure at multiple location in my 2D mesh, I really need to learn how to output the pressure only at those nodes for every iteration and not just read them from the .csv files that get generated using the MARKER_PLOTTING function. If anyone can please point me in the right direction as to where I need to start and look for in the code in order to accomplish this, I would sincerely appreciate it. I know that some developers are actively working on this (https://github.com/su2code/SU2/issues/466) however, since I do not know when this feature will be officially implemented in the new version of SU2, I would like to do it quickly for my specific case.

Any advice, suggestions, and insight in regards to this will be highly appreciated.

Cheers,
Mehdi