Ticket #18 (closed enhancement: fixed)

Opened 12 years ago

Last modified 7 years ago


Reported by: ole Owned by: nariman
Priority: normal Milestone: AnuGA ready for release
Component: Efficiency and optimisation Version:
Severity: normal Keywords:


Checkpointing (largely done in inundation/pyvolution/data_manager.py but needs to be revisited and properly tested)

Change History

Changed 11 years ago by ole

  • component changed from Compilation and installation to Efficiency and optimisation

Changed 11 years ago by anonymous

from another ticket;

Description by Nick <nick.bartzis@…>: Store all values of all varibles every 12-24 hours to disk and develop some code to run from this point.

This will prevent having to rerun the whole model if the node crashes

Changed 9 years ago by ole

Rudy asked for this functionality 4 Dec 2007.

Changed 8 years ago by ole

With flood models taking more than 4 weeks to complete, we really need this now. Looking at changeset:288 may be helpful and also the function sww2domain in data_manager.py. However, here's how I think it should work: Have a function

domain = restart_from_checkpoint()

which will restore stage, xmomentum, ymomentum, elevation, perhaps friction as well as mesh, time, starttime, name, georeference. The script must then redefine forcing terms and boundary conditions typically exactly as the original script did.

I imagine the function could take an sww file as input and use that. However, data is stored in single precision and friction is currently not stored. Alternatively, if no sww file is specified the function should look for a checkpoint file with same format as sww but with data stored in double precision and only the last few timesteps present.

Issues include what to do with parallel jobs.

Changed 8 years ago by ole

  • priority changed from low to high

Changed 8 years ago by ole

Or perhaps name the function create_domain_from_checkpoint. A script could then look like this:


domain = create_domain_from_checkpoint()


domain = create_domain_from_regions(...) domain.set_quantity('elevation', ...) etc...

Do boundary conditions and forcing terms.

This could later become automatic in the generic ANUGA interface (see ticket:308)

Moreover, I think we should concentrate on a specific (NetCDF) format for checkpoint files containing quantities at the latest yieldstep including friction. This could also include the parallel communication lookup table. Otherwise, the format would reuse some of the sww code except it would use double precision.

Finally, I suggest that for each stored checkpoint file (domain.cpt) the previous one is kept just in case the latest file got corrupted. The name could be domain.backup.cpt.

Changed 8 years ago by nariman

  • priority changed from high to normal

Changed 8 years ago by ole

  • owner changed from ole to nariman

Changed 7 years ago by hudson

  • status changed from new to closed
  • resolution set to fixed

Instructions for doing this are now on the ANUGA wiki.

Note: See TracTickets for help on using tickets.