Hello!

I am trying to implement "restart" functionality in my code, where if for some reason the code stops (i.e. iterations drop) I can pick up from where I started.

Here's what I did so far:

1. Load last iteration data files as my initial conditions in main ICs loop
2. Load last iteration time as well, as my start time before starting iterations loop
3. Use last iteration time as initial time + dt and update
4. Update all variables with iteration loop and save

Now, this logic works fine for me and returns correct output for the first iteration only before it restarts everything from the start for the following iterations.

Here's an example output from my code, assume these are the expected "correct" output:


the two numbers I am printing out after each iteration, are for checks and represent speed and dt in my code respectively. Now, what I have implemented returns the following:

where for the first iteration : iteration, t, phi_iter, and dt look about right or correct, but everything else resets to my original initial conditions, as if I am overwriting something. The issue is testing this code on small scale, i.e updating time and what not works but the moment I implement on large-scale things get messed up. I have no idea what I am doing wrong with my logic.

The full code can be found here:
https://www.zipshare.com/download/eyJhcmNoaXZlSWQiOiJjYzAzZTMzNi03MzU4LTRiMjUtODdmYy00ZTg2MmM2NGEyZTAiLCJlbWFpbCI6ImFzdHJvbHVqeUBnbWFpbC5jb20ifQ==

Thanks!

you will get more help if you put it in a repo where we can see the code without downloading it.

That aside, check your logic.
when you want to restart, you need *everything* done up to that point. you have to save the loop iteration counter(s) and current value of every relevant variable, and your code should be like

for(int i = valuefromfile; i< endval; i++)
not for (i=0; ...)

and so on. its a lot like the code for undo/redo, only more complicated as most of those only take snapshots once an action is completed or before it starts, never in the middle. If you can afford to do so, using that approach or the next thing to it is better -- eg if you have nested loops, maybe wait for the innermost to finish and only save the outermost one as an in-progress .. anything you can afford to wait on and let finish so you can start it from scratch next time reduces the complexity of the problem.

I suspect from your symptoms you have something that is being initialized to a constant and not from the file values.