Changeset 6371


Ignore:
Timestamp:
Feb 20, 2009, 8:42:19 AM (15 years ago)
Author:
ole
Message:

Comments about discontinuities in manual

File:
1 edited

Legend:

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

    r6180 r6371  
    1 vi% Complete documentation on the extended LaTeX markup used for Python
     1% Complete documentation on the extended LaTeX markup used for Python
    22% documentation is available in ``Documenting Python'', which is part
    33% of the standard documentation for Python.  It may be found online
     
    146146inundation software, describe what it can do and give step-by-step
    147147instructions for setting up and running hydrodynamic simulations.
     148The stable release of \anuga and this manual are available on sourceforge at \url{http://sourceforge.net/projects/anuga}. A snapshot of work in progress is available through the \anuga software repository at \url{https://datamining.anu.edu.au/svn/ga/anuga_core} where the more adventurous reader might like to go.
     149
    148150
    149151\section{Scope}
     
    195197and around structures such as buildings.  \anuga is also capable
    196198of modelling hydraulic jumps due to the ability of the finite-volume
    197 method to accommodate discontinuities in the solution.
     199method to accommodate discontinuities in the solution/footnote{While \anuga works with discontinuities in the conserved quantities stage, xmomentum and ymomentum, it does not allow discontinuities in the bed elevation}.
    198200
    199201To set up a particular scenario the user specifies the geometry
     
    18731875Triangles stored in the sww file can be discontinuous reflecting
    18741876the internal representation of the finite-volume scheme
    1875 (this is a feature allowing for arbitrary steepness).
     1877(this is a feature allowing for arbitrary steepness of the water surface gradient as well as the momentum gradients).
    18761878However, for visual purposes and also for use with \code{Field\_boundary}
    18771879(and \code{File\_boundary}) it is often desirable to store triangles
Note: See TracChangeset for help on using the changeset viewer.