[gittagawa]

According to SU2 documentation (https://su2code.github.io/docs/Restart-File/), for the reinitialization of a simulation, the restart files should be renamed as solution_flow_00098.dat and solution_flow_00099.dat. In this case, the solution would restart at UNST_RESTART_ITER = 100. I have been doing this for a while. However, today, as I restarted a simulation, I received the following message: "Unable to open SU2 restart file temperature_flow_sa_00098.dat". Once the name is renamed to "temperature_flow_sa_00098.dat", it works. I am wondering whether it only happens in specific cases? If so, what are those cases? Thanks!

[hlk]

Thanks for your interest in SU2.
First, did you update the code between these two behaviors? If the code version is the same then it will be the details of the configuration file that will be helpful to figuring out the problem.



Generally, the input file name for restarting the solution is determined from the option :

SOLUTION_FLOW_FILENAME

has that option been changed? By default it is set to solution_flow.dat, and the unsteady iteration number is automatically added.


If you were using the same config file between two code versions, please reply with what those two versions where.

Originally Posted by gittagawa

According to SU2 documentation (https://su2code.github.io/docs/Restart-File/), for the reinitialization of a simulation, the restart files should be renamed as solution_flow_00098.dat and solution_flow_00099.dat. In this case, the solution would restart at UNST_RESTART_ITER = 100. I have been doing this for a while. However, today, as I restarted a simulation, I received the following message: "Unable to open SU2 restart file temperature_flow_sa_00098.dat". Once the name is renamed to "temperature_flow_sa_00098.dat", it works. I am wondering whether it only happens in specific cases? If so, what are those cases? Thanks!

[gittagawa]

Hello hlk,

Thank you for your response and sorry for my late reply. I used the same config file and the same SU2 version (the last one, 6.1.0). I used different clusters though. Do you think that might have caused the problem?

Thanks!

[hlk]

I don't think so.
What is set under the SOLUTION_FLOW_FILENAME option, in the config file where you are seeing this problem?

Originally Posted by gittagawa

Hello hlk,

Thank you for your response and sorry for my late reply. I used the same config file and the same SU2 version (the last one, 6.1.0). I used different clusters though. Do you think that might have caused the problem?

Thanks!

[gittagawa]

You were right. I messed up my config files. The SOLUTION_FLOW_FILENAME was set as temperature_flow_sa.dat

Thanks a lot and sorry about that.