From 1e7e463799b40f3a8269cb74fd180ea64e50d487 Mon Sep 17 00:00:00 2001 From: swhite Date: Wed, 29 Mar 2006 10:41:32 +0000 Subject: Corrected information about time bins required to implement checkpointing. made CVS to ignore Latex .out files git-svn-id: http://svn.cactuscode.org/flesh/trunk@4275 17b73243-c579-4c4c-a9d2-2d5706c11dac --- doc/UsersGuide/Infrastructure.tex | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) (limited to 'doc') diff --git a/doc/UsersGuide/Infrastructure.tex b/doc/UsersGuide/Infrastructure.tex index 362b8480..d0c278c2 100644 --- a/doc/UsersGuide/Infrastructure.tex +++ b/doc/UsersGuide/Infrastructure.tex @@ -521,14 +521,17 @@ by thorns. The Flesh only provides specific time bins at which the scheduler will call thorns' routines in order to perform checkpointing and/or recovery. This chapter explains how to implement checkpointing and recovery methods -in your thorn. +in your thorn. For further information, see the documentation for thorn +\texttt{CactusBase/IOUtil}. \section{Checkpointing Invocation} Thorns register their checkpointing routines at {\t CCTK\_CPINITIAL} and/or -{\t CCTK\_CHECKPOINT}. These time bins are scheduled right after all initial -data has been set up and after every evolution timestep, respectively. (See -\ref{subsec:schedule_ccl} for a description of all timebins). Depending on +{\t CCTK\_CHECKPOINT} and/or {\t CCTK\_TERMINATE}. These time bins are +scheduled right after all initial data has been set up, after every +evolution timestep, and after the last time step of a simulation, +respectively. (See \ref{subsec:schedule_ccl} for a description of all timebins). +Depending on parameter settings, the checkpoint routines decide whether to write an initial data checkpoint, and when to write an evolution checkpoint. -- cgit v1.2.3