pictures for staggering

git-svn-id: http://svn.cactuscode.org/flesh/trunk@1362 17b73243-c579-4c4c-a9d2-2d5706c11dac

1 files changed, 23 insertions, 5 deletions

diff --git a/doc/UsersGuide/ThornWriters.tex b/doc/UsersGuide/ThornWriters.tex
index a48d03e1..41255df9 100644
--- a/doc/UsersGuide/ThornWriters.tex
+++ b/doc/UsersGuide/ThornWriters.tex
@@ -1047,11 +1047,20 @@ staggering each direction ({\tt stagger=CC}) is shown in (C). The full
 staggering in (D) ({\tt stagger=PP}) obeyes the same rules, but is
 rather unusual; included here for completeness. 
 
-\vskip .25cm
+\begin{figure}[h]
+  \def\epsfsize#1#2{0.45#1}
+  \centerline{\epsfbox{./staggering1.eps}}
+\caption[]{\small {\bf Staggered gridpoints in 2D} for several
+staggerings. (a) : {\tt MC}, (b): {\tt CM}, (c): {\tt CC}, (d): {\tt
+PP}. Note that the staggering of gridfunctions does change its
+index. The staggered gridpoints and the corresponding unstaggered
+points (arrows) are accessed by the same indeces.} 
+\label{fig:stagger2}
+\end{figure}
 
 {\bf Indexing, ghostzones, etc.}
 Note that staggering does not make any changes to the indexing of a
-gridfunction: the black solid circles in diagramm XX and their
+gridfunction: the black solid circles in diagramm \ref{fig:stagger2} and their
 associated staggered gridfunctions (connected by arrows) have the same index!
 
 Since the gridfunction does not ``know'' anything about the physical
@@ -1062,15 +1071,13 @@ Indeed, you could roll your own, but there compelling reasons:
 Readabilty and you are able to query the staggertype of a
 gridfunction. More important: in the way the grid is laid out, there is one grid
 point {\em less} for {\tt M} and {\tt P} staggered grid functions. This is
-illustrated in picture YY, which shows 15 gridpoints distributed
+illustrated in picture \ref{fig:stagger2}, which shows 15 gridpoints distributed
 across 3 processors. The solid black cirlces show the default
 location of the gridfunctions, the grey circles depict the ghostzones.
 Note that the number of center staggered gridpoints (fat crosses)
 corresponds to the number of default gridpoint on all processors but
 the last one. (Same is true for full staggered gridpoints).
 
-\vskip .25cm
-
 {\bf Staggertypes}
 The string specifying the staggering is encoded in a number called
 the {\em staggerindex}. With the 3 supported staggerings, the string
@@ -1091,6 +1098,17 @@ x-direction: {\em directional staggerindex} = CCTK\_STAGGER\_C (value 1).
 \end{Lentry}
 
 
+\begin{figure}[h]
+  \def\epsfsize#1#2{0.45#1}
+  \centerline{\epsfbox{./staggering2.eps}}
+\caption[]{\small {\bf Unstaggered and center-staggered gridpoints} with
+ghostzone size of one (above) and two (below). The points are
+distributed across three processors. Note that the number of  
+center staggered gridpoints (fat crosses) is one less on the outermost grid. How to
+treat this case in a easy way is explained below. }
+\label{fig:stagger2}
+\end{figure}
+
 When a thorn programmer uses staggered gridpoints, he has to be aware
 of this gridpoint anomaly. This can be done easiest by using the {\tt
 CCTL\_LSSH(<dir\_staggertype>,<direction>)} macro. For a given staggertype