Changeset 2780
- Timestamp:
- Apr 28, 2006, 3:37:51 PM (19 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
documentation/user_manual/anuga_user_manual.tex
r2779 r2780 1504 1504 1505 1505 1506 \subsection{Basic file conversions} 1506 1507 1508 \bigskip 1509 1510 \subsection{SWW and TMS Formats} 1511 1512 The SWW and TMS formats are both NetCDF formats, and are of key 1513 importance for \anuga. 1514 1515 An SWW file is used for storing \anuga output. 1516 1517 The contents of an SWW file may be viewed using the visualisation 1518 tool \code{swollen}, which creates an on-screen geometric 1519 representation. See section \ref{sec:swollen} (page 1520 \pageref{sec:swollen}) in Appendix \ref{ch:supportingtools} for more 1521 on \code{swollen}. 1522 1523 Alternatively, there are tools, such as \code{ncdump}, that allow 1524 you to convert an NetCDF file into a readable format such as the 1525 Class Definition Language (CDL). The following is an excerpt from a 1526 CDL representation of the output file \file{bedslope.sww} generated 1527 from running the simple example \filename{bedslopephysical.py}. 1528 1529 \verbatiminput{examples/bedslopeexcerpt.cdl} 1530 1531 The data stored in an SWW file pertains to a specific set of points 1532 and timesteps and comprises the following: 1533 1534 \begin{enumerate} 1535 \item Dimension information, stored as a number of constants. 1536 \item Variables \code{x} and \code{y}, storing coordinates of 1537 the points, represented as Numeric arrays. 1538 \item A variable \code{elevation}, storing bed-elevations at the 1539 points, also as a Numeric array. 1540 \item A variable \code{volumes} 1541 \item A variable \code{time}, 1542 \end{enumerate} 1543 1544 1545 1546 \subsection{Meshfile Formats} 1547 1548 A meshfile is a file that has a specific format suited to data used 1549 to specify a mesh suitable for use with \anuga. A meshfile can have 1550 one of two formats: it can be either a TSH file, which is an ASCII 1551 file, or an MSH file, which is a NetCDF file. 1552 1553 A meshfile describes the outline of the mesh---the vertices and line 1554 segments that enclose the region in which the mesh is created---and 1555 the triangular mesh itself, which is specified by listing the 1556 triangles and their vertices, and the segments, which are those 1557 sides of the triangles that are associated with boundary conditions. 1558 1559 In addition, a meshfile may contain `holes' and/or `regions'. A hole 1560 or region is defined by specifying a point and a number of segments 1561 that enclose the point. A hole represents an area where no mesh is 1562 to be created, while a region is a labelled area used for defining 1563 properties of a mesh, such as friction values. 1564 1565 A meshfile can also contain a georeference, which describes an 1566 offset to be applied to $x$ and $y$ values---eg to the vertices. 1567 1568 1569 \subsection{Formats for Storing Arbitrary Points and Attributes} 1570 1571 1572 \subsection{ArcView Formats} 1573 1574 1575 \subsection{Other Formats} 1576 1577 \subsection{Basic File Conversions} 1507 1578 1508 1579 \begin{funcdesc}{sww2dem}{basename_in, basename_out = None, … … 1523 1594 Module: \module{pyvolution.data\_manager} 1524 1595 1525 1596 Takes data from an SWW file and converts it to DEM format (ASC or 1597 ERS) 1526 1598 \end{funcdesc} 1527 1599 … … 1533 1605 Module: \module{pyvolution.data\_manager} 1534 1606 1535 1607 Takes DEM data (a NetCDF file representation of data from a regular Digital 1608 Elevation Model) and converts it to PTS format. 1536 1609 \end{funcdesc} 1537 1610 1538 \bigskip1539 1540 \subsection{SWW and TMS Formats}1541 1542 The SWW and TMS formats are both NetCDF formats, and are of key1543 importance for \anuga.1544 1545 The output from \anuga is stored in an SWW file. The contents may be1546 viewed using the visualisation tool \code{swollen}, which creates an1547 on-screen geometric representation. See section \ref{sec:swollen}1548 (page \pageref{sec:swollen}) in Appendix \ref{ch:supporting_tools}1549 for more on \code{swollen}.1550 1551 Alternatively, there are tools, such as \code{ncdump}, that allow1552 you to convert an NetCDF file into a readable format such as the1553 Class Definition Language (CDL). The following is an excerpt from a1554 CDL representation of the output file \file{bedslope.sww} generated1555 from running the simple example \filename{bedslopephysical.py}.1556 1557 \verbatiminput{examples/bedslopeexcerpt.cdl}1558 1559 1560 1561 \subsection{Meshfile Formats}1562 1563 A meshfile is a file of a specific format used for holding data that1564 specifies a mesh suitable for use with \anuga. A meshfile can have1565 one of two formats: it can be either a TSH file, which is an ASCII1566 file, or an MSH file, which is a NetCDF file.1567 1568 A meshfile describes the outline of the mesh---the vertices and line1569 segments that enclose the region in which the mesh is created---and1570 the triangular mesh itself, which is specified by listing the1571 triangles and their vertices, and the segments, which are those1572 sides of the triangles that are associated with boundary conditions.1573 1574 In addition, a meshfile may contain `holes' and/or `regions'. A hole1575 or region is defined by specifying a point and a number of segments1576 that enclose the point. A hole represents an area where no mesh is1577 to be created, while a region is a labelled area used for defining1578 properties of a mesh, such as friction values.1579 1580 A meshfile can also contain a georeference, which describes the1581 offset of the x,y values eg, the offset of the vertices.1582 1583 1584 \subsection{}1585 1611 1586 1612 … … 1649 1675 1650 1676 \chapter{Supporting Tools} 1651 \label{ch:supporting _tools}1677 \label{ch:supportingtools} 1652 1678 1653 1679 This section describes a number of supporting tools, supplied with \anuga, that offer a
Note: See TracChangeset
for help on using the changeset viewer.