CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > SU2 > SU2 Shape Design

Unsteady adjoint iteration number

Register Blogs Community New Posts Updated Threads Search

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   December 11, 2019, 14:08
Post Unsteady adjoint iteration number
  #1
New Member
 
Eduardo de Oliveira Carvalho
Join Date: Mar 2018
Location: São José dos Campos - SP. Brazil
Posts: 15
Rep Power: 8
Eduardo Carvalho is on a distinguished road
Hi All,

I'm trying to run the unsteady adjoint pitching_naca64a010_rans test case, but I'm always finding the same error at the log_Adjoint.out file:

Loading flow solution from direct iteration -1.


Error in "std::__cxx11::string CConfig::GetUnsteady_FileName(std::__cxx11::string , int)":
-------------------------------------------------------------------------
Requesting a negative iteration number for the restart file!!
------------------------------ Error Exit -------------------------------


It seems that the "UNST_ADJOINT_ITER=" command sets the first direct iteration to be used at the adjoint solution, but iterating at an inverse temporal sequence.

The problem seems to be that the adjoint solver doesn't stop at iteration number 0 and tries to continue to -1, where the error occurs.

Can I set a specific iteration where this process stops?
How can I choose the range of direct iterations used by the adjoint solver?

I'm using SU2 Version 6.2.0 "Falcon".
Eduardo Carvalho is offline   Reply With Quote

Old   December 18, 2019, 14:11
Default
  #2
New Member
 
Eduardo de Oliveira Carvalho
Join Date: Mar 2018
Location: São José dos Campos - SP. Brazil
Posts: 15
Rep Power: 8
Eduardo Carvalho is on a distinguished road
I finally solved this problem for v6 using:

RESTART_SOL= NO (This command needs to be specified, although I don't know exactly it's effect at the adjoint optimization)

UNST_RESTART_ITER = 2 (Even with "RESTART_SOL= NO" this parameter still needs to be specified, or SU2 will stop at the first design. I also don't know it's effect at the optimization, but using "2" seems to work)

EXT_ITER= 99999 (Setting this parameter smaller than the number of possible iterations made by the physical time will generate an index error, the same one that I described on my previous message, so use "EXT_ITER" >= "UNST_TIME" / "UNST_TIMESTEP" )

% Restart flow input file
SOLUTION_FLOW_FILENAME= restart_flow.dat
%
% Restart adjoint input file
SOLUTION_ADJ_FILENAME= solution_adj.dat
%
% Output file restart flow
RESTART_FLOW_FILENAME= restart_flow.dat
%
% Output file restart adjoint
RESTART_ADJ_FILENAME= restart_adj.dat
Eduardo Carvalho is offline   Reply With Quote

Reply

Tags
adjoint solver, optimizaion, unsteady


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
decomposePar no field transfert Jeanp OpenFOAM Pre-Processing 3 June 18, 2022 13:01
parallel run OpenFoam Srinath Reddy OpenFOAM Running, Solving & CFD 13 February 27, 2019 10:15
[blockMesh] --> foam fatal error: lillo763 OpenFOAM Meshing & Mesh Conversion 0 March 5, 2014 11:27
decomposePar pointfield flying OpenFOAM Running, Solving & CFD 28 December 30, 2013 16:05
AMI interDyMFoam for mixer danny123 OpenFOAM Running, Solving & CFD 4 June 19, 2013 05:49


All times are GMT -4. The time now is 20:21.