Ignore:
Timestamp:
Aug 21, 2007, 6:11:32 PM (17 years ago)
Author:
ole
Message:

Updates from Ted Rigby and Rudy van Drie

File:
1 edited

Legend:

Unmodified
Added
Removed
  • anuga_core/documentation/user_manual/anuga_user_manual.tex

    r4662 r4673  
    181181terrains in the model are represented by predefined forcing terms.
    182182
    183 The built-in mesh generator %, called pmesh,
     183The built-in mesh generator, called \code{graphical\_mesh\_generator},
    184184allows the user to set up the geometry
    185185of the problem interactively and to identify boundary segments and
     
    564564to an edge depending on which part of the boundary it belongs to.
    565565(In Section \ref{sec:realdataexample} we describe an example that
    566 uses different boundary tags---in general, the possible tags are not
    567 limited to `left', `right', `top' and `bottom', but can be specified
    568 by the user.)
     566uses different boundary tags --- in general, the possible tags are entirely selectable by the user when generating the mesh and not
     567limited to `left', `right', `top' and `bottom' as in this example.)
     568All segments in bounding polygon must be tagged. If a tag is not supplied, the default tag name 'exterior' will be assigned by ANUGA.
     569
    569570
    570571Using the boundary objects described above, we assign a boundary
     
    575576\end{verbatim}}
    576577
    577 This statement stipulates that, in the current example, the right
     578It is critical that all tags are assoctiated with a boundary conditing in this statement. If not the program will halt with a statement like
     579
     580\begin{verbatim}
     581
     582Traceback (most recent call last):
     583  File "mesh_test.py", line 114, in ?
     584    domain.set_boundary({'west': Bi, 'east': Bo, 'north': Br, 'south': Br})
     585  File "X:\inundation\sandpits\onielsen\anuga_core\source\anuga\abstract_2d_finite_volumes\domain.py", line 505, in set_boundary
     586    raise msg
     587ERROR (domain.py): Tag "exterior" has not been bound to a boundary object.
     588All boundary tags defined in domain must appear in the supplied dictionary.
     589The tags are: ['ocean', 'east', 'north', 'exterior', 'south']
     590\end{verbatim}
     591
     592
     593The command \code{set\_boundary} stipulates that, in the current example, the right
    578594boundary varies with time, as defined by the lambda function, while the other
    579595boundaries are all reflective.
     
    10451061segments associated with each of these tags. (The value associated
    10461062with each boundary tag is a one-element list.)
     1063If polygons intersect, or edges coincide the resolution may be undefined in some regions.
     1064Use the underlying mesh interface for such cases. See Section \ref{sec:mesh_interface}.
    10471065
    10481066
     
    13551373    \code{pmesh}$\slash$\code{mesh\_interface.py}
    13561374\end{center}
     1375\label{sec:mesh_interface}
    13571376
    13581377while in Windows syntax it would be
     
    35313550
    35323551\section{pmesh GUI}
    3533  \emph{Pmesh}
     3552The program \code{graphical\_mesh\_generator.py} in the pmesh module
    35343553allows the user to set up the mesh of the problem interactively.
    35353554It can be used to build the outline of a mesh or to visualise a mesh
Note: See TracChangeset for help on using the changeset viewer.