Changeset 4673

Timestamp:

Aug 21, 2007, 6:11:32 PM (18 years ago)

Author:

ole

Message:

Updates from Ted Rigby and Rudy van Drie

Location:

anuga_core/documentation/user_manual

Files:

• anuga_user_manual.tex (modified) (6 diffs)
• demos/channel3.py (modified) (1 diff)

anuga_core/documentation/user_manual/anuga_user_manual.tex

@@ -181 +181 @@
 terrains in the model are represented by predefined forcing terms.
 
-The built-in mesh generator %, called pmesh,
+The built-in mesh generator, called \code{graphical\_mesh\_generator},
 allows the user to set up the geometry
 of the problem interactively and to identify boundary segments and
@@ -564 +564 @@
 to an edge depending on which part of the boundary it belongs to.
 (In Section \ref{sec:realdataexample} we describe an example that
-uses different boundary tags---in general, the possible tags are not
-limited to `left', `right', `top' and `bottom', but can be specified
-by the user.)
+uses different boundary tags --- in general, the possible tags are entirely selectable by the user when generating the mesh and not
+limited to `left', `right', `top' and `bottom' as in this example.)
+All segments in bounding polygon must be tagged. If a tag is not supplied, the default tag name 'exterior' will be assigned by ANUGA.
+
 
 Using the boundary objects described above, we assign a boundary
@@ -575 +576 @@
 \end{verbatim}}
 
-This statement stipulates that, in the current example, the right
+It is critical that all tags are assoctiated with a boundary conditing in this statement. If not the program will halt with a statement like
+
+\begin{verbatim}
+
+Traceback (most recent call last):
+  File "mesh_test.py", line 114, in ?
+    domain.set_boundary({'west': Bi, 'east': Bo, 'north': Br, 'south': Br})
+  File "X:\inundation\sandpits\onielsen\anuga_core\source\anuga\abstract_2d_finite_volumes\domain.py", line 505, in set_boundary
+    raise msg
+ERROR (domain.py): Tag "exterior" has not been bound to a boundary object.
+All boundary tags defined in domain must appear in the supplied dictionary.
+The tags are: ['ocean', 'east', 'north', 'exterior', 'south']
+\end{verbatim} 
+
+
+The command \code{set\_boundary} stipulates that, in the current example, the right
 boundary varies with time, as defined by the lambda function, while the other
 boundaries are all reflective.
@@ -1045 +1061 @@
 segments associated with each of these tags. (The value associated
 with each boundary tag is a one-element list.)
+If polygons intersect, or edges coincide the resolution may be undefined in some regions.
+Use the underlying mesh interface for such cases. See Section \ref{sec:mesh_interface}.
 
 
@@ -1355 +1373 @@
     \code{pmesh}$\slash$\code{mesh\_interface.py}
 \end{center}
+\label{sec:mesh_interface}
 
 while in Windows syntax it would be
@@ -3531 +3550 @@
 
 \section{pmesh GUI}
- \emph{Pmesh}
+The program \code{graphical\_mesh\_generator.py} in the pmesh module 
 allows the user to set up the mesh of the problem interactively.
 It can be used to build the outline of a mesh or to visualise a mesh

anuga_core/documentation/user_manual/demos/channel3.py

@@ -19 +19 @@
 length = 40.
 width = 5.
-dx = dy = 1           # Resolution: Length of subdivisions on both axes
-#dx = dy = .1           # Resolution: Length of subdivisions on both axes
+#dx = dy = 1           # Resolution: Length of subdivisions on both axes
+dx = dy = .1           # Resolution: Length of subdivisions on both axes
 
 points, vertices, boundary = rectangular_cross(int(length/dx), int(width/dy),