[Arad]

I shall appreciate a suggestion:

A common situation in direct solution: You restart from a previous solution
(where say, AOA = 0.) aiming at the solution of different condition (say AOA=4.0).
This does not happen: The restart value overwrites the new cfg data. How can this be avoided?

An example: Setting the cfg file:

RESTART_SOL= YES
AOA= 4.0
SOLUTION_FLOW_FILENAME= solution_flow.dat
#(that was obtained before with AOA=0)

Starting SU2_CFD (serial or parallel mode) the output printout acknowledges the cfg:

"Angle of attack (AoA): 4 deg, and angle of sideslip (AoS): 0 deg."

But then you get the following warning:

"WARNING: AoA in the solution file (0.000 deg.) +
AoA offset in mesh file (0.000 deg.) = 0.000 deg."

and the code is running with the AOA of the solution (restart) file (0 in this case).

The warning is issued by SU2/SU2_CFD/src/solver_structure.cpp:2768:
issued by:

if ((config->GetAoA() != AoA_)

Actually the overwriting happens in solver_structure.cpp:2567:
AoA_ = Restart_Meta[0];

Is there a way to prevent this overwriting (other than modify the cpp file)?

Thanks,
Eran Arad

[fpalacios]

Hi Eran,

Oops... this is a clear problem with the SU2 documentation we will fix this to make it more clear.

As you know, we are storing the AOA in the solution file to be able to restart the solver when are running at a constant Cl (so the AoA in your config file is not correct). If you don't want to use the info in the solution file or the mesh file you just need to use :

%
% Discard the data storage in the solution and geometry files
% e.g. AOA, dCL/dAoA, dCD/dCL, iter, etc.
% Note that AoA in the solution and geometry files is critical
% to aero design using AoA as a variable. (NO, YES)
DISCARD_INFILES= YES

Best,
Francisco

[Arad]

Thanks Fransico
It works well now
Eran

[Arad]

Sorry, should have been Francisco