Changeset 3122
- Timestamp:
- Jun 8, 2006, 5:12:17 PM (19 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
documentation/user_manual/anuga_user_manual.tex
r3121 r3122 173 173 174 174 To set up a particular scenario the user specifies the geometry 175 (bathymetry and topography), the initial water level (stage) 176 , 175 (bathymetry and topography), the initial water level (stage), 177 176 boundary conditions such as tide, and any forcing terms that may 178 177 drive the system such as wind stress or atmospheric pressure … … 245 244 246 245 247 %\emph{[More details of the problem background]}248 249 246 \subsection{Outline of the Program} 250 247 … … 293 290 \module{mesh\_factory} defined elsewhere. (\anuga also contains 294 291 several other schemes that can be used for setting up meshes, but we 295 shall not discuss these now.) The above assignment sets up a $10296 \times10$ rectangular mesh, triangulated in a regular way. The assignment292 shall not discuss these.) The above assignment sets up a $10 \times 293 10$ rectangular mesh, triangulated in a regular way. The assignment 297 294 298 295 {\small \begin{verbatim} … … 310 307 \item a dictionary \code{boundary} that stores the edges on 311 308 the boundary and associates each with one of the symbolic tags \code{`left'}, \code{`right'}, 312 \code{`top'} or \code{`bottom'}. (For more details on symbolic tags, 313 see page \pageref{ref:tagdescription}.) 309 \code{`top'} or \code{`bottom'}. 314 310 315 311 \end{itemize} 312 313 (For more details on symbolic tags, see page 314 \pageref{ref:tagdescription}.) 316 315 317 316 An example of a general unstructured mesh and the associated data … … 398 397 \subsubsection{Friction} 399 398 400 The assignment of the friction quantity (a forcing term) demonstrates another way we401 can use \method{set\_quantity} to set quantities---namely, assign 402 them to a constant numerical value:399 The assignment of the friction quantity (a forcing term) 400 demonstrates another way we can use \method{set\_quantity} to set 401 quantities---namely, assign them to a constant numerical value: 403 402 404 403 {\small \begin{verbatim} … … 414 413 elevation and the depth at any time by the equation 415 414 416 417 415 {\small \begin{verbatim} 418 416 stage = elevation + depth … … 430 428 i.e. 0.4 units (m) below the zero level. 431 429 432 %FIXME (Howard): Can we put this para somewhere else?433 430 Although it is not necessary for this example, it may be useful to 434 431 digress here and mention a variant to this requirement, which allows … … 584 581 The output is a NetCDF file with the extension \code{.sww}. It 585 582 contains stage and momentum information and can be used with the 586 \code{swollen} (see Section \ref{sec:swollen}) 587 visualisation package to generate a visual display. 588 See Section \ref{sec:file formats} (page \pageref{sec:file formats}) 589 for more on NetCDF and other file formats.583 \code{swollen} (see Section \ref{sec:swollen}) visualisation package 584 to generate a visual display. See Section \ref{sec:file formats} 585 (page \pageref{sec:file formats}) for more on NetCDF and other file 586 formats. 590 587 591 588 The following is a listing of the screen output seen by the user
Note: See TracChangeset
for help on using the changeset viewer.