Changeset 4875
- Timestamp:
- Dec 4, 2007, 5:21:38 PM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
anuga_core/documentation/user_manual/anuga_user_manual.tex
r4874 r4875 889 889 concepts introduced through the \file{runup.py} example and 890 890 introduces a second example, \file{runcairns.py}. This refers to 891 a real-life scenario, in which the domain of interest surrounds the 891 a {\bf hypothetical} scenario using real-life data, 892 in which the domain of interest surrounds the 892 893 Cairns region. Two scenarios are given; firstly, a 893 894 hypothetical tsunami wave is generated by a submarine mass failure 894 895 situated on the edge of the continental shelf, and secondly, a fixed wave 895 896 of given amplitude and period is introduced through the boundary. 897 898 {\bf 899 Each scenario has been designed to generate a tsunami which will 900 inundate the Cairns region. To achieve this, suitably large 901 parameters were chosen and were not based on any known tsunami sources 902 or realistic amplitudes. 903 } 896 904 897 905 \subsection{Overview} … … 1140 1148 width, thickness, slope, etc), its location (origin) and the depth at that 1141 1149 location. For this example, we choose to apply the slide function 1142 at a specified time into the simulation. 1150 at a specified time into the simulation. {\bf Note, the parameters used 1151 in this example have been deliberately chosen to generate a suitably 1152 large amplitude tsunami which would inundate the Cairns region.} 1143 1153 1144 1154 \subsubsection{Friction} … … 1268 1278 Figures \ref{fig:maxdepthcairnsslide} and \ref{fig:maxdepthcairnsfixedwave} show 1269 1279 the maximum water depth within the defined region for the slide and fixed wave scenario 1270 respectively. 1280 respectively. {\bf Note, these inundation maps have been based on purely hypothetical 1281 scenarios and were designed explicitly for demonstration purposes only.} 1271 1282 The user could develop a maximum absolute momentum or other expressions which can be 1272 1283 derived from the quantities. … … 1280 1291 \begin{figure}[hbt] 1281 1292 \centerline{\includegraphics[scale=0.5]{graphics/slidedepth.jpg}} 1282 \caption{Maximum inundation map for the Cairns slide scenario.} 1293 \caption{Maximum inundation map for the Cairns slide scenario. \bf Note, this 1294 inundaiton map has been based on a purely hypothetical scenario which was 1295 designed explictiy for demonstration purposes only.} 1283 1296 \label{fig:maxdepthcairnsslide} 1284 1297 \end{figure} … … 1286 1299 \begin{figure}[hbt] 1287 1300 \centerline{\includegraphics[scale=0.5]{graphics/fixedwavedepth.jpg}} 1288 \caption{Maximum inundation map for the Cairns fixed wave scenario.} 1301 \caption{Maximum inundation map for the Cairns fixed wave scenario. 1302 \bf Note, this 1303 inundaiton map has been based on a purely hypothetical scenario which was 1304 designed explictiy for demonstration purposes only.} 1289 1305 \label{fig:maxdepthcairnsfixedwave} 1290 1306 \end{figure} … … 1325 1341 Figure \ref{fig:reef} shows the time series for the quantity stage for the 1326 1342 Elford Reef location for each scenario (the elevation at this location is negative, 1327 thereby showing stage). 1343 thereby showing stage). Note the large negative stage value when the slide was 1344 introduced. This is due to the double gaussian form of the initial surface 1345 displacement of the slide. By contrast, the time series for depth is shown for the onshore location of the Cairns 1346 Airport for each scenario is Figure \ref{fig:airportboth}. 1328 1347 1329 1348 \begin{figure}[hbt] … … 1333 1352 \label{fig:reef} 1334 1353 \end{figure} 1335 1336 By contrast, the time series for depth is shown for the onshore location of the Cairns1337 Airport for each scenario is Figure \ref{fig:airportboth}.1338 1354 1339 1355 \begin{figure}[hbt] … … 4026 4042 4027 4043 This technique can be expanded to handle point data sets as well. In the case 4028 of a bathymetry data set available in text format in an \code{. xya} file, then4044 of a bathymetry data set available in text format in an \code{.csv} file, then 4029 4045 the geospatial addition is updated to 4030 4046 {\small \begin{verbatim} 4031 G3 = Geospatial_data(file_name = bathy_data_name + '. xya')4047 G3 = Geospatial_data(file_name = bathy_data_name + '.csv') 4032 4048 G = G1 + G2.clip_outside(Geospatial_data(poly1)) + G3 4033 4049 \end{verbatim}} 4034 The \code{. xya} file has the data stored as \code{x,y,elevation} with the text \code{elevation}4050 The \code{.csv} file has the data stored as \code{x,y,elevation} with the text \code{elevation} 4035 4051 on the first line. 4036 4052
Note: See TracChangeset
for help on using the changeset viewer.