Hi all, This is a bit off-topic, but i would like to ask how do you prefer to implement restart/checkpoints in your user applications? I see two options:
1. Make restarting usable with the same input parameter file so that calculations will continue exactly from the point of restart. For example, if you wanted to do 10 adaptive refinements and one node failed on 6th step, you would use exactly the same input parameter file to automatically continue from the 5th step if the application see that restart information is available. 2. Another approach is to consider restarts as an arbitrary input (similar to the input mesh / initial conditions and alike). With the same example in mind, if one uses the same input parameter file with 10 refinement steps but specify `Restart = true` and thereby use the restart generated from 5th step, then the program would actually end up doing 10 refinement steps starting from the input data taken from the restart. In other words, 15 steps in total. Maybe ASPECT (Timo, Wolfagng?), pi-DoMUS ( Luca?) or DOpElib developers could comment on which restart strategy you have chosen for your libraries and why? Regards, Denis. -- The deal.II project is located at http://www.dealii.org/ For mailing list/forum options, see https://groups.google.com/d/forum/dealii?hl=en --- You received this message because you are subscribed to the Google Groups "deal.II User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
