Index: /DVD_images/extra_files/BatemansBay/installation.html
===================================================================
--- /DVD_images/extra_files/BatemansBay/installation.html	(revision 7301)
+++ /DVD_images/extra_files/BatemansBay/installation.html	(revision 7301)
@@ -0,0 +1,148 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+  <title>Geoscience Australia</title>
+  <link rel="stylesheet" href="browser_files/style.css">
+  <link REL="SHORTCUT ICON" HREF="browser_files/favicon.ico">
+</head>
+<body>
+  <table cellspacing="10" border="0">
+    <tr>
+      <td>
+        <img src="browser_files/logo.jpg" alt="Australian Government, Geoscience Australia" width="327" height="80" border="0"/>
+      </td>
+      <td width="50">
+        &nbsp;
+      </td>
+      <td>
+        <H1>Tsunami Inundation Models for the BATEMANS BAY region</H1>
+      </td>
+    </tr>
+  </table>
+  <hr>
+
+  <a name="introduction"><h2><b>Installing, Running and Changing the Simulation</b></h2></a>
+
+  This document describes the installation and running of the simulation software.
+  <p>
+  In addition, we show how to change your simulation, add new elevation data, etc, and how to get help if you have trouble.
+
+  <a name="requirements"><h3><b>Requirements</b></h3></a>
+
+  The tsunami inundation simulations are based on the Open Source software package called ANUGA.
+  For more information about ANUGA visit <a href="https://datamining.anu.edu.au/anuga">https://datamining.anu.edu.au/anuga</a>. 
+  <p>
+  ANUGA has been developed and tested under the Windows XP and Linux (Ubuntu, Mint and Red Hat) operating systems.  
+  ANUGA may also be installed on a Windows Vista system and Debian Linux, but these have not been extensively tested.
+  <p>
+  The ANUGA scripts on this DVD require a minimum of 3GB of memory and possibly more, if mesh resolutions are increased. For this reason
+  we recommend using 64 bit Ubuntu Linux as this operating system can use more than 3GB of memory, whereas Windows XP cannot.
+
+  <a name="installing"><h3><b>Installing ANUGA</b></h3></a>
+
+  You must install ANUGA according to the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
+  As the installation procedure comprises a number of steps we suggest that it is carried out by someone with a
+  basic understanding of how to install software packages on the operating system of choice. 
+
+  <a name="simulating"><h3><b>How to run a simulation</b></h3></a>
+
+  This is how you should run the model on this DVD.
+  We assume that you are using Windows and will give examples for that operating system.
+  The translation to Linux should be obvious, but the <a href="#userslist">ANUGA user's mailing list</a>
+  can be used to get help.
+  <p>
+  
+  <p>
+  <hr align="left" width="100">
+  <p>
+  First, it is assumed you have installed the ANUGA software according to the
+  <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
+  <p>
+  <hr align="left" width="100">
+  <p>
+  Next, you must copy the entire contents of the DVD to a place in your filesystem. Let's assume
+  that you want to put the data into <b>C:\ANUGA</b>. You would do this in a Command Prompt window:
+  <table class="code"><tr><td>
+    C:<br>
+    cd \<br>
+    mkdir ANUGA<br>
+    xcopy /e X:\ ANUGA
+  </td></tr></table>
+  <p>
+  Of course, you could just drag all files on the DVD (X:\ is the assumed drive letter) to the desired target directory with Explorer.
+  <p>
+  <hr align="left" width="100">
+  <p>
+  Now you must create an environment variable <b>ANUGADATA</b> that points to the directory you just created:
+  <table class="code"><tr><td>
+    set ANUGADATA=C:\ANUGA
+  </td></tr></table>
+  <p>
+  Doing the above in a Command Prompt window is temporary - if you open another
+  window you will not have the ANUGADATA environment variable defined. To make
+  the variable permanent you must set it in the <b>Start|Settings|Control Panel|System</b>
+  tool (<b>Advanced</b> tab).  See the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>
+  if you don't know how to do this.
+  <p>
+  <hr align="left" width="100">
+  <p>
+  Next, you prepare and execute the model:
+  <table class="code"><tr><td>
+    cd C:\ANUGA<br>
+    cd project<br>
+    python setup_model.py<br >
+    python run_model.py
+  </td></tr></table>
+  <p>
+  <hr align="left" width="100">
+  <p>
+  This should all run to completion though it may take several days, depending on
+  the hardware used.
+  <p>
+  If you get an error from <font color="red">setup_model.py</font>
+  or <font color="red">run_model.py</font> look for some explanation in the log
+  files, which you will find under <b>C:\ANUGA\data</b>. Just keep
+  drilling down from that point until you find a directory called <b>outputs</b>.
+  The latest directory in <b>outputs</b> should contain a file called <font color="red">screen_error.txt</font>
+  with an explanation of the error at the end. 
+  <p>
+  Once the simulation has completed you may view the results using the ANUGA
+  viewer as described in the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a> 
+  and <a href="documents/anuga_user_manual.pdf">User Manual</a>.  You may also
+  generate rasters suitable for GIS mapping or write dedicated scripts extracting timeseries at selected
+  locations.  Some hints to help you do this are at the <a href="analysis.html">analysis page</a>.
+  <p>
+  The ANUGA <a href="documents/anuga_user_manual.pdf">User Manual</a> describes
+  how to use the ANUGA system in general and provides some examples of its use.
+
+  <a name="auxscripts"><h3><b>How to extract data from the simulation output files</b></h3></a>
+
+  After you have run a simulation you may wish to extract information from the generated SWW file.
+  On this disk there are a selection of example analysis scripts that you can use or modify.
+  The <a href="analysis.html">analysis scripts</a> page explains how to use the scripts.
+
+  <a name="modifications"><h3><b>How to modify a simulation</b></h3></a>
+
+  After you have run the supplied simulation you may wish to change it in some way, such as adding improved bathymetry data, for example.
+  The <a href="modifications.html">modifications</a> page explains how to do this.
+
+  <a name="userslist"><h3><b>How to join the ANUGA user's mailing list</b></h3></a>
+
+  One of the quickest ways to get your ANUGA questions answered is by asking them on the <b>ANUGA-user</b> mailing list.
+  You can <a href="https://lists.sourceforge.net/lists/listinfo/anuga-user">subscribe to the list</a>
+  and can view the mailing list <a href="https://sourceforge.net/mailarchive/forum.php?forum_name=anuga-user">archives</a>.
+  <p>
+  It costs nothing to register and you can choose to have list mail sent to you as individual emails or have them batched
+  into a few emails per day.  You can unsubscribe at any time through the subscribe link above.
+
+  <a name="FAQ"><h3><b>Frequently Asked Questions</b></h3></a>
+
+  There is a <b>Frequently Asked Questions</b> (FAQ) page at
+  <a href="https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions">https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions</a>.
+  Look in there and search the mailing list archives before asking questions on the ANUGA user's mailing list.
+  Someone may already have asked your question!
+  <p>
+  Note that you can edit the FAQ pages, so it is helpful if you can update the FAQ with your question and its answer if you feel
+  it would be helpful to others.
+</body>
+</html>
Index: /DVD_images/extra_files/GoldCoast/analysis.html
===================================================================
--- /DVD_images/extra_files/GoldCoast/analysis.html	(revision 7301)
+++ /DVD_images/extra_files/GoldCoast/analysis.html	(revision 7301)
@@ -0,0 +1,121 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+  <title>Geoscience Australia</title>
+  <link rel="stylesheet" href="browser_files/style.css">
+  <link REL="SHORTCUT ICON" HREF="browser_files/favicon.ico">
+</head>
+<body>
+  <table cellspacing="10" border="0">
+    <tr>
+      <td>
+        <img src="browser_files/logo.jpg" alt="Australian Government, Geoscience Australia" width="327" height="80" border="0"/>
+      </td>
+      <td width="50">
+        &nbsp;
+      </td>
+      <td>
+        <H1>Tsunami Inundation Models for the GOLD COAST region</H1>
+      </td>
+    </tr>
+  </table>
+  <hr>
+
+  <a name="analysis scripts"><h2><b>Analysis Scripts</b></h2></a>
+  There are number of analysis scripts on this disk that you can use to extract information from the SWW files
+  produced by a simulation run.  These scripts are not meant to be the definitive answer on how to get information
+  from SWW files, but are offered as an example of one way to do it.
+  <p>
+  This page describes the scripts and shows how to use them.  Note that due to the ad-hoc nature of the scripts, 
+  you <b>must</b> modify these scripts before they can be used to extract information from any SWW files you
+  generate.
+
+  <a name="export_results_max.py scripts"><h3><b>export_results_max.py</b></h3></a>
+  The <font color="red">export_results_max.py</font> script can be used to create an ASC file that contains the maximum
+  of an ANUGA variable or expression for each point in a user-defined raster on the simulation region.
+  <p>
+  You must change certain values within the <font color="red">export_results_max.py</font> file to get what you want:
+  <ul>
+    <li> You must determine how many SWW files your simulation produced and create as many lines like this:
+<pre><font color="brown">    time_dir1 = '20090505_150430_run_final_0.8_58292_None_kvanputt'
+    time_dir2 = '20090505_150517_run_final_0_58292_None_kvanputt'</font></pre>
+         as necessary.  Then modify the line:
+<pre><font color="brown">    time_dirs = [time_dir1, time_dir2]</font></pre>
+         to include each of the variables you defined above.
+         <p>   
+    <li> Your SWW output will have a name like <font color="red">gold_coast.sww</font>. For a large model you 
+         may have more than one output file with extra filenames like <font color="red">gold_coast_37860_0.sww</font>,
+         where the <b>37860</b> tells us that the timestep at the start of this file is 37860 sec. The  
+         <font color="red">export_results_max.py</font> script needs to examine all SWW output files, so we specify
+         all the files produced by the model run to create a maximum over the entire time.
+         We do this by specifying the start times of all the extra SWW files: 
+         <p>	
+<pre><font color="brown">    times = [37860]</font></pre>
+         <p>
+         Note we do not have to specify the first SWW file, only the extra file start times. If there are no extra SWW files,
+         just do:
+         <p>	
+<pre><font color="brown">    times = []</font></pre>
+         <p>
+    <li> Modify the <b>cellsize</b> value to set the size of the raster you require.  For example:
+<pre><font color="brown">    cellsize = 20		# raster cell size in metres</font></pre>
+         <p>	
+    <li> You can get the maximum of a variable or expression over the entire model time, or for a single time in the simulation. 
+         Set <b>timestep</b> to the required time you want the maximum for, or set it to <b>None</b> to indicate that you want
+         the maximum values in the raster over all timesteps:
+<pre><font color="brown">    timestep = None  # over all timesteps
+    #timestep = 0</font></pre>
+         <p>         
+         Note that if you want the elevation use <b>timestep = 0</b>. Elevation does not change over time and you only need the 
+         first SWW file.		
+         <p>
+    <li> If you want to clip the raster to one or more small regions then put the names of the regions of interest
+         into the <b>area</b> list:
+<pre><font color="brown">    area = ['Gold_Coast', 'NW', 'South']</font></pre>
+         Note that the name strings you put into the <b>area</b> list must match the names used in the
+         <font color="red">project.py</font> file.  That is, if you use a name such as 'NW', then the
+         <font color="red">project.py</font> file must have lines like:
+<pre><font color="brown">    xminNW = 548000
+    xmaxNW = 561000
+    yminNW = 5250000
+    ymaxNW = 5258000</font></pre>
+         which set the maximum and minimum eastings and northings that define a rectangular region.
+         <p>
+         If you don't want to clip to a region of interest, then do this:
+<pre><font color="brown">    area = ['All']		# no region of interest</font></pre>
+         <p>
+    <li> Finally you must decide which variable or expression values you want sampled on your raster.
+         Define a list <b>var</b> that contains strings defining the required variable or expression:
+<pre><font color="brown">    var = ['depth', 'speed']</font></pre>
+         Note that the strings you supply must be defined in the <b>var_equations</b> dictionary
+         prior to your definition of <b>var</b>:
+<pre><font color="brown">    var_equations = {'stage':     'stage',
+                     'momentum':  '(xmomentum**2 + ymomentum**2)**0.5',
+                     'depth':     'stage-elevation',
+                     'speed':     '(xmomentum**2 + ymomentum**2)**0.5/(stage-elevation+1.e-6)',
+                     'elevation': 'elevation' }</font></pre>
+         This dictionary maps your <b>var</b> strings to a variable or expression.
+  </ul>
+
+  <a name="get_timeseries.py"><h3><b>get_timeseries.py</b></h3></a>
+  The <font color="red">get_timeseries.py</font> script is used to get timeseries data for a selection of variable
+  data at one or more gauge points in a simulation.
+  <p>
+  You must change certain values within the <font color="red">get_timeseries.py</font> file to get what you want:
+  <ul>
+    <li> You must determine how many SWW files your simulation produced and create as many lines like this:
+<pre><font color="brown">    time_dir1 = '20090505_150430_run_final_0.8_58292_None_kvanputt'
+    time_dir2 = '20090505_150517_run_final_0_58292_None_kvanputt'</font></pre>
+         as necessary.  Then modify the line:
+<pre><font color="brown">    time_dirs = [time_dir1, time_dir2]</font></pre>
+         to include each of the variables you defined above.
+         <p>
+    <li> Make sure that the <b>gauges</b> list in <font color="red">projects.py</font> contains one or more CSV files
+         defining the gauges within the simulation that you want the timeseries data for.
+         The gauge file must have this format:
+<pre><font color="brown">    easting,northing,name,elevation
+    559134.8963,5251176.875,Connelly,2
+    532441.5164,5239639.686,Opossum,2</font></pre>
+  </ul>
+</body>
+</html>
Index: /DVD_images/extra_files/GoldCoast/installation.html
===================================================================
--- /DVD_images/extra_files/GoldCoast/installation.html	(revision 7301)
+++ /DVD_images/extra_files/GoldCoast/installation.html	(revision 7301)
@@ -0,0 +1,148 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+  <title>Geoscience Australia</title>
+  <link rel="stylesheet" href="browser_files/style.css">
+  <link REL="SHORTCUT ICON" HREF="browser_files/favicon.ico">
+</head>
+<body>
+  <table cellspacing="10" border="0">
+    <tr>
+      <td>
+        <img src="browser_files/logo.jpg" alt="Australian Government, Geoscience Australia" width="327" height="80" border="0"/>
+      </td>
+      <td width="50">
+        &nbsp;
+      </td>
+      <td>
+        <H1>Tsunami Inundation Models for the GOLD COAST region</H1>
+      </td>
+    </tr>
+  </table>
+  <hr>
+
+  <a name="introduction"><h2><b>Installing, Running and Changing the Simulation</b></h2></a>
+
+  This document describes the installation and running of the simulation software.
+  <p>
+  In addition, we show how to change your simulation, add new elevation data, etc, and how to get help if you have trouble.
+
+  <a name="requirements"><h3><b>Requirements</b></h3></a>
+
+  The tsunami inundation simulations are based on the Open Source software package called ANUGA.
+  For more information about ANUGA visit <a href="https://datamining.anu.edu.au/anuga">https://datamining.anu.edu.au/anuga</a>. 
+  <p>
+  ANUGA has been developed and tested under the Windows XP and Linux (Ubuntu, Mint and Red Hat) operating systems.  
+  ANUGA may also be installed on a Windows Vista system and Debian Linux, but these have not been extensively tested.
+  <p>
+  The ANUGA scripts on this DVD require a minimum of 3GB of memory and possibly more, if mesh resolutions are increased. For this reason
+  we recommend using 64 bit Ubuntu Linux as this operating system can use more than 3GB of memory, whereas Windows XP cannot.
+
+  <a name="installing"><h3><b>Installing ANUGA</b></h3></a>
+
+  You must install ANUGA according to the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
+  As the installation procedure comprises a number of steps we suggest that it is carried out by someone with a
+  basic understanding of how to install software packages on the operating system of choice. 
+
+  <a name="simulating"><h3><b>How to run a simulation</b></h3></a>
+
+  This is how you should run the model on this DVD.
+  We assume that you are using Windows and will give examples for that operating system.
+  The translation to Linux should be obvious, but the <a href="#userslist">ANUGA user's mailing list</a>
+  can be used to get help.
+  <p>
+  
+  <p>
+  <hr align="left" width="100">
+  <p>
+  First, it is assumed you have installed the ANUGA software according to the
+  <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
+  <p>
+  <hr align="left" width="100">
+  <p>
+  Next, you must copy the entire contents of the DVD to a place in your filesystem. Let's assume
+  that you want to put the data into <b>C:\ANUGA</b>. You would do this in a Command Prompt window:
+  <table class="code"><tr><td>
+    C:<br>
+    cd \<br>
+    mkdir ANUGA<br>
+    xcopy /e X:\ ANUGA
+  </td></tr></table>
+  <p>
+  Of course, you could just drag all files on the DVD (X:\ is the assumed drive letter) to the desired target directory with Explorer.
+  <p>
+  <hr align="left" width="100">
+  <p>
+  Now you must create an environment variable <b>ANUGADATA</b> that points to the directory you just created:
+  <table class="code"><tr><td>
+    set ANUGADATA=C:\ANUGA
+  </td></tr></table>
+  <p>
+  Doing the above in a Command Prompt window is temporary - if you open another
+  window you will not have the ANUGADATA environment variable defined. To make
+  the variable permanent you must set it in the <b>Start|Settings|Control Panel|System</b>
+  tool (<b>Advanced</b> tab).  See the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>
+  if you don't know how to do this.
+  <p>
+  <hr align="left" width="100">
+  <p>
+  Next, you prepare and execute the model:
+  <table class="code"><tr><td>
+    cd C:\ANUGA<br>
+    cd project<br>
+    python setup_model.py<br >
+    python run_model.py
+  </td></tr></table>
+  <p>
+  <hr align="left" width="100">
+  <p>
+  This should all run to completion though it may take several days, depending on
+  the hardware used.
+  <p>
+  If you get an error from <font color="red">setup_model.py</font>
+  or <font color="red">run_model.py</font> look for some explanation in the log
+  files, which you will find under <b>C:\ANUGA\data</b>. Just keep
+  drilling down from that point until you find a directory called <b>outputs</b>.
+  The latest directory in <b>outputs</b> should contain a file called <font color="red">screen_error.txt</font>
+  with an explanation of the error at the end. 
+  <p>
+  Once the simulation has completed you may view the results using the ANUGA
+  viewer as described in the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a> 
+  and <a href="documents/anuga_user_manual.pdf">User Manual</a>.  You may also
+  generate rasters suitable for GIS mapping or write dedicated scripts extracting timeseries at selected
+  locations.  Some hints to help you do this are at the <a href="analysis.html">analysis page</a>.
+  <p>
+  The ANUGA <a href="documents/anuga_user_manual.pdf">User Manual</a> describes
+  how to use the ANUGA system in general and provides some examples of its use.
+
+  <a name="auxscripts"><h3><b>How to extract data from the simulation output files</b></h3></a>
+
+  After you have run a simulation you may wish to extract information from the generated SWW file.
+  On this disk there are a selection of example analysis scripts that you can use or modify.
+  The <a href="analysis.html">analysis scripts</a> page explains how to use the scripts.
+
+  <a name="modifications"><h3><b>How to modify a simulation</b></h3></a>
+
+  After you have run the supplied simulation you may wish to change it in some way, such as adding improved bathymetry data, for example.
+  The <a href="modifications.html">modifications</a> page explains how to do this.
+
+  <a name="userslist"><h3><b>How to join the ANUGA user's mailing list</b></h3></a>
+
+  One of the quickest ways to get your ANUGA questions answered is by asking them on the <b>ANUGA-user</b> mailing list.
+  You can <a href="https://lists.sourceforge.net/lists/listinfo/anuga-user">subscribe to the list</a>
+  and can view the mailing list <a href="https://sourceforge.net/mailarchive/forum.php?forum_name=anuga-user">archives</a>.
+  <p>
+  It costs nothing to register and you can choose to have list mail sent to you as individual emails or have them batched
+  into a few emails per day.  You can unsubscribe at any time through the subscribe link above.
+
+  <a name="FAQ"><h3><b>Frequently Asked Questions</b></h3></a>
+
+  There is a <b>Frequently Asked Questions</b> (FAQ) page at
+  <a href="https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions">https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions</a>.
+  Look in there and search the mailing list archives before asking questions on the ANUGA user's mailing list.
+  Someone may already have asked your question!
+  <p>
+  Note that you can edit the FAQ pages, so it is helpful if you can update the FAQ with your question and its answer if you feel
+  it would be helpful to others.
+</body>
+</html>
Index: /DVD_images/extra_files/GoldCoast/modifications.html
===================================================================
--- /DVD_images/extra_files/GoldCoast/modifications.html	(revision 7301)
+++ /DVD_images/extra_files/GoldCoast/modifications.html	(revision 7301)
@@ -0,0 +1,188 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+  <title>Geoscience Australia</title>
+  <link rel="stylesheet" href="browser_files/style.css">
+  <link REL="SHORTCUT ICON" HREF="browser_files/favicon.ico">
+</head>
+<body>
+  <table cellspacing="10" border="0">
+    <tr>
+      <td>
+        <img src="browser_files/logo.jpg" alt="Australian Government, Geoscience Australia" width="327" height="80" border="0"/>
+      </td>
+      <td width="50">
+        &nbsp;
+      </td>
+      <td>
+        <H1>Tsunami Inundation Models for the GOLD COAST region</H1>
+      </td>
+    </tr>
+  </table>
+  <hr>
+
+  <a name="modifications"><h2><b>Modifying a simulation</b></h2></a>
+
+  Here we talk about how you change a simulation.  Why would you need to change a simulation?  Well, 
+  you might have some better elevation data, you want to run the simulation on a finer mesh in certain
+  areas, or maybe you want to see the result for different events.
+  <p>
+  First we describe the uses of the script files you might change, then we walk through a few examples 
+  of changes you might make.
+  <p>
+
+  <a name="project_files"><h3><b>The project scripts</b></h3></a>
+
+  In the <b>project</b> directory are the scripts that control the simulation.  These scripts are:
+  <table class="code">
+    <tr><td><font color="red">project.py</font></td><td>Defines the input data used, where to place output, etc.</td></tr>
+    <tr><td><font color="red">build_elevation.py</font></td><td>Builds a PTS file of all elevation data specified by <font color="red">project.py</font></td></tr>
+    <tr><td><font color="red">setup_model.py</font></td><td>Prepares the simulation before actually running it</td></tr>
+    <tr><td><font color="red">run_model.py</font></td><td>Runs the simulation</td></tr>
+  </table>
+
+  <a name="project.py"><h4><b>project.py</b></h4></a>
+
+    This file is the heart of the simulation. The project script introduces all files that are necessary to run all accompanying scripts.
+    By changing one of the variables in this script the output could be completely different.
+    For further details on changing parameters see <a href="#change">Making changes to a simulation</a>.
+
+<!--  This file is the heart of the simulation.  Here we specify many things, including the tide level, the simulation
+  start and stop times, input data files, and so on.  Because we are using python as the programming language in
+  these files, we can use the power of the language to speed up our development.  We use this by <i>parameterising</i>
+  data as much as possible.
+  <p>
+  Parameters that you might change 
+  As an example, let's look at the <b>scenario_name</b> variable we define in <font color="red">project.py</font>:
+  <table class="code">
+    <tr><td>scenario_name = 'hobart'&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;# name of the scenario</td></tr>
+  </table>
+  <p>
+  We define this variable solely to quickly change other input filenames.  Where we want a different input files for
+  a different scenario, 
+  depending on whether we want a 'small' or 'large' model, we build the filenames using the <b>model</b> variable.
+  Some examples are:
+  <p>
+  <table class="code">
+    <tr height="25"><td>bounding_polygon_filename = 'bounding_polygon_'+ model + '.csv'</td></tr>
+    <tr height="25"><td>land_initial_conditions_filename = [['initial_conditions_' + model +'.csv', 0]]</td></tr>
+    <tr height="25"><td>landward_boundary_filename = 'landward_boundary_'+ model +'.csv'</td></tr>
+  </table>
+  <p>
+  We must, of course, ensure that there are input files <font color="red">bounding_polygon_small.csv</font>
+  and <font color="red">bounding_polygon_large.csv</font>, and so on.
+  <p>
+  Now, if we need to change the simulation model from 'small' to 'large', we need only change the
+  value of the <b>model</b> variable, and all the input files that depend on the model will change.
+  This speeds up development and make errors less likely.  If you want to add another model to the two 
+  we show above, just set <b>model</b> to 'medium' and create appropriate input files with the string
+  'medium' in the filename. -->
+
+  <a name="build_elevation.py"><h4><b>build_elevation.py</b></h4></a>
+
+  This script combines all input elevation files into one PTS file.
+  We have provided you with the PTS file used to create the outputs on this DVD.
+  If you would like to change the elevation see <a href="#change">Making changes to a simulation</a>. 
+  <p>
+
+  <a name="setup_model.py"><h4><b>setup_model.py</b></h4></a>
+
+  This script is used to transform data into a specific format for <font color="red">run_model.py</font>,
+  if required, and to generate warning messages if you are missing data.
+  <p>
+
+  <a name="run_model.py"><h4><b>run_model.py</b></h4></a>
+
+  This script runs a tsunami inundation scenario.  It relies on the parameters set in <font color="red">project.py</font>
+  as well as the PTS and STS files.
+  An STS file has been generated for each event listed in the boundaries directory. For further details on events see
+  <a href="#change">Making changes to a simulation</a>.
+  <p>
+
+  <a name="change"><h3><b>Making changes to a simulation</b></h3></a>
+
+  There are many parameters that you can change within the <font color="red">project.py</font> script,
+  but the following four parameters are those most commonly changed.
+  <p>
+
+  <a name="tide"><h4><b>Tide</b></h4></a>
+
+  The <b>tide</b> parameter is used to change the mean stage of the simulation.  When <b>tide</b> is set to 0
+  the initial water level will be at Mean Sea Level.  If you increase the <b>tide</b> value the water level will become deeper.
+  However land is masked out using initial conditions.  Within ANUGA <b>tide</b> is modelled as a constant.
+  <p>
+
+  <a name="events"><h4><b>Events</b></h4></a>
+
+  The <b>event_number</b> variable contains the event number that initiates the tsunami we are modelling.
+  You can change <b>event_number</b> to any event number in the anuga/boundaries directory.
+  As we said above, a new STS file must be generated for <font color="red">run_model.py</font> to work.
+  <p>
+  The event numbers correspond to a quake ID from the probabilistic tsunami hazard map of Australia.
+  <table class="code">
+    <tr><td><pre>event_number = 51436    # 1 in 10000 yr event from New Hebrides</pre></td></tr>
+  </table>
+  <p>
+
+  <a name="elevation"><h4><b>Elevation</b></h4></a>
+
+  Elevation data can be changed in the <font color="red">project.py</font> elevation script.
+  Elevation data can be read as either a point file, comma delimited, or as an ASCII grid file
+  (ASC) with an accompanying projection file (PRJ). All elevation input must be projected in the correct UTM zone.
+  <p>
+
+  A header for a CSV file has the format:
+  <table class="code">
+    <tr><td><pre>x,y,elevation</pre></td></tr>
+  </table>
+  <p>
+
+  An ASC file header has the format:
+  <table class="code">
+    <tr><td><pre>ncols         868
+nrows         856
+xllcorner     418933.86055096
+yllcorner     5151810.6668096
+cellsize      250
+NODATA_value  -9999</pre></td></tr>
+  </table>
+  <p>
+
+  The header of a PRJ file has the format:
+  <table class="code">
+    <tr><td><pre>Projection    UTM
+Zone          55
+Datum         D_GDA_1994
+Zunits        NO
+Units         METERS
+Spheroid      GRS_1980
+Xshift        500000
+Yshift        10000000
+Parameters</pre></td></tr>
+  </table>
+  <p>
+
+  The elevation filenames must be listed in either <b>point_filenames</b> or <b>ascii_grid_filenames</b>
+  depending on their format. Point files need to have their extension shown however the ascii grid files have the .asc extension assumed:
+  <table class="code">
+    <tr><td><pre>point_filenames = ['SD100031996_jgriffin_clip.csv',
+                   'tomaga_offshore_AHD_MGA_1997.csv',
+                   'Batemans_BBHD_MGA_1995.csv',
+                   'moruya_AHD_MGA_2000.csv']
+
+ascii_grid_filenames = ['sd100031996_p',
+                        'sd100031996_p2',
+                        'sd100031996_p3',
+                        'sd100031996_p4']</pre></td></tr>
+  </table>
+  <p>
+
+  For further information on ANUGA file formats please see the ANUGA User Manual, section 6.1.
+  <p>
+
+  <a name="interior_regions"><h4><b>Interior regions</b></h4></a>
+
+  The <b>interior_regions</b> parameter allows you to change the mesh of the model.
+  <p>
+</body>
+</html>
Index: /DVD_images/extra_files/Gosford/analysis.html
===================================================================
--- /DVD_images/extra_files/Gosford/analysis.html	(revision 7301)
+++ /DVD_images/extra_files/Gosford/analysis.html	(revision 7301)
@@ -0,0 +1,121 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+  <title>Geoscience Australia</title>
+  <link rel="stylesheet" href="browser_files/style.css">
+  <link REL="SHORTCUT ICON" HREF="browser_files/favicon.ico">
+</head>
+<body>
+  <table cellspacing="10" border="0">
+    <tr>
+      <td>
+        <img src="browser_files/logo.jpg" alt="Australian Government, Geoscience Australia" width="327" height="80" border="0"/>
+      </td>
+      <td width="50">
+        &nbsp;
+      </td>
+      <td>
+        <H1>Tsunami Inundation Models for the GOSFORD region</H1>
+      </td>
+    </tr>
+  </table>
+  <hr>
+
+  <a name="analysis scripts"><h2><b>Analysis Scripts</b></h2></a>
+  There are number of analysis scripts on this disk that you can use to extract information from the SWW files
+  produced by a simulation run.  These scripts are not meant to be the definitive answer on how to get information
+  from SWW files, but are offered as an example of one way to do it.
+  <p>
+  This page describes the scripts and shows how to use them.  Note that due to the ad-hoc nature of the scripts, 
+  you <b>must</b> modify these scripts before they can be used to extract information from any SWW files you
+  generate.
+
+  <a name="export_results_max.py scripts"><h3><b>export_results_max.py</b></h3></a>
+  The <font color="red">export_results_max.py</font> script can be used to create an ASC file that contains the maximum
+  of an ANUGA variable or expression for each point in a user-defined raster on the simulation region.
+  <p>
+  You must change certain values within the <font color="red">export_results_max.py</font> file to get what you want:
+  <ul>
+    <li> You must determine how many SWW files your simulation produced and create as many lines like this:
+<pre><font color="brown">    time_dir1 = '20090505_150430_run_final_0.8_58292_None_kvanputt'
+    time_dir2 = '20090505_150517_run_final_0_58292_None_kvanputt'</font></pre>
+         as necessary.  Then modify the line:
+<pre><font color="brown">    time_dirs = [time_dir1, time_dir2]</font></pre>
+         to include each of the variables you defined above.
+         <p>   
+    <li> Your SWW output will have a name like <font color="red">gosford.sww</font>. For a large model you 
+         may have more than one output file with extra filenames like <font color="red">gosford_37860_0.sww</font>,
+         where the <b>37860</b> tells us that the timestep at the start of this file is 37860 sec. The  
+         <font color="red">export_results_max.py</font> script needs to examine all SWW output files, so we specify
+         all the files produced by the model run to create a maximum over the entire time.
+         We do this by specifying the start times of all the extra SWW files: 
+         <p>	
+<pre><font color="brown">    times = [37860]</font></pre>
+         <p>
+         Note we do not have to specify the first SWW file, only the extra file start times. If there are no extra SWW files,
+         just do:
+         <p>	
+<pre><font color="brown">    times = []</font></pre>
+         <p>
+    <li> Modify the <b>cellsize</b> value to set the size of the raster you require.  For example:
+<pre><font color="brown">    cellsize = 20		# raster cell size in metres</font></pre>
+         <p>	
+    <li> You can get the maximum of a variable or expression over the entire model time, or for a single time in the simulation. 
+         Set <b>timestep</b> to the required time you want the maximum for, or set it to <b>None</b> to indicate that you want
+         the maximum values in the raster over all timesteps:
+<pre><font color="brown">    timestep = None  # over all timesteps
+    #timestep = 0</font></pre>
+         <p>         
+         Note that if you want the elevation use <b>timestep = 0</b>. Elevation does not change over time and you only need the 
+         first SWW file.		
+         <p>
+    <li> If you want to clip the raster to one or more small regions then put the names of the regions of interest
+         into the <b>area</b> list:
+<pre><font color="brown">    area = ['Batemans_Bay', 'NW', 'South']</font></pre>
+         Note that the name strings you put into the <b>area</b> list must match the names used in the
+         <font color="red">project.py</font> file.  That is, if you use a name such as 'NW', then the
+         <font color="red">project.py</font> file must have lines like:
+<pre><font color="brown">    xminNW = 548000
+    xmaxNW = 561000
+    yminNW = 5250000
+    ymaxNW = 5258000</font></pre>
+         which set the maximum and minimum eastings and northings that define a rectangular region.
+         <p>
+         If you don't want to clip to a region of interest, then do this:
+<pre><font color="brown">    area = ['All']		# no region of interest</font></pre>
+         <p>
+    <li> Finally you must decide which variable or expression values you want sampled on your raster.
+         Define a list <b>var</b> that contains strings defining the required variable or expression:
+<pre><font color="brown">    var = ['depth', 'speed']</font></pre>
+         Note that the strings you supply must be defined in the <b>var_equations</b> dictionary
+         prior to your definition of <b>var</b>:
+<pre><font color="brown">    var_equations = {'stage':     'stage',
+                     'momentum':  '(xmomentum**2 + ymomentum**2)**0.5',
+                     'depth':     'stage-elevation',
+                     'speed':     '(xmomentum**2 + ymomentum**2)**0.5/(stage-elevation+1.e-6)',
+                     'elevation': 'elevation' }</font></pre>
+         This dictionary maps your <b>var</b> strings to a variable or expression.
+  </ul>
+
+  <a name="get_timeseries.py"><h3><b>get_timeseries.py</b></h3></a>
+  The <font color="red">get_timeseries.py</font> script is used to get timeseries data for a selection of variable
+  data at one or more gauge points in a simulation.
+  <p>
+  You must change certain values within the <font color="red">get_timeseries.py</font> file to get what you want:
+  <ul>
+    <li> You must determine how many SWW files your simulation produced and create as many lines like this:
+<pre><font color="brown">    time_dir1 = '20090505_150430_run_final_0.8_58292_None_kvanputt'
+    time_dir2 = '20090505_150517_run_final_0_58292_None_kvanputt'</font></pre>
+         as necessary.  Then modify the line:
+<pre><font color="brown">    time_dirs = [time_dir1, time_dir2]</font></pre>
+         to include each of the variables you defined above.
+         <p>
+    <li> Make sure that the <b>gauges</b> list in <font color="red">projects.py</font> contains one or more CSV files
+         defining the gauges within the simulation that you want the timeseries data for.
+         The gauge file must have this format:
+<pre><font color="brown">    easting,northing,name,elevation
+    559134.8963,5251176.875,Connelly,2
+    532441.5164,5239639.686,Opossum,2</font></pre>
+  </ul>
+</body>
+</html>
Index: /DVD_images/extra_files/Gosford/installation.html
===================================================================
--- /DVD_images/extra_files/Gosford/installation.html	(revision 7301)
+++ /DVD_images/extra_files/Gosford/installation.html	(revision 7301)
@@ -0,0 +1,148 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+  <title>Geoscience Australia</title>
+  <link rel="stylesheet" href="browser_files/style.css">
+  <link REL="SHORTCUT ICON" HREF="browser_files/favicon.ico">
+</head>
+<body>
+  <table cellspacing="10" border="0">
+    <tr>
+      <td>
+        <img src="browser_files/logo.jpg" alt="Australian Government, Geoscience Australia" width="327" height="80" border="0"/>
+      </td>
+      <td width="50">
+        &nbsp;
+      </td>
+      <td>
+        <H1>Tsunami Inundation Models for the GOSFORD region</H1>
+      </td>
+    </tr>
+  </table>
+  <hr>
+
+  <a name="introduction"><h2><b>Installing, Running and Changing the Simulation</b></h2></a>
+
+  This document describes the installation and running of the simulation software.
+  <p>
+  In addition, we show how to change your simulation, add new elevation data, etc, and how to get help if you have trouble.
+
+  <a name="requirements"><h3><b>Requirements</b></h3></a>
+
+  The tsunami inundation simulations are based on the Open Source software package called ANUGA.
+  For more information about ANUGA visit <a href="https://datamining.anu.edu.au/anuga">https://datamining.anu.edu.au/anuga</a>. 
+  <p>
+  ANUGA has been developed and tested under the Windows XP and Linux (Ubuntu, Mint and Red Hat) operating systems.  
+  ANUGA may also be installed on a Windows Vista system and Debian Linux, but these have not been extensively tested.
+  <p>
+  The ANUGA scripts on this DVD require a minimum of 3GB of memory and possibly more, if mesh resolutions are increased. For this reason
+  we recommend using 64 bit Ubuntu Linux as this operating system can use more than 3GB of memory, whereas Windows XP cannot.
+
+  <a name="installing"><h3><b>Installing ANUGA</b></h3></a>
+
+  You must install ANUGA according to the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
+  As the installation procedure comprises a number of steps we suggest that it is carried out by someone with a
+  basic understanding of how to install software packages on the operating system of choice. 
+
+  <a name="simulating"><h3><b>How to run a simulation</b></h3></a>
+
+  This is how you should run the model on this DVD.
+  We assume that you are using Windows and will give examples for that operating system.
+  The translation to Linux should be obvious, but the <a href="#userslist">ANUGA user's mailing list</a>
+  can be used to get help.
+  <p>
+  
+  <p>
+  <hr align="left" width="100">
+  <p>
+  First, it is assumed you have installed the ANUGA software according to the
+  <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
+  <p>
+  <hr align="left" width="100">
+  <p>
+  Next, you must copy the entire contents of the DVD to a place in your filesystem. Let's assume
+  that you want to put the data into <b>C:\ANUGA</b>. You would do this in a Command Prompt window:
+  <table class="code"><tr><td>
+    C:<br>
+    cd \<br>
+    mkdir ANUGA<br>
+    xcopy /e X:\ ANUGA
+  </td></tr></table>
+  <p>
+  Of course, you could just drag all files on the DVD (X:\ is the assumed drive letter) to the desired target directory with Explorer.
+  <p>
+  <hr align="left" width="100">
+  <p>
+  Now you must create an environment variable <b>ANUGADATA</b> that points to the directory you just created:
+  <table class="code"><tr><td>
+    set ANUGADATA=C:\ANUGA
+  </td></tr></table>
+  <p>
+  Doing the above in a Command Prompt window is temporary - if you open another
+  window you will not have the ANUGADATA environment variable defined. To make
+  the variable permanent you must set it in the <b>Start|Settings|Control Panel|System</b>
+  tool (<b>Advanced</b> tab).  See the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>
+  if you don't know how to do this.
+  <p>
+  <hr align="left" width="100">
+  <p>
+  Next, you prepare and execute the model:
+  <table class="code"><tr><td>
+    cd C:\ANUGA<br>
+    cd project<br>
+    python setup_model.py<br >
+    python run_model.py
+  </td></tr></table>
+  <p>
+  <hr align="left" width="100">
+  <p>
+  This should all run to completion though it may take several days, depending on
+  the hardware used.
+  <p>
+  If you get an error from <font color="red">setup_model.py</font>
+  or <font color="red">run_model.py</font> look for some explanation in the log
+  files, which you will find under <b>C:\ANUGA\data</b>. Just keep
+  drilling down from that point until you find a directory called <b>outputs</b>.
+  The latest directory in <b>outputs</b> should contain a file called <font color="red">screen_error.txt</font>
+  with an explanation of the error at the end. 
+  <p>
+  Once the simulation has completed you may view the results using the ANUGA
+  viewer as described in the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a> 
+  and <a href="documents/anuga_user_manual.pdf">User Manual</a>.  You may also
+  generate rasters suitable for GIS mapping or write dedicated scripts extracting timeseries at selected
+  locations.  Some hints to help you do this are at the <a href="analysis.html">analysis page</a>.
+  <p>
+  The ANUGA <a href="documents/anuga_user_manual.pdf">User Manual</a> describes
+  how to use the ANUGA system in general and provides some examples of its use.
+
+  <a name="auxscripts"><h3><b>How to extract data from the simulation output files</b></h3></a>
+
+  After you have run a simulation you may wish to extract information from the generated SWW file.
+  On this disk there are a selection of example analysis scripts that you can use or modify.
+  The <a href="analysis.html">analysis scripts</a> page explains how to use the scripts.
+
+  <a name="modifications"><h3><b>How to modify a simulation</b></h3></a>
+
+  After you have run the supplied simulation you may wish to change it in some way, such as adding improved bathymetry data, for example.
+  The <a href="modifications.html">modifications</a> page explains how to do this.
+
+  <a name="userslist"><h3><b>How to join the ANUGA user's mailing list</b></h3></a>
+
+  One of the quickest ways to get your ANUGA questions answered is by asking them on the <b>ANUGA-user</b> mailing list.
+  You can <a href="https://lists.sourceforge.net/lists/listinfo/anuga-user">subscribe to the list</a>
+  and can view the mailing list <a href="https://sourceforge.net/mailarchive/forum.php?forum_name=anuga-user">archives</a>.
+  <p>
+  It costs nothing to register and you can choose to have list mail sent to you as individual emails or have them batched
+  into a few emails per day.  You can unsubscribe at any time through the subscribe link above.
+
+  <a name="FAQ"><h3><b>Frequently Asked Questions</b></h3></a>
+
+  There is a <b>Frequently Asked Questions</b> (FAQ) page at
+  <a href="https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions">https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions</a>.
+  Look in there and search the mailing list archives before asking questions on the ANUGA user's mailing list.
+  Someone may already have asked your question!
+  <p>
+  Note that you can edit the FAQ pages, so it is helpful if you can update the FAQ with your question and its answer if you feel
+  it would be helpful to others.
+</body>
+</html>
Index: /DVD_images/extra_files/Gosford/modifications.html
===================================================================
--- /DVD_images/extra_files/Gosford/modifications.html	(revision 7301)
+++ /DVD_images/extra_files/Gosford/modifications.html	(revision 7301)
@@ -0,0 +1,188 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+  <title>Geoscience Australia</title>
+  <link rel="stylesheet" href="browser_files/style.css">
+  <link REL="SHORTCUT ICON" HREF="browser_files/favicon.ico">
+</head>
+<body>
+  <table cellspacing="10" border="0">
+    <tr>
+      <td>
+        <img src="browser_files/logo.jpg" alt="Australian Government, Geoscience Australia" width="327" height="80" border="0"/>
+      </td>
+      <td width="50">
+        &nbsp;
+      </td>
+      <td>
+        <H1>Tsunami Inundation Models for the GOSFORD region</H1>
+      </td>
+    </tr>
+  </table>
+  <hr>
+
+  <a name="modifications"><h2><b>Modifying a simulation</b></h2></a>
+
+  Here we talk about how you change a simulation.  Why would you need to change a simulation?  Well, 
+  you might have some better elevation data, you want to run the simulation on a finer mesh in certain
+  areas, or maybe you want to see the result for different events.
+  <p>
+  First we describe the uses of the script files you might change, then we walk through a few examples 
+  of changes you might make.
+  <p>
+
+  <a name="project_files"><h3><b>The project scripts</b></h3></a>
+
+  In the <b>project</b> directory are the scripts that control the simulation.  These scripts are:
+  <table class="code">
+    <tr><td><font color="red">project.py</font></td><td>Defines the input data used, where to place output, etc.</td></tr>
+    <tr><td><font color="red">build_elevation.py</font></td><td>Builds a PTS file of all elevation data specified by <font color="red">project.py</font></td></tr>
+    <tr><td><font color="red">setup_model.py</font></td><td>Prepares the simulation before actually running it</td></tr>
+    <tr><td><font color="red">run_model.py</font></td><td>Runs the simulation</td></tr>
+  </table>
+
+  <a name="project.py"><h4><b>project.py</b></h4></a>
+
+    This file is the heart of the simulation. The project script introduces all files that are necessary to run all accompanying scripts.
+    By changing one of the variables in this script the output could be completely different.
+    For further details on changing parameters see <a href="#change">Making changes to a simulation</a>.
+
+<!--  This file is the heart of the simulation.  Here we specify many things, including the tide level, the simulation
+  start and stop times, input data files, and so on.  Because we are using python as the programming language in
+  these files, we can use the power of the language to speed up our development.  We use this by <i>parameterising</i>
+  data as much as possible.
+  <p>
+  Parameters that you might change 
+  As an example, let's look at the <b>scenario_name</b> variable we define in <font color="red">project.py</font>:
+  <table class="code">
+    <tr><td>scenario_name = 'hobart'&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;# name of the scenario</td></tr>
+  </table>
+  <p>
+  We define this variable solely to quickly change other input filenames.  Where we want a different input files for
+  a different scenario, 
+  depending on whether we want a 'small' or 'large' model, we build the filenames using the <b>model</b> variable.
+  Some examples are:
+  <p>
+  <table class="code">
+    <tr height="25"><td>bounding_polygon_filename = 'bounding_polygon_'+ model + '.csv'</td></tr>
+    <tr height="25"><td>land_initial_conditions_filename = [['initial_conditions_' + model +'.csv', 0]]</td></tr>
+    <tr height="25"><td>landward_boundary_filename = 'landward_boundary_'+ model +'.csv'</td></tr>
+  </table>
+  <p>
+  We must, of course, ensure that there are input files <font color="red">bounding_polygon_small.csv</font>
+  and <font color="red">bounding_polygon_large.csv</font>, and so on.
+  <p>
+  Now, if we need to change the simulation model from 'small' to 'large', we need only change the
+  value of the <b>model</b> variable, and all the input files that depend on the model will change.
+  This speeds up development and make errors less likely.  If you want to add another model to the two 
+  we show above, just set <b>model</b> to 'medium' and create appropriate input files with the string
+  'medium' in the filename. -->
+
+  <a name="build_elevation.py"><h4><b>build_elevation.py</b></h4></a>
+
+  This script combines all input elevation files into one PTS file.
+  We have provided you with the PTS file used to create the outputs on this DVD.
+  If you would like to change the elevation see <a href="#change">Making changes to a simulation</a>. 
+  <p>
+
+  <a name="setup_model.py"><h4><b>setup_model.py</b></h4></a>
+
+  This script is used to transform data into a specific format for <font color="red">run_model.py</font>,
+  if required, and to generate warning messages if you are missing data.
+  <p>
+
+  <a name="run_model.py"><h4><b>run_model.py</b></h4></a>
+
+  This script runs a tsunami inundation scenario.  It relies on the parameters set in <font color="red">project.py</font>
+  as well as the PTS and STS files.
+  An STS file has been generated for each event listed in the boundaries directory. For further details on events see
+  <a href="#change">Making changes to a simulation</a>.
+  <p>
+
+  <a name="change"><h3><b>Making changes to a simulation</b></h3></a>
+
+  There are many parameters that you can change within the <font color="red">project.py</font> script,
+  but the following four parameters are those most commonly changed.
+  <p>
+
+  <a name="tide"><h4><b>Tide</b></h4></a>
+
+  The <b>tide</b> parameter is used to change the mean stage of the simulation.  When <b>tide</b> is set to 0
+  the initial water level will be at Mean Sea Level.  If you increase the <b>tide</b> value the water level will become deeper.
+  However land is masked out using initial conditions.  Within ANUGA <b>tide</b> is modelled as a constant.
+  <p>
+
+  <a name="events"><h4><b>Events</b></h4></a>
+
+  The <b>event_number</b> variable contains the event number that initiates the tsunami we are modelling.
+  You can change <b>event_number</b> to any event number in the anuga/boundaries directory.
+  As we said above, a new STS file must be generated for <font color="red">run_model.py</font> to work.
+  <p>
+  The event numbers correspond to a quake ID from the probabilistic tsunami hazard map of Australia.
+  <table class="code">
+    <tr><td><pre>event_number = 51436    # 1 in 10000 yr event from New Hebrides</pre></td></tr>
+  </table>
+  <p>
+
+  <a name="elevation"><h4><b>Elevation</b></h4></a>
+
+  Elevation data can be changed in the <font color="red">project.py</font> elevation script.
+  Elevation data can be read as either a point file, comma delimited, or as an ASCII grid file
+  (ASC) with an accompanying projection file (PRJ). All elevation input must be projected in the correct UTM zone.
+  <p>
+
+  A header for a CSV file has the format:
+  <table class="code">
+    <tr><td><pre>x,y,elevation</pre></td></tr>
+  </table>
+  <p>
+
+  An ASC file header has the format:
+  <table class="code">
+    <tr><td><pre>ncols         868
+nrows         856
+xllcorner     418933.86055096
+yllcorner     5151810.6668096
+cellsize      250
+NODATA_value  -9999</pre></td></tr>
+  </table>
+  <p>
+
+  The header of a PRJ file has the format:
+  <table class="code">
+    <tr><td><pre>Projection    UTM
+Zone          55
+Datum         D_GDA_1994
+Zunits        NO
+Units         METERS
+Spheroid      GRS_1980
+Xshift        500000
+Yshift        10000000
+Parameters</pre></td></tr>
+  </table>
+  <p>
+
+  The elevation filenames must be listed in either <b>point_filenames</b> or <b>ascii_grid_filenames</b>
+  depending on their format. Point files need to have their extension shown however the ascii grid files have the .asc extension assumed:
+  <table class="code">
+    <tr><td><pre>point_filenames = ['SD100031996_jgriffin_clip.csv',
+                   'tomaga_offshore_AHD_MGA_1997.csv',
+                   'gosford_BBHD_MGA_1995.csv',
+                   'gosford_AHD_MGA_2000.csv']
+
+ascii_grid_filenames = ['sd100031996_p',
+                        'sd100031996_p2',
+                        'sd100031996_p3',
+                        'sd100031996_p4']</pre></td></tr>
+  </table>
+  <p>
+
+  For further information on ANUGA file formats please see the ANUGA User Manual, section 6.1.
+  <p>
+
+  <a name="interior_regions"><h4><b>Interior regions</b></h4></a>
+
+  The <b>interior_regions</b> parameter allows you to change the mesh of the model.
+  <p>
+</body>
+</html>
Index: /DVD_images/extra_files/Hobart/analysis.html
===================================================================
--- /DVD_images/extra_files/Hobart/analysis.html	(revision 7301)
+++ /DVD_images/extra_files/Hobart/analysis.html	(revision 7301)
@@ -0,0 +1,121 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+  <title>Geoscience Australia</title>
+  <link rel="stylesheet" href="browser_files/style.css">
+  <link REL="SHORTCUT ICON" HREF="browser_files/favicon.ico">
+</head>
+<body>
+  <table cellspacing="10" border="0">
+    <tr>
+      <td>
+        <img src="browser_files/logo.jpg" alt="Australian Government, Geoscience Australia" width="327" height="80" border="0"/>
+      </td>
+      <td width="50">
+        &nbsp;
+      </td>
+      <td>
+        <H1>Tsunami Inundation Models for the HOBART region</H1>
+      </td>
+    </tr>
+  </table>
+  <hr>
+
+  <a name="analysis scripts"><h2><b>Analysis Scripts</b></h2></a>
+  There are number of analysis scripts on this disk that you can use to extract information from the SWW files
+  produced by a simulation run.  These scripts are not meant to be the definitive answer on how to get information
+  from SWW files, but are offered as an example of one way to do it.
+  <p>
+  This page describes the scripts and shows how to use them.  Note that due to the ad-hoc nature of the scripts, 
+  you <b>must</b> modify these scripts before they can be used to extract information from any SWW files you
+  generate.
+
+  <a name="export_results_max.py scripts"><h3><b>export_results_max.py</b></h3></a>
+  The <font color="red">export_results_max.py</font> script can be used to create an ASC file that contains the maximum
+  of an ANUGA variable or expression for each point in a user-defined raster on the simulation region.
+  <p>
+  You must change certain values within the <font color="red">export_results_max.py</font> file to get what you want:
+  <ul>
+    <li> You must determine how many SWW files your simulation produced and create as many lines like this:
+<pre><font color="brown">    time_dir1 = '20090505_150430_run_final_0.8_58292_None_kvanputt'
+    time_dir2 = '20090505_150517_run_final_0_58292_None_kvanputt'</font></pre>
+         as necessary.  Then modify the line:
+<pre><font color="brown">    time_dirs = [time_dir1, time_dir2]</font></pre>
+         to include each of the variables you defined above.
+         <p>   
+    <li> Your SWW output will have a name like <font color="red">hobart.sww</font>. For a large model you 
+         may have more than one output file with extra filenames like <font color="red">hobart_37860_0.sww</font>,
+         where the <b>37860</b> tells us that the timestep at the start of this file is 37860 sec. The  
+         <font color="red">export_results_max.py</font> script needs to examine all SWW output files, so we specify
+         all the files produced by the model run to create a maximum over the entire time.
+         We do this by specifying the start times of all the extra SWW files: 
+         <p>	
+<pre><font color="brown">    times = [37860]</font></pre>
+         <p>
+         Note we do not have to specify the first SWW file, only the extra file start times. If there are no extra SWW files,
+         just do:
+         <p>	
+<pre><font color="brown">    times = []</font></pre>
+         <p>
+    <li> Modify the <b>cellsize</b> value to set the size of the raster you require.  For example:
+<pre><font color="brown">    cellsize = 20		# raster cell size in metres</font></pre>
+         <p>	
+    <li> You can get the maximum of a variable or expression over the entire model time, or for a single time in the simulation. 
+         Set <b>timestep</b> to the required time you want the maximum for, or set it to <b>None</b> to indicate that you want
+         the maximum values in the raster over all timesteps:
+<pre><font color="brown">    timestep = None  # over all timesteps
+    #timestep = 0</font></pre>
+         <p>         
+         Note that if you want the elevation use <b>timestep = 0</b>. Elevation does not change over time and you only need the 
+         first SWW file.		
+         <p>
+    <li> If you want to clip the raster to one or more small regions then put the names of the regions of interest
+         into the <b>area</b> list:
+<pre><font color="brown">    area = ['Hobart', 'NW', 'South']</font></pre>
+         Note that the name strings you put into the <b>area</b> list must match the names used in the
+         <font color="red">project.py</font> file.  That is, if you use a name such as 'NW', then the
+         <font color="red">project.py</font> file must have lines like:
+<pre><font color="brown">    xminNW = 548000
+    xmaxNW = 561000
+    yminNW = 5250000
+    ymaxNW = 5258000</font></pre>
+         which set the maximum and minimum eastings and northings that define a rectangular region.
+         <p>
+         If you don't want to clip to a region of interest, then do this:
+<pre><font color="brown">    area = ['All']		# no region of interest</font></pre>
+         <p>
+    <li> Finally you must decide which variable or expression values you want sampled on your raster.
+         Define a list <b>var</b> that contains strings defining the required variable or expression:
+<pre><font color="brown">    var = ['depth', 'speed']</font></pre>
+         Note that the strings you supply must be defined in the <b>var_equations</b> dictionary
+         prior to your definition of <b>var</b>:
+<pre><font color="brown">    var_equations = {'stage':     'stage',
+                     'momentum':  '(xmomentum**2 + ymomentum**2)**0.5',
+                     'depth':     'stage-elevation',
+                     'speed':     '(xmomentum**2 + ymomentum**2)**0.5/(stage-elevation+1.e-6)',
+                     'elevation': 'elevation' }</font></pre>
+         This dictionary maps your <b>var</b> strings to a variable or expression.
+  </ul>
+
+  <a name="get_timeseries.py"><h3><b>get_timeseries.py</b></h3></a>
+  The <font color="red">get_timeseries.py</font> script is used to get timeseries data for a selection of variable
+  data at one or more gauge points in a simulation.
+  <p>
+  You must change certain values within the <font color="red">get_timeseries.py</font> file to get what you want:
+  <ul>
+    <li> You must determine how many SWW files your simulation produced and create as many lines like this:
+<pre><font color="brown">    time_dir1 = '20090505_150430_run_final_0.8_58292_None_kvanputt'
+    time_dir2 = '20090505_150517_run_final_0_58292_None_kvanputt'</font></pre>
+         as necessary.  Then modify the line:
+<pre><font color="brown">    time_dirs = [time_dir1, time_dir2]</font></pre>
+         to include each of the variables you defined above.
+         <p>
+    <li> Make sure that the <b>gauges</b> list in <font color="red">projects.py</font> contains one or more CSV files
+         defining the gauges within the simulation that you want the timeseries data for.
+         The gauge file must have this format:
+<pre><font color="brown">    easting,northing,name,elevation
+    559134.8963,5251176.875,Connelly,2
+    532441.5164,5239639.686,Opossum,2</font></pre>
+  </ul>
+</body>
+</html>
Index: /DVD_images/extra_files/Hobart/installation.html
===================================================================
--- /DVD_images/extra_files/Hobart/installation.html	(revision 7301)
+++ /DVD_images/extra_files/Hobart/installation.html	(revision 7301)
@@ -0,0 +1,148 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+  <title>Geoscience Australia</title>
+  <link rel="stylesheet" href="browser_files/style.css">
+  <link REL="SHORTCUT ICON" HREF="browser_files/favicon.ico">
+</head>
+<body>
+  <table cellspacing="10" border="0">
+    <tr>
+      <td>
+        <img src="browser_files/logo.jpg" alt="Australian Government, Geoscience Australia" width="327" height="80" border="0"/>
+      </td>
+      <td width="50">
+        &nbsp;
+      </td>
+      <td>
+        <H1>Tsunami Inundation Models for the HOBART region</H1>
+      </td>
+    </tr>
+  </table>
+  <hr>
+
+  <a name="introduction"><h2><b>Installing, Running and Changing the Simulation</b></h2></a>
+
+  This document describes the installation and running of the simulation software.
+  <p>
+  In addition, we show how to change your simulation, add new elevation data, etc, and how to get help if you have trouble.
+
+  <a name="requirements"><h3><b>Requirements</b></h3></a>
+
+  The tsunami inundation simulations are based on the Open Source software package called ANUGA.
+  For more information about ANUGA visit <a href="https://datamining.anu.edu.au/anuga">https://datamining.anu.edu.au/anuga</a>. 
+  <p>
+  ANUGA has been developed and tested under the Windows XP and Linux (Ubuntu, Mint and Red Hat) operating systems.  
+  ANUGA may also be installed on a Windows Vista system and Debian Linux, but these have not been extensively tested.
+  <p>
+  The ANUGA scripts on this DVD require a minimum of 3GB of memory and possibly more, if mesh resolutions are increased. For this reason
+  we recommend using 64 bit Ubuntu Linux as this operating system can use more than 3GB of memory, whereas Windows XP cannot.
+
+  <a name="installing"><h3><b>Installing ANUGA</b></h3></a>
+
+  You must install ANUGA according to the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
+  As the installation procedure comprises a number of steps we suggest that it is carried out by someone with a
+  basic understanding of how to install software packages on the operating system of choice. 
+
+  <a name="simulating"><h3><b>How to run a simulation</b></h3></a>
+
+  This is how you should run the model on this DVD.
+  We assume that you are using Windows and will give examples for that operating system.
+  The translation to Linux should be obvious, but the <a href="#userslist">ANUGA user's mailing list</a>
+  can be used to get help.
+  <p>
+  
+  <p>
+  <hr align="left" width="100">
+  <p>
+  First, it is assumed you have installed the ANUGA software according to the
+  <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
+  <p>
+  <hr align="left" width="100">
+  <p>
+  Next, you must copy the entire contents of the DVD to a place in your filesystem. Let's assume
+  that you want to put the data into <b>C:\ANUGA</b>. You would do this in a Command Prompt window:
+  <table class="code"><tr><td>
+    C:<br>
+    cd \<br>
+    mkdir ANUGA<br>
+    xcopy /e X:\ ANUGA
+  </td></tr></table>
+  <p>
+  Of course, you could just drag all files on the DVD (X:\ is the assumed drive letter) to the desired target directory with Explorer.
+  <p>
+  <hr align="left" width="100">
+  <p>
+  Now you must create an environment variable <b>ANUGADATA</b> that points to the directory you just created:
+  <table class="code"><tr><td>
+    set ANUGADATA=C:\ANUGA
+  </td></tr></table>
+  <p>
+  Doing the above in a Command Prompt window is temporary - if you open another
+  window you will not have the ANUGADATA environment variable defined. To make
+  the variable permanent you must set it in the <b>Start|Settings|Control Panel|System</b>
+  tool (<b>Advanced</b> tab).  See the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>
+  if you don't know how to do this.
+  <p>
+  <hr align="left" width="100">
+  <p>
+  Next, you prepare and execute the model:
+  <table class="code"><tr><td>
+    cd C:\ANUGA<br>
+    cd project<br>
+    python setup_model.py<br >
+    python run_model.py
+  </td></tr></table>
+  <p>
+  <hr align="left" width="100">
+  <p>
+  This should all run to completion though it may take several days, depending on
+  the hardware used.
+  <p>
+  If you get an error from <font color="red">setup_model.py</font>
+  or <font color="red">run_model.py</font> look for some explanation in the log
+  files, which you will find under <b>C:\ANUGA\data</b>. Just keep
+  drilling down from that point until you find a directory called <b>outputs</b>.
+  The latest directory in <b>outputs</b> should contain a file called <font color="red">screen_error.txt</font>
+  with an explanation of the error at the end. 
+  <p>
+  Once the simulation has completed you may view the results using the ANUGA
+  viewer as described in the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a> 
+  and <a href="documents/anuga_user_manual.pdf">User Manual</a>.  You may also
+  generate rasters suitable for GIS mapping or write dedicated scripts extracting timeseries at selected
+  locations.  Some hints to help you do this are at the <a href="analysis.html">analysis page</a>.
+  <p>
+  The ANUGA <a href="documents/anuga_user_manual.pdf">User Manual</a> describes
+  how to use the ANUGA system in general and provides some examples of its use.
+
+  <a name="auxscripts"><h3><b>How to extract data from the simulation output files</b></h3></a>
+
+  After you have run a simulation you may wish to extract information from the generated SWW file.
+  On this disk there are a selection of example analysis scripts that you can use or modify.
+  The <a href="analysis.html">analysis scripts</a> page explains how to use the scripts.
+
+  <a name="modifications"><h3><b>How to modify a simulation</b></h3></a>
+
+  After you have run the supplied simulation you may wish to change it in some way, such as adding improved bathymetry data, for example.
+  The <a href="modifications.html">modifications</a> page explains how to do this.
+
+  <a name="userslist"><h3><b>How to join the ANUGA user's mailing list</b></h3></a>
+
+  One of the quickest ways to get your ANUGA questions answered is by asking them on the <b>ANUGA-user</b> mailing list.
+  You can <a href="https://lists.sourceforge.net/lists/listinfo/anuga-user">subscribe to the list</a>
+  and can view the mailing list <a href="https://sourceforge.net/mailarchive/forum.php?forum_name=anuga-user">archives</a>.
+  <p>
+  It costs nothing to register and you can choose to have list mail sent to you as individual emails or have them batched
+  into a few emails per day.  You can unsubscribe at any time through the subscribe link above.
+
+  <a name="FAQ"><h3><b>Frequently Asked Questions</b></h3></a>
+
+  There is a <b>Frequently Asked Questions</b> (FAQ) page at
+  <a href="https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions">https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions</a>.
+  Look in there and search the mailing list archives before asking questions on the ANUGA user's mailing list.
+  Someone may already have asked your question!
+  <p>
+  Note that you can edit the FAQ pages, so it is helpful if you can update the FAQ with your question and its answer if you feel
+  it would be helpful to others.
+</body>
+</html>
Index: /DVD_images/extra_files/Hobart/modifications.html
===================================================================
--- /DVD_images/extra_files/Hobart/modifications.html	(revision 7301)
+++ /DVD_images/extra_files/Hobart/modifications.html	(revision 7301)
@@ -0,0 +1,188 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+  <title>Geoscience Australia</title>
+  <link rel="stylesheet" href="browser_files/style.css">
+  <link REL="SHORTCUT ICON" HREF="browser_files/favicon.ico">
+</head>
+<body>
+  <table cellspacing="10" border="0">
+    <tr>
+      <td>
+        <img src="browser_files/logo.jpg" alt="Australian Government, Geoscience Australia" width="327" height="80" border="0"/>
+      </td>
+      <td width="50">
+        &nbsp;
+      </td>
+      <td>
+        <H1>Tsunami Inundation Models for the HOBART region</H1>
+      </td>
+    </tr>
+  </table>
+  <hr>
+
+  <a name="modifications"><h2><b>Modifying a simulation</b></h2></a>
+
+  Here we talk about how you change a simulation.  Why would you need to change a simulation?  Well, 
+  you might have some better elevation data, you want to run the simulation on a finer mesh in certain
+  areas, or maybe you want to see the result for different events.
+  <p>
+  First we describe the uses of the script files you might change, then we walk through a few examples 
+  of changes you might make.
+  <p>
+
+  <a name="project_files"><h3><b>The project scripts</b></h3></a>
+
+  In the <b>project</b> directory are the scripts that control the simulation.  These scripts are:
+  <table class="code">
+    <tr><td><font color="red">project.py</font></td><td>Defines the input data used, where to place output, etc.</td></tr>
+    <tr><td><font color="red">build_elevation.py</font></td><td>Builds a PTS file of all elevation data specified by <font color="red">project.py</font></td></tr>
+    <tr><td><font color="red">setup_model.py</font></td><td>Prepares the simulation before actually running it</td></tr>
+    <tr><td><font color="red">run_model.py</font></td><td>Runs the simulation</td></tr>
+  </table>
+
+  <a name="project.py"><h4><b>project.py</b></h4></a>
+
+    This file is the heart of the simulation. The project script introduces all files that are necessary to run all accompanying scripts.
+    By changing one of the variables in this script the output could be completely different.
+    For further details on changing parameters see <a href="#change">Making changes to a simulation</a>.
+
+<!--  This file is the heart of the simulation.  Here we specify many things, including the tide level, the simulation
+  start and stop times, input data files, and so on.  Because we are using python as the programming language in
+  these files, we can use the power of the language to speed up our development.  We use this by <i>parameterising</i>
+  data as much as possible.
+  <p>
+  Parameters that you might change 
+  As an example, let's look at the <b>scenario_name</b> variable we define in <font color="red">project.py</font>:
+  <table class="code">
+    <tr><td>scenario_name = 'hobart'&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;# name of the scenario</td></tr>
+  </table>
+  <p>
+  We define this variable solely to quickly change other input filenames.  Where we want a different input files for
+  a different scenario, 
+  depending on whether we want a 'small' or 'large' model, we build the filenames using the <b>model</b> variable.
+  Some examples are:
+  <p>
+  <table class="code">
+    <tr height="25"><td>bounding_polygon_filename = 'bounding_polygon_'+ model + '.csv'</td></tr>
+    <tr height="25"><td>land_initial_conditions_filename = [['initial_conditions_' + model +'.csv', 0]]</td></tr>
+    <tr height="25"><td>landward_boundary_filename = 'landward_boundary_'+ model +'.csv'</td></tr>
+  </table>
+  <p>
+  We must, of course, ensure that there are input files <font color="red">bounding_polygon_small.csv</font>
+  and <font color="red">bounding_polygon_large.csv</font>, and so on.
+  <p>
+  Now, if we need to change the simulation model from 'small' to 'large', we need only change the
+  value of the <b>model</b> variable, and all the input files that depend on the model will change.
+  This speeds up development and make errors less likely.  If you want to add another model to the two 
+  we show above, just set <b>model</b> to 'medium' and create appropriate input files with the string
+  'medium' in the filename. -->
+
+  <a name="build_elevation.py"><h4><b>build_elevation.py</b></h4></a>
+
+  This script combines all input elevation files into one PTS file.
+  We have provided you with the PTS file used to create the outputs on this DVD.
+  If you would like to change the elevation see <a href="#change">Making changes to a simulation</a>. 
+  <p>
+
+  <a name="setup_model.py"><h4><b>setup_model.py</b></h4></a>
+
+  This script is used to transform data into a specific format for <font color="red">run_model.py</font>,
+  if required, and to generate warning messages if you are missing data.
+  <p>
+
+  <a name="run_model.py"><h4><b>run_model.py</b></h4></a>
+
+  This script runs a tsunami inundation scenario.  It relies on the parameters set in <font color="red">project.py</font>
+  as well as the PTS and STS files.
+  An STS file has been generated for each event listed in the boundaries directory. For further details on events see
+  <a href="#change">Making changes to a simulation</a>.
+  <p>
+
+  <a name="change"><h3><b>Making changes to a simulation</b></h3></a>
+
+  There are many parameters that you can change within the <font color="red">project.py</font> script,
+  but the following four parameters are those most commonly changed.
+  <p>
+
+  <a name="tide"><h4><b>Tide</b></h4></a>
+
+  The <b>tide</b> parameter is used to change the mean stage of the simulation.  When <b>tide</b> is set to 0
+  the initial water level will be at Mean Sea Level.  If you increase the <b>tide</b> value the water level will become deeper.
+  However land is masked out using initial conditions.  Within ANUGA <b>tide</b> is modelled as a constant.
+  <p>
+
+  <a name="events"><h4><b>Events</b></h4></a>
+
+  The <b>event_number</b> variable contains the event number that initiates the tsunami we are modelling.
+  You can change <b>event_number</b> to any event number in the anuga/boundaries directory.
+  As we said above, a new STS file must be generated for <font color="red">run_model.py</font> to work.
+  <p>
+  The event numbers correspond to a quake ID from the probabilistic tsunami hazard map of Australia.
+  <table class="code">
+    <tr><td><pre>event_number = 51436    # 1 in 10000 yr event from New Hebrides</pre></td></tr>
+  </table>
+  <p>
+
+  <a name="elevation"><h4><b>Elevation</b></h4></a>
+
+  Elevation data can be changed in the <font color="red">project.py</font> elevation script.
+  Elevation data can be read as either a point file, comma delimited, or as an ASCII grid file
+  (ASC) with an accompanying projection file (PRJ). All elevation input must be projected in the correct UTM zone.
+  <p>
+
+  A header for a CSV file has the format:
+  <table class="code">
+    <tr><td><pre>x,y,elevation</pre></td></tr>
+  </table>
+  <p>
+
+  An ASC file header has the format:
+  <table class="code">
+    <tr><td><pre>ncols         868
+nrows         856
+xllcorner     418933.86055096
+yllcorner     5151810.6668096
+cellsize      250
+NODATA_value  -9999</pre></td></tr>
+  </table>
+  <p>
+
+  The header of a PRJ file has the format:
+  <table class="code">
+    <tr><td><pre>Projection    UTM
+Zone          55
+Datum         D_GDA_1994
+Zunits        NO
+Units         METERS
+Spheroid      GRS_1980
+Xshift        500000
+Yshift        10000000
+Parameters</pre></td></tr>
+  </table>
+  <p>
+
+  The elevation filenames must be listed in either <b>point_filenames</b> or <b>ascii_grid_filenames</b>
+  depending on their format. Point files need to have their extension shown however the ascii grid files have the .asc extension assumed:
+  <table class="code">
+    <tr><td><pre>point_filenames = ['SD100031996_jgriffin_clip.csv',
+                   'tomaga_offshore_AHD_MGA_1997.csv',
+                   'hobart_BBHD_MGA_1995.csv',
+                   'hobart_AHD_MGA_2000.csv']
+
+ascii_grid_filenames = ['sd100031996_p',
+                        'sd100031996_p2',
+                        'sd100031996_p3',
+                        'sd100031996_p4']</pre></td></tr>
+  </table>
+  <p>
+
+  For further information on ANUGA file formats please see the ANUGA User Manual, section 6.1.
+  <p>
+
+  <a name="interior_regions"><h4><b>Interior regions</b></h4></a>
+
+  The <b>interior_regions</b> parameter allows you to change the mesh of the model.
+  <p>
+</body>
+</html>
