Discuss case sensitivity of parameter tables.

Clarify wave speed argument to radiation bcs.


git-svn-id: http://svn.cactuscode.org/arrangements/CactusBase/Boundary/trunk@212 6a38eb6e-646e-4a02-a296-d141613ad6c4

1 files changed, 8 insertions, 2 deletions

diff --git a/doc/documentation.tex b/doc/documentation.tex
index 58260b6..cc34f5a 100644
--- a/doc/documentation.tex
+++ b/doc/documentation.tex
@@ -209,7 +209,13 @@ boundary condition, when it is called within the
 \ref{schedule_groups}), will return an error code.  However, in most
 cases it is optional.  If one uses an invalid table handle here (such
 as -1), commonly used default values will be assumed for all arguments
-(besides the explicit faces specification).
+(besides the explicit faces specification).  Note that you, the user,
+will be creating the table, so you may choose whatever options (such
+as case sensitivity) you like.  The case of the keys for which the
+boundary conditions implemented in this thorn search are as given in the
+documentation, which is currently all capitals.  To be safe you may
+choose to create case-insensitive tables, however cases sensitive
+tables are slightly faster.
 
 The name of the boundary condition must match that with which the
 boundary condition providing function was registered.  These names are
@@ -623,7 +629,7 @@ LIMIT & CCTK\_REAL & $f_0$ & 0.0\\
 STENCIL WIDTH & CCTK\_INT array & stencil widths & 1 in all directions\\
 PREVIOUS TIME LEVEL & CCTK\_INT or CCTK\_STRING & GV which holds the & Cactus previous time level\\
 && previous time level&\\
-SPEED & CCTK\_REAL & wave speed & 1.0\\
+SPEED & CCTK\_REAL & wave speed $v$& 1.0\\
 \hline
 \end{tabular}
 \\[1mm] The default behavior is to use the Cactus previous time level,