Managing Restart Save Start and Stop

Question

In our project use of AEM3D we would like to generate a restart file at a particular point following a spinup period, and not overwrite that restart during the last few days of the simulation. We basically are looking to checkpoint the spinup to use for running experiments in the last days of the simulation.

We have considered using the start_output_restart control parameter as a way to begin restart saves at the end of the extended spinup. The intent was to minimize disk write during spinup for restart times we are not interested in.  When we try to specify the parameter it is getting flagged as not supported. We are using aem3d-1.1.2-535.

The start_output_restart parameter is described in the user manual. Has it been deprecated?

Regarding the desire to not overwrite a particular saved restart, according to the users guide there is no listed control for specifying that restart saves should not take place after a particular time step.

Is the only way to avoid overwriting a particular saved restart to set the iter_out_restart large enough that the desired restart save time step is the last time step that triggers a restart save?

Answer 1

What you want to use in this situation is the save files.  These are exactly the same file format as the restart files but the filenames are date stamped at the output timestep and so are not overwritten.  The lines 

 20000                                              start_output_save

  20000                                              iter_out_save

would write a fille at the 20000th timestep and every 20000 steps after that.

Comments

[email protected],

Revising this thread because after a few tests, I don't think it works exactly the way you describe.  My my testing, if I specify:

128        start_output_save
300        iter_out_save

I get save files at iteration 300, 600, 900, etc., not 128, 428, 728 as you indicated above.  Or... am I missing something?

So... this is a bit of a pain, because if I have, say 432 iterations per day (200 for del_t) I can't save on the even day (i.e. xxxxxx.0000) because those are at iteration 1, 433, 865, etc.  Instead, plugging in 432 for iter_out_save gives me saves just before x.0000 and then that can be a problem because I need a data point for the previous day when I restart.  It makes all the data prep logic more complex than it probably needs to be.

Long story short... is there a configuration that would create the save files at x + y * n where I can specify x and y and n is the sequence of integers [1...2...3... and so on]?

Thanks,
Pat

---

Hi, I've fixed this bug in the latest dev download.

---

Ah!  Great!  Thanks for the update!