Unnecessary data from SU2 solver in the C drive
 

Dear SU2 experts,
Hope you are doing great! I have started using SU2 recently. My simulations are running fine and completing successfully. However, after each simulation run, I am seeing that my C drive is getting filled with unknown data. I am guessing that SU2 solver is dumping extra files somewhere, despite the result files being written in the folder where the configuration and su2 mesh file are placed.

Would you be kind to let me know, in which folders the SU2 solver is shedding this unncessary files!! I am not finding them unfortunately and my C drive is running out of space. To mention, my result files are a couple of MB large, although after each simulation run, space in GB is getting occupied in the C drive, which is not logical.

Thanks for your help. I appreciate.

Best regards,
Zahid

Hi,
The code writes all the outputs with respect to the current directory.
No idea what version or branch you are working with though.

Hi Pedro,
Thank you for your reply. I am using the Nemo Navier Stokes solver in SU2 version 7.3.1. Using Windows 10 operating system.
Do you need any other information for an initial guess? For your convenience, I have attached below the input/output option I am using in the configuration file. Again, I appreciate your reply.

% ------------------------- INPUT/OUTPUT INFORMATION --------------------------%
%
% Mesh input file
MESH_FILENAME= cooling5.su2
%
% Mesh input file format (SU2, CGNS, NETCDF_ASCII)
MESH_FORMAT= SU2
%
% Mesh output file
MESH_OUT_FILENAME= mesh_out.su2
%
% Restart flow input file
SOLUTION_FILENAME= solution_flow.dat
%
% Restart adjoint input file
SOLUTION_ADJ_FILENAME= solution_adj.dat
%
% Output tabular format (CSV, TECPLOT)
TABULAR_FORMAT= CSV
%
% Output file formats
% OUTPUT_FILES= PARAVIEW
%
% Frequency at which the paraview file is written
% OUTPUT_WRT_FREQ= 50
%
% Output file convergence history (w/o extension)
CONV_FILENAME= history
%
% Output file restart flow
RESTART_FILENAME= restart_flow.dat
%
% Output file restart adjoint
RESTART_ADJ_FILENAME= restart_adj.dat
%
% Output file flow (w/o extension) variables
VOLUME_FILENAME= flow
%
% Output file adjoint (w/o extension) variables
VOLUME_ADJ_FILENAME= adjoint
%
% Output objective function gradient (using continuous adjoint)
GRAD_OBJFUNC_FILENAME= of_grad.dat
%
% Output file surface flow coefficient (w/o extension)
SURFACE_FILENAME= surface_flow
%
% Output file surface adjoint coefficient (w/o extension)
SURFACE_ADJ_FILENAME= surface_adjoint
%
%
% Screen output
SCREEN_OUTPUT=(INNER_ITER, WALL_TIME, RMS_DENSITY, RMS_ENERGY, LIFT, DRAG)

% ----------------------- DESIGN VARIABLE PARAMETERS --------------------------%
%
%
% Kind of deformation (NO_DEFORMATION, SCALE_GRID, TRANSLATE_GRID, ROTATE_GRID,
% FFD_SETTING, FFD_NACELLE,
% FFD_CONTROL_POINT, FFD_CAMBER, FFD_THICKNESS, FFD_TWIST
% FFD_CONTROL_POINT_2D, FFD_CAMBER_2D, FFD_THICKNESS_2D,
% FFD_TWIST_2D, HICKS_HENNE, SURFACE_BUMP, SURFACE_FILE)
DV_KIND= SCALE_GRID
%
% - NO_DEFORMATION ( 1.0 )
% - TRANSLATE_GRID ( x_Disp, y_Disp, z_Disp ), as a unit vector
% - ROTATE_GRID ( x_Orig, y_Orig, z_Orig, x_End, y_End, z_End ) axis, DV_VALUE in deg.
% - SCALE_GRID ( 1.0 )
DV_PARAM= ( 1.0 )
%
% Value of the deformation
DV_VALUE= 10.0

We need to know which files are being written.

You can do a 'find all recent files' check on the entire disk to see which files were created during the last hour or so (immediately after running an SU2 simulation). You can also search for large files, but it could be many, many small files as well, so better search for recent files.