Changeset 2357
- Timestamp:
- Feb 8, 2006, 3:41:01 PM (19 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
documentation/AnuGA_user_manual.tex
r2356 r2357 459 459 460 460 \begin{itemize} 461 \item{from a Windows command line} as in \ texttt{python bedslope.py}461 \item{from a Windows command line} as in \code{python bedslope.py} 462 462 463 463 \item{within the Python IDLE environment} … … 465 465 \item{within emacs} 466 466 467 \item{from a Linux command line} as in \ texttt{python bedslope.py}467 \item{from a Linux command line} as in \code{python bedslope.py} 468 468 \end{itemize} 469 469 470 470 471 471 \section{Example with real data} 472 473 The following discussion builds on the \code{bedslope.py} example and shows 474 how, using the same basic outline, we can incorporate many more complex features. 475 476 The chief difference is in the method used to create the mesh. Instead of imposing a mesh 477 structure on a rectangular grid, the technique used for this example involves building 478 mesh structures inside polygons. 479 480 In its simplest form, the mesh is created within a 481 single polygon whose vertices are at geographical locations specified by the user. 482 A triangular mesh is created using points inside the polygon selected 483 through a random process, the 484 user specifying the \emph{resolution}---that is, the maximal area of a triangle used for triangulation. 485 486 Figure XXX shows a simple example, in which the triangulation is carried out within a 487 pentagon. Instead of using the four tags \texttt{`left'}, \texttt{`right'}, \texttt{`bottom'} and 488 \texttt{`top'} to distinguish 489 boundary elements, the user can define tags appropriate to the configuration being modelled. 490 491 While this offers more flexibility than the rectangular grid, it doesn't provide a way to 492 adapt to geographic 493 or other features in the landscape, for which we may require to vary the resolution. We achieve 494 more flexibility by extending this method, allowing the user to specify a number of 495 interior polygons which are triangulated separately, possibly using different resolutions. 496 See Figure XXX. 472 497 473 498 \appendix
Note: See TracChangeset
for help on using the changeset viewer.