Steady-state override
Dear TOUGH community,
I'm running some simple simulations and reach steady-state too early.
"
!!!!!!!!! FOR 10 CONSECUTIVE TIME STEPS HAVE CONVERGENCE ON <NumNRIterations> = 1
==> WRITE OUT CURRENT DATA, THEN STOP EXECUTION
"
Yet, I do want the simulations to keep going because action is around the corner and I need to export specific times. I could reduce RE1 but it is the only solution? I couldn't find any other input parameter which would help.
For example, could I change the number of consecutive time stepswhich trigger the "stop execution" (from "10" to "100") ? Or is it hardwired in the source code?
Thank you
Ludo
1 reply
-
Hi Ludo,
In case you are using iTOUGH2, simply set MOP2(1)=2 and it enforces at least 2 Newton-Raphson iterations, so it never converges in a single iteration and always updates the primary variables. This feature may also be available in TOUGH3 (I'm not sure, though).
In iTOUGH2, you can also increase the maximum number of time steps converging in a single iteration using command >>> consecutive: max_iter1. Increasing the fixed number of 10 in whatever version of TOUGH you are using would also be easy.
However, my main recommendation would be to accept the insight that nothing is happening in the system for a while. Then just remove all the tiny-spaced printout times causing the problem. In a simple post-processing step, just take the output at the beginning of this inactive period and copy (rather than "exporting") it as many times as you need until the period converging in a single time step is over - after all, you know that the primary variables stay the same until you turn the corner.
I hope everything is going well down under.
Cheers,
Stefan