mdolab
Unsteady timestep doesn't stop after l2Convergence is reached
Type of issue
What types of issue is it?
- Bug (probably?)
Description
In an unsteady RANS simulation, the solver doesn't stop when the l2Convergence is reached for a given timestep.
Steps to reproduce issue
Run the attached files.
Current behavior
The following behavior only happens after the first time step. The first time step works fine.
If the RK or DADI solver is used, the solver runs until nCycles is reached. If the ANK solver is used, the CLF number goes to 0 after l2Convergence is approximatly reached. Even though there is an ankcflmin of 1.0. The NK solver just stops making progress after l2Convergence is approximatly reached.
Expected behavior
Once l2Convergence is reached, the solver should stop executing the current timestep and start the next one.
Code version (if relevant)
adflow 2.2
Would you mind posting the text output by the program. That would help a great deal.
@DavidAnderegg, I believe you need to disable blockettes if you want to use ANK or NK with an unsteady simulation with the following option: 'useblockettes':False,. Also, I suggest adding this parameter in your runscript to prevent stalling of the ANK solver: 'anklinresmax':0.1,. Finally, I would also add 'nsubiterturb':5, to the options if you use the ANK solver.
The stalling is gone, otherwise it's the same result.
run_adflow_unsteady_implicit_nonBlockette.txt unsteady_implicit_nonBlockette.log
That is odd that it doesn't stop at 0.18E0. When I change the L2Convergence to something very small like 1e-2 it stops at 0.18e6 as it should.
Definitely looks like a bug to me.