[DataDriven]

Hi all,

I've had issues where a DES simulation would not write the final time-step due to inaccuracies in the timestep because I'm using single precision. (It never reaches the required time of 10 because due to single precision the time of final iteration is 9.99875 or something like that, causing the final result to not be written.)

Now i'm trying a workaround, by allowing slightly more iterations than required and using timeActivatedFileUpdate to change the controlDict and stop the simulation by setting 'stopAt writeNow'. However, it doesn't work...

I'm testing with the pitzDaily case now. The timeActivatedFileUpdate updates the controlDict perfectly fine at the required time, also runTimeModifiable is set to true so I don't understand why it doesn't stop the run.

Please find the used controlDict's attached, does anyone have an idea why this doesn't work?

Thanks!

[Tobermory]

Have you tried using the

writeControl adjustableRunTime

(or adjustable in the ESI version, I think)? This will adjust the time step to make sure that the save occurs exactly at the required interval. That might cure the original problem of getting a save at t=10.

[DataDriven]

No I have not. Thank you, solving the original problem is of course more elegant!

Will give it a try and report what I found.

[DataDriven]

However, I'm also still keen to learn why stopAt writeNow doesn't work as expected.

[Tobermory]

Haha! Me too! I tried doing something similar around a year ago to change time step sizes I think, and I ended up tearing my hair out since it seemed to be ignoring the changes to the controlDict (i.e. was not rereading the new deltaT). In the end, I gave up trying to control the run from inside, and instead managed the run parameters externally with the Allrun script.

If you have a simple test case that you can reproduce this on, then it may be worth uploading it as a "bug" and see what the Development team say, since it clearly isn't working as intended. Let us know if you find a fix. Good luck.