Error-"There is no flow restart file!! Solution_flow.dat. "
 

Hi,

I'm new to SU2 so this might be a noob question.

I was following the "quick start" tutorial, but I got an error stating "There is no flow restart file!! Solution_flow.dat." after I entered "SU2_CFD inv_NACA0012.cfg". Attached is a screenshot explaining the situation.

The OS of my computer is win8.1 and the version of SU2 I installed is "SU2-Parallel--3.2.200-64-bit".

Any insights would be appreciated!
Eric

Updates:

Now I just solved my problems.

I changed the RESTART_SOL value in the configuration file from YES to NO, then I got no more flow restart file errors. This may seem pretty much obvious but the quick start tutorial does not mention this at all.

As for the second problem, I added a new system variable "PATH, C:\SU2", then "SU2_CFD" was recognized as a valid command.
Attachment 35481

Updates:

I copied those .dat files from the TestCase to the SU2 directory then the SU2_CFD solver proceeded just fine, but the quick start tutorial does not mention this and it seems kind of funny that I need those result files to run the solver.

And I have another question. Do I need to copy the configuration & mesh files to the SU2 directory every time I run the solver? I added "SU2_RUN" to the system variants but every time I entered "SU2_CFD blabla.cfg" at the command line under any other directory, I got a message saying it is not "recognized as an internal or external command".

It is not necessary to copy the configuration and mesh file to your SU2 directory every time. Can you just tell what system variables you have added and what path you have given? Also let me know the directory where SU2 has been installed?

Updates:

Now I just solved my problems.

I changed the RESTART_SOL value in the configuration file from YES to NO, then I got no more flow restart file errors. This may seem pretty much obvious but the quick start tutorial does not mention this at all.

As for the second problem, I added a new system variable "PATH, C:\SU2", then "SU2_CFD" was recognized as a valid command.

Hi Sachchit,

Thank you for your response.

I added a new system variable "PATH, c:\SU2", then this problem is no more.

The system variable I added before this one is "SU2_RUN, c:\SU2" and the installation directory is "c:\SU2". I still get no idea why this "SU2_RUN, c:\SU2" variable is needed.:confused:

Great,

I don't know about windows but in linux system it is helpful to directly access the directory by using command cd $SU2_RUN. In linux system also path should be added to system's $PATH.