Changeset 7336


Ignore:
Timestamp:
Aug 7, 2009, 2:39:09 PM (13 years ago)
Author:
jgriffin
Message:

updated html pages to be consistent with other models

Location:
DVD_images/extra_files/Gosford
Files:
1 deleted
4 edited

Legend:

Unmodified
Added
Removed
  • DVD_images/extra_files/Gosford/analysis.html

    r7301 r7336  
    2727  from SWW files, but are offered as an example of one way to do it.
    2828  <p>
    29   This page describes the scripts and shows how to use them.  Note that due to the ad-hoc nature of the scripts, 
     29  This page describes the scripts and shows how to use them.  Note that due to the ad-hoc nature of the scripts,
    3030  you <b>must</b> modify these scripts before they can be used to extract information from any SWW files you
    3131  generate.
     
    3333  <a name="export_results_max.py scripts"><h3><b>export_results_max.py</b></h3></a>
    3434  The <font color="red">export_results_max.py</font> script can be used to create an ASC file that contains the maximum
    35   of an ANUGA variable or expression for each point in a user-defined raster on the simulation region.
     35  of an ANUGA variable or expression for each point in a user-defined ArcGIS grid on the simulation region.
    3636  <p>
    3737  You must change certain values within the <font color="red">export_results_max.py</font> file to get what you want:
    3838  <ul>
    39     <li> You must determine how many SWW files your simulation produced and create as many lines like this:
     39    <li> List the output folder names here, with one for each simulation you have run:
    4040<pre><font color="brown">    time_dir1 = '20090505_150430_run_final_0.8_58292_None_kvanputt'
    4141    time_dir2 = '20090505_150517_run_final_0_58292_None_kvanputt'</font></pre>
    42          as necessary.  Then modify the line:
     42         For information on  <a href="modifications.html#output">output_folder_name</a>.
     43  <p>Then modify the line:
    4344<pre><font color="brown">    time_dirs = [time_dir1, time_dir2]</font></pre>
    4445         to include each of the variables you defined above.
    45          <p>   
    46     <li> Your SWW output will have a name like <font color="red">gosford.sww</font>. For a large model you 
     46         <p>
     47    <li> Your SWW output will have a name like <font color="red">gosford.sww</font>. For a large model you
    4748         may have more than one output file with extra filenames like <font color="red">gosford_37860_0.sww</font>,
    48          where the <b>37860</b> tells us that the timestep at the start of this file is 37860 sec. The 
     49         where the <b>37860</b> tells us that the timestep at the start of this file is 37860 sec. The
    4950         <font color="red">export_results_max.py</font> script needs to examine all SWW output files, so we specify
    5051         all the files produced by the model run to create a maximum over the entire time.
    51          We do this by specifying the start times of all the extra SWW files:
    52          <p>   
    53 <pre><font color="brown">    times = [37860]</font></pre>
     52         We do this by specifying the start times of all the extra SWW files:
    5453         <p>
    55          Note we do not have to specify the first SWW file, only the extra file start times. If there are no extra SWW files,
    56          just do:
    57          <p>   
     54<pre><font color="brown">    times = [37860] <font color="black"> or </font>
     55    times = [20000, 40000, 60000]</font></pre>
     56         <p>
     57         <i>Note we do not have to specify the first SWW file, only the extra file start times. If there are no extra SWW files,
     58         just do:</i>
     59         <p>
    5860<pre><font color="brown">    times = []</font></pre>
    5961         <p>
    60     <li> Modify the <b>cellsize</b> value to set the size of the raster you require.  For example:
    61 <pre><font color="brown">    cellsize = 20              # raster cell size in metres</font></pre>
    62          <p>   
    63     <li> You can get the maximum of a variable or expression over the entire model time, or for a single time in the simulation.
     62    <li> Modify the <b>cellsize</b> value to set the size of the ArcGIS grid you require.  For example:
     63<pre><font color="brown">    cellsize = 20              # ArcGIS grid cell size in metres</font></pre>
     64         <p>
     65         <i>Note: That this value should not go beyond the most refined part of the mesh
     66         i.e. if mesh resolution is 500m<sup>2</sup>, cellsize = (500 </i>x<i> 2)<sup>1/2</sup> = 32m</i>
     67         <p>
     68    <li> You can get the maximum of a variable or expression over the entire model time, or for a single time in the simulation.
    6469         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
    65          the maximum values in the raster over all timesteps:
     70         the maximum values over all timesteps:
    6671<pre><font color="brown">    timestep = None  # over all timesteps
    6772    #timestep = 0</font></pre>
    68          <p>         
    69          Note that if you want the elevation use <b>timestep = 0</b>. Elevation does not change over time and you only need the
    70          first SWW file.               
    7173         <p>
    72     <li> If you want to clip the raster to one or more small regions then put the names of the regions of interest
     74         <i>Note that if you want the elevation use <b>timestep = 0</b>. Elevation does not change over time and you only need the
     75         first SWW file.</i>
     76         <p>
     77    <li> If you want to clip the ArcGIS grid to one or more small regions then put the names of the regions of interest
    7378         into the <b>area</b> list:
    74 <pre><font color="brown">    area = ['Batemans_Bay', 'NW', 'South']</font></pre>
    75          Note that the name strings you put into the <b>area</b> list must match the names used in the
     79<pre><font color="brown">    area = ['gosford', 'NW', 'South']</font></pre>
     80         <p>
     81         <i>Note that the name strings you put into the <b>area</b> list must match the names used in the
    7682         <font color="red">project.py</font> file.  That is, if you use a name such as 'NW', then the
    77          <font color="red">project.py</font> file must have lines like:
     83         <font color="red">project.py</font> file must have lines like:</i>
    7884<pre><font color="brown">    xminNW = 548000
    7985    xmaxNW = 561000
     
    8591<pre><font color="brown">    area = ['All']             # no region of interest</font></pre>
    8692         <p>
    87     <li> Finally you must decide which variable or expression values you want sampled on your raster.
     93    <li> Finally you must decide which variable or expression values you want sampled on your ArcGIS grid.
    8894         Define a list <b>var</b> that contains strings defining the required variable or expression:
    8995<pre><font color="brown">    var = ['depth', 'speed']</font></pre>
    90          Note that the strings you supply must be defined in the <b>var_equations</b> dictionary
    91          prior to your definition of <b>var</b>:
     96         <i>Note that the strings you supply must be defined in the <b>var_equations</b> dictionary
     97         prior to your definition of <b>var</b>:</i>
    9298<pre><font color="brown">    var_equations = {'stage':     'stage',
    9399                     'momentum':  '(xmomentum**2 + ymomentum**2)**0.5',
     
    100106  <a name="get_timeseries.py"><h3><b>get_timeseries.py</b></h3></a>
    101107  The <font color="red">get_timeseries.py</font> script is used to get timeseries data for a selection of variable
    102   data at one or more gauge points in a simulation.
     108  data at one or more timeseries gauge points in a simulation.
    103109  <p>
    104110  You must change certain values within the <font color="red">get_timeseries.py</font> file to get what you want:
    105111  <ul>
    106     <li> You must determine how many SWW files your simulation produced and create as many lines like this:
     112    <li> Depending on how many simulations you have run will determine the number of output folder names you insert here:
    107113<pre><font color="brown">    time_dir1 = '20090505_150430_run_final_0.8_58292_None_kvanputt'
    108114    time_dir2 = '20090505_150517_run_final_0_58292_None_kvanputt'</font></pre>
     
    111117         to include each of the variables you defined above.
    112118         <p>
    113     <li> Make sure that the <b>gauges</b> list in <font color="red">projects.py</font> contains one or more CSV files
     119    <li> Make sure that the <b>gauges</b> list specified in <font color="red">projects.py</font> contains one or more CSV files
    114120         defining the gauges within the simulation that you want the timeseries data for.
    115121         The gauge file must have this format:
  • DVD_images/extra_files/Gosford/index.html

    r7300 r7336  
    2323
    2424  <a name="introduction"><h3><b>Introduction</b></h3></a>
    25 
    26   The information on this DVD and the associated report is intended to assist emergency managers in developing preparation and
    27   response plans that can be used during a tsunami threat or emergency.
    28   <p>
    29   The Attorney General's Department (AGD) has supported Geoscience Australia (GA) in developing a range of products to support
    30   the understanding of tsunami hazard through the Australian Probabilistic Tsunami Warning System Project. The work reported here is intended
    31   to further build the capacity of the Jurisdictions in developing inundation models for prioritised locations.
     25  The information within this DVD is intended to assist emergency managers in tsunami planning and preparation
     26  activities. The Australian Government Attorney General’s Department (AGD) has supported Geoscience Australia (GA) in developing a
     27  range of products to support the understanding of tsunami hazard through the Australian Tsunami Warning System Project. The work
     28  reported here is intended to further build the capacity of the New South Wales (NSW) State Government in developing inundation models for
     29  prioritised locations.
    3230  <p>
    3331  While the associated report provides background, model results and interpretations, the DVD contains all data, scripts and
    34   software necessary to reproduce and potentially augment the models underpinning the report. This will allow the Jurisdiction
     32  instructions for installing software necessary to reproduce and potentially augment the models underpinning the report. This will allow the NSW State Government
    3533  to rerun the models with minor modifications or new elevation data as needed and also potentially replicate the methodology
    36   to other locations within the model extent, if desired. 
     34  for other locations within the model extent, if desired.
    3735  <p>
    3836  The data provided on this DVD is:
    3937  <ul>
    40     <li> The Professional Opinion Report 2009/XX entitled <blink><i><a href="documents/not_there.pdf">Capacity Building for Tsunami Planning and Preparation:
    41          Inundation Models for Four East Coast Australian Communities</a> <b><font color="red">UNFINISHED</font></b></i></blink>
    42     <li>  <a href="documents/Figures">Figures</a> of maximum inundation and maximum speed
    43     <li> Generated <a href="data/new_south_wales/gosford_tsunami_scenario_2009/anuga/outputs">Arc grids</a> of maximum inundation and maximum speed for the areas of interest
    44     <li> Generated <a href="data/new_south_wales/gosford_tsunami_scenario_2009/anuga/outputs">timeseries</a> from the models
     38    <li> The Professional Opinion Report 2009/07 entitled <blink><i><a href="documents/PO_2009_09.pdf">Capacity building for tsunami planning and preparation:
     39         inundation models for two New South Wales communities</a></i></blink>
     40    <li>  <a href="documents/Figures">Figures</a> of maximum inundation depth and maximum flow speed
     41    <li> <a href="data/new_south_wales/gosford_tsunami_scenario_2009/anuga/outputs">Model outputs</a> including:
     42    <ul>
     43      <li>ArcGIS grids of maximum inundation depth and maximum flow speed for the areas of interest
     44      <li>CSV files containing timeseries for specific locations in the models
     45      <li>ArcGIS grid of the resulting elevation generated by the model software <a href="https://datamining.anu.edu.au/anuga">ANUGA</a></ul>
    4546    <li> Combined <a href="data/new_south_wales/gosford_tsunami_scenario_2009/anuga/topographies">elevation data</a> used by the simulation
    46     <li> The <a href="data/new_south_wales/gosford_tsunami_scenario_2009/anuga/outputs/elevation">Arc grid</a> of the resulting elevation generated by ANUGA
    47     <li> The Python scripts used to run the models
     47    <li> The <a href="project">Python scripts</a> used to run the models
    4848  </ul>
    4949  <p>
    50   The tsunami wave data on this disk are all derived from events available in the Australian Tsunami
    51   Hazard Map. As this dataset is very large, this DVD only contains the events
     50  The input tsunami wave data on this disk are all derived from events available in the Probabilistic Tsunami Hazard Assessment (PTHA) for Australia. As this dataset is very large, this DVD only contains the events
    5251  described in the report.
    5352
  • DVD_images/extra_files/Gosford/installation.html

    r7301 r7336  
    3131
    3232  The tsunami inundation simulations are based on the Open Source software package called ANUGA.
    33   For more information about ANUGA visit <a href="https://datamining.anu.edu.au/anuga">https://datamining.anu.edu.au/anuga</a>. 
     33  For more information about ANUGA visit <a href="https://datamining.anu.edu.au/anuga">https://datamining.anu.edu.au/anuga</a>.
    3434  <p>
    35   ANUGA has been developed and tested under the Windows XP and Linux (Ubuntu, Mint and Red Hat) operating systems. 
     35  ANUGA has been developed and tested under the Windows XP and Linux (Ubuntu, Mint and Red Hat) operating systems.
    3636  ANUGA may also be installed on a Windows Vista system and Debian Linux, but these have not been extensively tested.
    3737  <p>
     
    4040
    4141  <a name="installing"><h3><b>Installing ANUGA</b></h3></a>
    42 
     42  <a href="http://sourceforge.net/projects/anuga/">Download Software</a><i>: please note Internet Explorer has the habit of renaming the
     43  .tgz file to .gz - the remedy is to rename them back or use another browser such as Firefox.</i>
     44  <p>
    4345  You must install ANUGA according to the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
    4446  As the installation procedure comprises a number of steps we suggest that it is carried out by someone with a
    45   basic understanding of how to install software packages on the operating system of choice. 
     47  basic understanding of how to install software packages on the operating system of choice.
    4648
    4749  <a name="simulating"><h3><b>How to run a simulation</b></h3></a>
     
    5254  can be used to get help.
    5355  <p>
    54  
     56
    5557  <p>
    5658  <hr align="left" width="100">
     
    6163  <hr align="left" width="100">
    6264  <p>
    63   Next, you must copy the entire contents of the DVD to a place in your filesystem. Let's assume
    64   that you want to put the data into <b>C:\ANUGA</b>. You would do this in a Command Prompt window:
    65   <table class="code"><tr><td>
    66     C:<br>
    67     cd \<br>
    68     mkdir ANUGA<br>
     65  Next, you must copy the entire contents of the DVD to a place in your file system. Let's assume
     66  that you want to put the data into <b>C:\ANUGA</b>. You could drag all files from the DVD into this folder with Explorer.
     67  Or through the Command Prompt window:
     68  <pre><font color="brown">
     69    C:
     70    cd
     71    mkdir ANUGA
    6972    xcopy /e X:\ ANUGA
    70   </td></tr></table>
    71   <p>
    72   Of course, you could just drag all files on the DVD (X:\ is the assumed drive letter) to the desired target directory with Explorer.
     73  </font></pre>
     74  X:\ is the assumed to be the CD drive letter.
    7375  <p>
    7476  <hr align="left" width="100">
    7577  <p>
    7678  Now you must create an environment variable <b>ANUGADATA</b> that points to the directory you just created:
    77   <table class="code"><tr><td>
     79  <pre><font color="brown">
    7880    set ANUGADATA=C:\ANUGA
    79   </td></tr></table>
    80   <p>
     81  </font></pre>
    8182  Doing the above in a Command Prompt window is temporary - if you open another
    8283  window you will not have the ANUGADATA environment variable defined. To make
     
    8485  tool (<b>Advanced</b> tab).  See the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>
    8586  if you don't know how to do this.
    86   <p>
    8787  <hr align="left" width="100">
    88   <p>
    8988  Next, you prepare and execute the model:
    90   <table class="code"><tr><td>
    91     cd C:\ANUGA<br>
    92     cd project<br>
    93     python setup_model.py<br >
     89  <pre><font color="brown">
     90    cd C:\ANUGA
     91    cd project
     92    python setup_model.py
    9493    python run_model.py
    95   </td></tr></table>
    96   <p>
     94  </font></pre>
    9795  <hr align="left" width="100">
    98   <p>
    9996  This should all run to completion though it may take several days, depending on
    10097  the hardware used.
     
    105102  drilling down from that point until you find a directory called <b>outputs</b>.
    106103  The latest directory in <b>outputs</b> should contain a file called <font color="red">screen_error.txt</font>
    107   with an explanation of the error at the end. 
     104  with an explanation of the error at the end.
    108105  <p>
    109106  Once the simulation has completed you may view the results using the ANUGA
    110   viewer as described in the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a> 
     107  viewer as described in the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>
    111108  and <a href="documents/anuga_user_manual.pdf">User Manual</a>.  You may also
    112109  generate rasters suitable for GIS mapping or write dedicated scripts extracting timeseries at selected
     
    120117  After you have run a simulation you may wish to extract information from the generated SWW file.
    121118  On this disk there are a selection of example analysis scripts that you can use or modify.
    122   The <a href="analysis.html">analysis scripts</a> page explains how to use the scripts.
     119  The <a href="analysis.html">analysis</a> page explains how to use the scripts.
    123120
    124121  <a name="modifications"><h3><b>How to modify a simulation</b></h3></a>
     
    138135  <a name="FAQ"><h3><b>Frequently Asked Questions</b></h3></a>
    139136
    140   There is a <b>Frequently Asked Questions</b> (FAQ) page at
    141   <a href="https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions">https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions</a>.
    142   Look in there and search the mailing list archives before asking questions on the ANUGA user's mailing list.
    143   Someone may already have asked your question!
     137  Look in <b><a href="https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions">Frequently Asked Questions</a></b> (FAQ) and search the mailing list archives before asking questions on the ANUGA user's mailing list.
     138  Someone may already have asked and answered your question!
    144139  <p>
    145140  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
  • DVD_images/extra_files/Gosford/modifications.html

    r7301 r7336  
    2424  <a name="modifications"><h2><b>Modifying a simulation</b></h2></a>
    2525
    26   Here we talk about how you change a simulation.  Why would you need to change a simulation?  Well,
     26  Here we talk about how to change a simulation.  Why would you need to change a simulation?  Well,
    2727  you might have some better elevation data, you want to run the simulation on a finer mesh in certain
    2828  areas, or maybe you want to see the result for different events.
    2929  <p>
    30   First we describe the uses of the script files you might change, then we walk through a few examples
     30  First we describe the usage of the script files you might change, then we walk through a few examples
    3131  of changes you might make.
    3232  <p>
     
    3737  <table class="code">
    3838    <tr><td><font color="red">project.py</font></td><td>Defines the input data used, where to place output, etc.</td></tr>
    39     <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>
     39    <tr><td><font color="red">build_elevation.py</font></td><td>Combines the elevation data specified by <font color="red">project.py</font> into one file; with the extension .PTS</td></tr>
    4040    <tr><td><font color="red">setup_model.py</font></td><td>Prepares the simulation before actually running it</td></tr>
    4141    <tr><td><font color="red">run_model.py</font></td><td>Runs the simulation</td></tr>
     
    4848    For further details on changing parameters see <a href="#change">Making changes to a simulation</a>.
    4949
    50 <!--  This file is the heart of the simulation.  Here we specify many things, including the tide level, the simulation
    51   start and stop times, input data files, and so on.  Because we are using python as the programming language in
    52   these files, we can use the power of the language to speed up our development.  We use this by <i>parameterising</i>
    53   data as much as possible.
    54   <p>
    55   Parameters that you might change
    56   As an example, let's look at the <b>scenario_name</b> variable we define in <font color="red">project.py</font>:
    57   <table class="code">
    58     <tr><td>scenario_name = 'hobart'&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;# name of the scenario</td></tr>
    59   </table>
    60   <p>
    61   We define this variable solely to quickly change other input filenames.  Where we want a different input files for
    62   a different scenario,
    63   depending on whether we want a 'small' or 'large' model, we build the filenames using the <b>model</b> variable.
    64   Some examples are:
    65   <p>
    66   <table class="code">
    67     <tr height="25"><td>bounding_polygon_filename = 'bounding_polygon_'+ model + '.csv'</td></tr>
    68     <tr height="25"><td>land_initial_conditions_filename = [['initial_conditions_' + model +'.csv', 0]]</td></tr>
    69     <tr height="25"><td>landward_boundary_filename = 'landward_boundary_'+ model +'.csv'</td></tr>
    70   </table>
    71   <p>
    72   We must, of course, ensure that there are input files <font color="red">bounding_polygon_small.csv</font>
    73   and <font color="red">bounding_polygon_large.csv</font>, and so on.
    74   <p>
    75   Now, if we need to change the simulation model from 'small' to 'large', we need only change the
    76   value of the <b>model</b> variable, and all the input files that depend on the model will change.
    77   This speeds up development and make errors less likely.  If you want to add another model to the two
    78   we show above, just set <b>model</b> to 'medium' and create appropriate input files with the string
    79   'medium' in the filename. -->
    80 
    8150  <a name="build_elevation.py"><h4><b>build_elevation.py</b></h4></a>
    8251
    83   This script combines all input elevation files into one PTS file.
     52  This script combines all input elevation files into a single elevation point file (PTS file).
    8453  We have provided you with the PTS file used to create the outputs on this DVD.
    85   If you would like to change the elevation see <a href="#change">Making changes to a simulation</a>.
     54  If you would like to change the elevation, see <a href="#change">Making changes to a simulation</a>.
    8655  <p>
    8756
     
    9564
    9665  This script runs a tsunami inundation scenario.  It relies on the parameters set in <font color="red">project.py</font>
    97   as well as the PTS and STS files.
    98   An STS file has been generated for each event listed in the boundaries directory. For further details on events see
     66  as well as the elevation and event input files (PTS and STS files respectively).
     67  An STS file has been generated for each event listed in the <u>boundaries</u> directory. For further details on events see
    9968  <a href="#change">Making changes to a simulation</a>.
    10069  <p>
     
    10675  <p>
    10776
     77  <a name="output"><h4><b>Output Folder Name</b></h4></a>
     78
     79  The <b>output folder name</b> should be unique between different runs on different data.
     80  The list of items below will be used to create the folder in your <u>output</u> directory.
     81  Your user name and time+date will be automatically added.  For example,
     82  <pre><font color="brown">
     83  output_comments = [setup, tide, event_number]</font></pre>
     84  will result in a folder name like
     85  <pre><font color="brown">
     86  20090212_091046_run_final_0_27283_rwilson</font>
     87Where you (<u>rwilson</u>) ran a <u>run</u> script at <u>9:10.46</u> in the morning on the <u>2/12/09</u>, <b>setup</b> = <u>final</u>,
     88<b>tide</b> = <u>0</u>, <b>event_number</b> = <u>27283</u>  - refer below for more information on these parameters </pre>
     89  <p>
     90  You can also add strings to this list
     91  <pre><font color="brown">
     92  output_comments = [setup, tide, event_number, 'large']</font></pre>
     93  will result in a folder name like
     94  <pre><font color="brown">
     95  20090212_091046_run_final_0_27283_large_rwilson</font></pre>
     96  <p>
     97  <p>
     98    <a name="setup"><h4><b>Setup</b></h4></a>
     99
     100  The <b>setup</b> parameter determines the type of run. This can be one of three values:
     101  <pre><font color="brown">
     102  'trial' <font color="black">- coarsest mesh, fast </font>
     103  'basic' <font color="black">- coarse mesh</font>
     104  'final' <font color="black">- fine mesh, slowest</font>
     105  </pre></font>
     106  Note: <b>'final'</b> must be used if determining the best estimate of inundation for your area of interest.
     107  <p>
    108108  <a name="tide"><h4><b>Tide</b></h4></a>
    109109
    110   The <b>tide</b> parameter is used to change the mean stage of the simulation.  When <b>tide</b> is set to 0
     110  The <b>tide</b> parameter is used to change the mean inital water level of the simulation.  When <b>tide</b> is set to 0
    111111  the initial water level will be at Mean Sea Level.  If you increase the <b>tide</b> value the water level will become deeper.
    112   However land is masked out using initial conditions.  Within ANUGA <b>tide</b> is modelled as a constant.
     112  This setting will also increase non tidal lakes and rivers inside the model.  To compensate a mask is used on land called
     113  <b>initial conditions</b> which brings the internal water bodies back to 0.  Within ANUGA <b>tide</b> is modelled as a constant.
    113114  <p>
    114115
     
    116117
    117118  The <b>event_number</b> variable contains the event number that initiates the tsunami we are modelling.
    118   You can change <b>event_number</b> to any event number in the anuga/boundaries directory.
    119   As we said above, a new STS file must be generated for <font color="red">run_model.py</font> to work.
    120   <p>
    121   The event numbers correspond to a quake ID from the probabilistic tsunami hazard map of Australia.
    122   <table class="code">
    123     <tr><td><pre>event_number = 51436    # 1 in 10000 yr event from New Hebrides</pre></td></tr>
    124   </table>
     119  You can change <b>event_number</b> to any event number in the <u>boundaries</u> directory.
     120  An STS file has been generated for all events listed in the <u>boundaries</u> directory.
     121  <p>
     122  The event numbers correspond to a quake ID from the Probabilistic Tsunami Hazard Map Assessment of Australia.
     123
     124  <pre><font color="brown">
     125  event_number = 51436    # 1 in 10000 yr event from New Hebrides</font></pre>
     126
    125127  <p>
    126128
    127129  <a name="elevation"><h4><b>Elevation</b></h4></a>
    128130
    129   Elevation data can be changed in the <font color="red">project.py</font> elevation script.
     131  Elevation data can be changed in the <font color="red">project.py</font> script under ELEVATION DATA.
    130132  Elevation data can be read as either a point file, comma delimited, or as an ASCII grid file
    131   (ASC) with an accompanying projection file (PRJ). All elevation input must be projected in the correct UTM zone.
     133  (ASC) with an accompanying projection file (PRJ). All elevation input should sit in <u>topographies</u> and must be projected in the correct UTM zone.
    132134  <p>
    133135
    134136  A header for a CSV file has the format:
    135   <table class="code">
    136     <tr><td><pre>x,y,elevation</pre></td></tr>
    137   </table>
     137
     138    <pre><font color="brown">
     139  x,y,elevation</font></pre>
     140
    138141  <p>
    139142
    140143  An ASC file header has the format:
    141   <table class="code">
    142     <tr><td><pre>ncols         868
    143 nrows         856
    144 xllcorner     418933.86055096
    145 yllcorner     5151810.6668096
    146 cellsize      250
    147 NODATA_value  -9999</pre></td></tr>
    148   </table>
     144
     145    <pre><font color="brown">
     146  ncols         868
     147  nrows         856
     148  xllcorner     418933.86055096
     149  yllcorner     5151810.6668096
     150  cellsize      250
     151  NODATA_value  -9999</font></pre>
     152
    149153  <p>
    150154
    151155  The header of a PRJ file has the format:
    152   <table class="code">
    153     <tr><td><pre>Projection    UTM
    154 Zone          55
    155 Datum         D_GDA_1994
    156 Zunits        NO
    157 Units         METERS
    158 Spheroid      GRS_1980
    159 Xshift        500000
    160 Yshift        10000000
    161 Parameters</pre></td></tr>
    162   </table>
    163   <p>
    164 
    165   The elevation filenames must be listed in either <b>point_filenames</b> or <b>ascii_grid_filenames</b>
     156
     157    <pre><font color="brown">
     158  Projection    UTM
     159  Zone          56
     160  Datum         D_GDA_1994
     161  Zunits        NO
     162  Units         METERS
     163  Spheroid      GRS_1980
     164  Xshift        500000
     165  Yshift        10000000
     166  Parameters</font></pre>
     167
     168  <p>
     169
     170  The elevation filenames in <font color="red">project.py</font> must be listed in either <b>point_filenames</b> or <b>ascii_grid_filenames</b>
    166171  depending on their format. Point files need to have their extension shown however the ascii grid files have the .asc extension assumed:
    167   <table class="code">
    168     <tr><td><pre>point_filenames = ['SD100031996_jgriffin_clip.csv',
    169                    'tomaga_offshore_AHD_MGA_1997.csv',
    170                    'gosford_BBHD_MGA_1995.csv',
    171                    'gosford_AHD_MGA_2000.csv']
    172 
    173 ascii_grid_filenames = ['sd100031996_p',
    174                         'sd100031996_p2',
    175                         'sd100031996_p3',
    176                         'sd100031996_p4']</pre></td></tr>
    177   </table>
     172
     173    <pre><font color="brown">
     174  point_filenames = ['point1.csv',
     175                     'point2.csv',
     176                     'point3.csv']
     177
     178  ascii_grid_filenames = ['grid1',
     179                          'grid2',
     180                          'grid3']</font></pre>
     181
    178182  <p>
    179183
     
    183187  <a name="interior_regions"><h4><b>Interior regions</b></h4></a>
    184188
    185   The <b>interior_regions</b> parameter allows you to change the mesh of the model.
     189  The user can specify a number of internal polygons within each of which the resolution of the mesh can be specified.
     190  Mesh resolution is the maximum allowable area specified for each region, defining the largest area an indivdual
     191  triangular element of the mesh can take (and therefore the minimum mesh resolution).
     192  These polygons need to be nested within each other with no overlapping edges.
     193  <p>
     194  The <b>interior regions</b> can be changed in the <font color="red">project.py</font> script under INTERIOR REGIONS.
     195  Interior regions can be read as either seperate CSV files for each polygon displayed as a listed paired with its
     196  resolution and/or one CSV file for all polygons, where its resolution is defined within the csv under 'id'.
     197  All file inputs should sit in <u>polygons</u> and must be projected in the correct UTM zone.
     198  <p>
     199  The format for a CSV file with ONE polygon has the format:
     200  <pre><font color="brown">
     201  easting,northing  </font><font color="black"> Note: NO Header  </font></pre>
     202
     203
     204  The header for a CSV file with MANY polygons has the format:
     205  <pre><font color="brown">
     206  easting,northing,id,value</font></pre>
     207  <p>
     208  Where id = polygon number and value = maximum allowable area.
     209  <p>
     210  The <font color="red">project.py</font> script for this section looks like this:
     211
     212
     213  <pre><font color="brown">
     214  interior_regions_list = [['aos1.csv', 1500],
     215                           ['aos2.csv', 1500],
     216                           ['sw.csv', 30000]]
     217  interior_regions_multiple_csv = 'PriorityAreas.csv'</font></pre>
     218
     219  <p>
     220
     221  For further information on ANUGA file formats please see the ANUGA User Manual, section 5.1.
    186222  <p>
    187223</body>
    188224</html>
     225
Note: See TracChangeset for help on using the changeset viewer.