[kmiller]

Hello! I am new to SU2 and am having trouble with a few of the basics. I have a file running and I think it should be done by now, but there isn't anything in my output folder. Is there a way to check the progress of my run or simply end it to see the results thus far? I'm also wondering how to display output during the run. I'm running it on a remote computer and I'm SSH-ing in through a terminal on my laptop but all I am able to see is the file directory, from here how can I navigate to the output?

And to avoid future, potentially unnecessary, posts, is there an existing document that contains answers to questions like these?

[lejonetfrannorden]

Hello,

It should be written on your configuration file. For example, I use this to differentiate the solutions of different turbulence models.

% ------------------------- INPUT/OUTPUT INFORMATION --------------------------%
%
% Mesh input file
MESH_FILENAME= your_mesh_file_name_here.su2
......
......
......
% Output file flow (w/o extension) variables
VOLUME_FLOW_FILENAME= flow_sa

Examining the quote above, at the bottom you can see that my volumetric flow output filename is flow_sa. I get flow_sa.dat/csv files in the folder which contains my .cfg file. You can also use history file to check the convergence. You can navigate the corresponding folder in the SSH and see the results with a plotting software.

[pcg]

Hello,

If you want SU2 to output the current solution every N steps set WRT_SOL_FREQ= N in the config file. In parallel only the native format files are outputted by default (I am not sure if there is an option to override that), nevertheless you can always run SU2_SOL manually to convert the solution files when you want to check them.

Cheers,
Pedro

[hlk]

In general for running programs on a remote computer (and often for command-line programs in general), you will want to redirect the output:

SU2_CFD inputfile.cfg >& outputfile.txt &



SU2 will print a lot of information as soon as it starts, so you will be able to see whether it's working immediately by looking at the content of the output file.



The '>' symbol redirects the output that would normally be printed to the terminal to the specified file, the first '&' symbol tells it to also output error messages to the same file, and the second '&' symbol backgrounds the process. This works for any command-line process started from a linux (I think mac as well?) terminal, and similar commands also exist for windows terminals. If you haven't been told otherwise, the remote computer is probably linux. Other useful commands can be found by googling 'linux terminal commands'.



If you haven't logged out since you started the process, use the 'ps' command to see if the process is still running or not. What happens to the process if you log out, and whether you need a batch submission script (aka slurm or PBS) depends on the remote system, and you'll need to refer to their documentation or ask a system administrator to figure that out.



In terms of other existing documents for SU2, if you have not already found them I suggest the tutorials: https://su2code.github.io/

Originally Posted by kmiller

Hello! I am new to SU2 and am having trouble with a few of the basics. I have a file running and I think it should be done by now, but there isn't anything in my output folder. Is there a way to check the progress of my run or simply end it to see the results thus far? I'm also wondering how to display output during the run. I'm running it on a remote computer and I'm SSH-ing in through a terminal on my laptop but all I am able to see is the file directory, from here how can I navigate to the output?

And to avoid future, potentially unnecessary, posts, is there an existing document that contains answers to questions like these?