Changeset 7300


Ignore:
Timestamp:
Jul 3, 2009, 4:47:17 PM (15 years ago)
Author:
rwilson
Message:
 
Location:
DVD_images
Files:
18 edited

Legend:

Unmodified
Added
Removed

  • DVD_images/Jonos_README.txt

    r7205 r7300  
    3939# To include new data please prepare data in the same formats as those above.
    4040# For further information on ANUGA file formats please see the ANUGA User Maunal section 6.1
     41
     42Interior regions

  • DVD_images/extra_files/BatemansBay/analysis.html

    r7265 r7300  
    3939    <li> You must determine how many SWW files your simulation produced and create as many lines like this:
    4040<pre><font color="brown">    time_dir1 = '20090505_150430_run_final_0.8_58292_None_kvanputt'
    41     time_dir2 = '20090505_150517_run_final_0_58292_None_kvanputt'
    42     time_dir3 = '20090505_150711_run_final_0_58280_None_kvanputt'
    43     time_dir4 = '20090505_150805_run_final_0.8_58280_None_kvanputt'
    44     time_dir5 = '20090505_151322_run_final_0.8_64477_None_kvanputt'
    45     time_dir6 = '20090505_151447_run_final_0_64477_None_kvanputt'</font></pre>
     41    time_dir2 = '20090505_150517_run_final_0_58292_None_kvanputt'</font></pre>
    4642         as necessary.  Then modify the line:
    47 <pre><font color="brown">    time_dirs = [time_dir1, time_dir2, time_dir3, time_dir4, time_dir5, time_dir6]</font></pre>
     43<pre><font color="brown">    time_dirs = [time_dir1, time_dir2]</font></pre>
    4844         to include each of the variables you defined above.
    49 
     45         <p>   
     46    <li> Your SWW output will have a name like <font color="red">batemans_bay.sww</font>. For a large model you
     47         may have more than one output file with extra filenames like <font color="red">batemans_bay_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         <font color="red">export_results_max.py</font> script needs to examine all SWW output files, so we specify
     50         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>
     54         <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>   
     58<pre><font color="brown">    times = []</font></pre>
     59         <p>
    5060    <li> Modify the <b>cellsize</b> value to set the size of the raster you require.  For example:
    5161<pre><font color="brown">    cellsize = 20              # raster cell size in metres</font></pre>
    52 
    53     <li> Now set the timestep at which you want the raster generated.  Either set the actual timestep required or use
    54          <b>None</b> to indicate that you want the maximum values in the raster over all timesteps:
    55 <pre><font color="brown">    timestep = 1000
    56     #timestep = None            # over all timesteps</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.
     64         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:
     66<pre><font color="brown">    timestep = None  # over all timesteps
     67    #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.               
    5771         <p>
    58          Note that if you specify a particular timestep here you may not need to include all SWW files in the
    59          <b>time_dirs</b> list above.  For example, if you wanted data from timestep 0 only then you would need
    60          to include only the first SWW file in the list.
    61 
    6272    <li> If you want to clip the raster to one or more small regions then put the names of the regions of interest
    6373         into the <b>area</b> list:
    64 <pre><font color="brown">    area = ['Hobart', 'NW', 'South']</font></pre>
     74<pre><font color="brown">    area = ['Batemans_Bay', 'NW', 'South']</font></pre>
    6575         Note that the name strings you put into the <b>area</b> list must match the names used in the
    6676         <font color="red">project.py</font> file.  That is, if you use a name such as 'NW', then the
    … …  
    7484         If you don't want to clip to a region of interest, then do this:
    7585<pre><font color="brown">    area = ['All']             # no region of interest</font></pre>
    76 
    77     <li> Now you must decide which variable or expression values you want sampled on your raster.
    78          Define a list <b>var</b> that contains strings defining the required variable/expression:
     86         <p>
     87    <li> Finally you must decide which variable or expression values you want sampled on your raster.
     88         Define a list <b>var</b> that contains strings defining the required variable or expression:
    7989<pre><font color="brown">    var = ['depth', 'speed']</font></pre>
    8090         Note that the strings you supply must be defined in the <b>var_equations</b> dictionary
    … …  
    96106    <li> You must determine how many SWW files your simulation produced and create as many lines like this:
    97107<pre><font color="brown">    time_dir1 = '20090505_150430_run_final_0.8_58292_None_kvanputt'
    98     time_dir2 = '20090505_150517_run_final_0_58292_None_kvanputt'
    99     time_dir3 = '20090505_150711_run_final_0_58280_None_kvanputt'
    100     time_dir4 = '20090505_150805_run_final_0.8_58280_None_kvanputt'
    101     time_dir5 = '20090505_151322_run_final_0.8_64477_None_kvanputt'
    102     time_dir6 = '20090505_151447_run_final_0_64477_None_kvanputt'</font></pre>
     108    time_dir2 = '20090505_150517_run_final_0_58292_None_kvanputt'</font></pre>
    103109         as necessary.  Then modify the line:
    104 <pre><font color="brown">    time_dirs = [time_dir1, time_dir2, time_dir3, time_dir4, time_dir5, time_dir6]</font></pre>
     110<pre><font color="brown">    time_dirs = [time_dir1, time_dir2]</font></pre>
    105111         to include each of the variables you defined above.
    106 
     112         <p>
    107113    <li> Make sure that the <b>gauges</b> list in <font color="red">projects.py</font> contains one or more CSV files
    108114         defining the gauges within the simulation that you want the timeseries data for.
     115         The gauge file must have this format:
     116<pre><font color="brown">    easting,northing,name,elevation
     117    559134.8963,5251176.875,Connelly,2
     118    532441.5164,5239639.686,Opossum,2</font></pre>
    109119  </ul>
    110120</body>

  • DVD_images/extra_files/BatemansBay/index.html

    r7265 r7300  
    3434  software necessary to reproduce and potentially augment the models underpinning the report. This will allow the Jurisdiction
    3535  to rerun the models with minor modifications or new elevation data as needed and also potentially replicate the methodology
    36   to other locations if desired. 
     36  to other locations within the model extent, if desired. 
    3737  <p>
    3838  The data provided on this DVD is:
    3939  <ul>
    40     <li> The Professional Opinion Report 2009/XX entitled <i>Capacity Building for Tsunami Planning and Preparation:
    41          Inundation Models for Four East Coast Australian Communities</i>
    42     <li> Elevation data used with the tsunami inundation model
    43     <li> Input data for a range of tsunami events
     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/batemans_bay_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/batemans_bay_tsunami_scenario_2009/anuga/outputs">timeseries</a> from the models
     45    <li> Combined <a href="data/new_south_wales/batemans_bay_tsunami_scenario_2009/anuga/topographies">elevation data</a> used by the simulation
     46    <li> The <a href="data/new_south_wales/batemans_bay_tsunami_scenario_2009/anuga/outputs/elevation">Arc grid</a> of the resulting elevation generated by ANUGA
    4447    <li> The Python scripts used to run the models
    4548  </ul>
    4649  <p>
    47   The input wave data on this disk are all derived from events available in the Australian Tsunami
     50  The tsunami wave data on this disk are all derived from events available in the Australian Tsunami
    4851  Hazard Map. As this dataset is very large, this DVD only contains the events
    4952  described in the report.
    5053
    51   <a name="requirements"><h3><b>Requirements</b></h3></a>
     54  <a name="requirements"><h3><b>Report Figures</b></h3></a>
    5255
    53   The tsunami inundation simulations are based on the Open Source software package called ANUGA.
    54   For more information about ANUGA visit <a href="https://datamining.anu.edu.au/anuga">https://datamining.anu.edu.au/anuga</a>.
    55   <p>
    56   ANUGA has been developed and tested under the Windows XP and Linux (Ubuntu, Mint and Red Hat) operating systems. 
    57   ANUGA may also be installed on a Windows Vista system and Debian Linux, but these have not been extensively tested.
    58   <p>
    59   The ANUGA scripts on this DVD require a minimum of 3GB of memory and possibly more, if mesh resolutions are increased. For this reason
    60   we recommend using 64 bit Ubuntu Linux as this operating system can use more than 3GB of memory, whereas Windows XP cannot.
     56  The figures from the report may be found <a href="documents/Figures">here</a>.
    6157
    62   <a name="installing"><h3><b>Installing ANUGA</b></h3></a>
     58  <a name="installation"><h3><b>Simulation Installation and Usage</b></h3></a>
    6359
    64   You must install ANUGA according to the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
    65   As the installation procedure comprises a number of steps we suggest that it is carried out by someone with a
    66   basic understanding of how to install software packages on the operating system of choice.
     60  Information for installing and using the simulation is <a href="installation.html">here</a>.
    6761
    68   <a name="simulating"><h3><b>How to run a simulation</b></h3></a>
    69 
    70   This is how you should run the model on this DVD.
    71   We assume that you are using Windows and will give examples for that operating system.
    72   The translation to Linux should be obvious, but the <a href="#userslist">ANUGA user's mailing list</a>
    73   can be used to get help.
    74   <p>
    75  
    76   <p>
    77   <hr align="left" width="100">
    78   <p>
    79   First, it is assumed you have installed the ANUGA software according to the
    80   <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
    81   <p>
    82   <hr align="left" width="100">
    83   <p>
    84   Next, you must copy the entire contents of the DVD to a place in your filesystem. Let's assume
    85   that you want to put the data into <b>C:\ANUGA</b>. You would do this in a Command Prompt window:
    86   <table class="code"><tr><td>
    87     C:<br>
    88     cd \<br>
    89     mkdir ANUGA<br>
    90     xcopy /e X:\ ANUGA
    91   </td></tr></table>
    92   <p>
    93   Of course, you could just drag all files on the DVD (X:\ is the assumed drive letter) to the desired target directory with Explorer.
    94   <p>
    95   <hr align="left" width="100">
    96   <p>
    97   Now you must create an environment variable <b>ANUGADATA</b> that points to the directory you just created:
    98   <table class="code"><tr><td>
    99     set ANUGADATA=C:\ANUGA
    100   </td></tr></table>
    101   <p>
    102   Doing the above in a Command Prompt window is temporary - if you open another
    103   window you will not have the ANUGADATA environment variable defined. To make
    104   the variable permanent you must set it in the <b>Start|Settings|Control Panel|System</b>
    105   tool (<b>Advanced</b> tab).  See the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>
    106   if you don't know how to do this.
    107   <p>
    108   <hr align="left" width="100">
    109   <p>
    110   Next, you prepare and execute the model:
    111   <table class="code"><tr><td>
    112     cd C:\ANUGA<br>
    113     cd project<br>
    114     python setup_model.py<br >
    115     python run_model.py
    116   </td></tr></table>
    117   <p>
    118   <hr align="left" width="100">
    119   <p>
    120   This should all run to completion though it may take several days, depending on
    121   the hardware used.
    122   <p>
    123   If you get an error from <font color="red">setup_model.py</font>
    124   or <font color="red">run_model.py</font> look for some explanation in the log
    125   files, which you will find under <b>C:\ANUGA\data</b>. Just keep
    126   drilling down from that point until you find a directory called <b>outputs</b>.
    127   The latest directory in <b>outputs</b> should contain a file called <font color="red">screen_error.txt</font>
    128   with an explanation of the error at the end.
    129   <p>
    130   Once the simulation has completed you may view the results using the ANUGA
    131   viewer as described in the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>
    132   and <a href="documents/anuga_user_manual.pdf">User Manual</a>.  You may also
    133   generate rasters suitable for GIS mapping or write dedicated scripts extracting timeseries at selected
    134   locations.  Some hints to help you do this are at the <a href="analysis.html">analysis page</a>.
    135   <p>
    136   The ANUGA <a href="documents/anuga_user_manual.pdf">User Manual</a> describes
    137   how to use the ANUGA system in general and provides some examples of its use.
    138 
    139   <a name="auxscripts"><h3><b>How to extract data from the simulation output files</b></h3></a>
    140 
    141   After you have run a simulation you may wish to extract information from the generated SWW file.
    142   On this disk there are a selection of example analysis scripts that you can use or modify.
    143   The <a href="analysis.html">analysis scripts</a> page explains how to use the scripts.
    144 
    145   <a name="modifications"><h3><b>How to modify a simulation</b></h3></a>
    146 
    147   After you have run the supplied simulation you may wish to change it in some way, such as adding improved bathymetry data, for example.
    148   The <a href="modifications.html">modifications</a> page explains how to do this.
    149 
    150   <a name="userslist"><h3><b>How to join the ANUGA user's mailing list</b></h3></a>
    151 
    152   One of the quickest ways to get your ANUGA questions answered is by asking them on the <b>ANUGA-user</b> mailing list.
    153   You can <a href="https://lists.sourceforge.net/lists/listinfo/anuga-user">subscribe to the list</a>
    154   and can view the mailing list <a href="https://sourceforge.net/mailarchive/forum.php?forum_name=anuga-user">archives</a>.
    155   <p>
    156   It costs nothing to register and you can choose to have list mail sent to you as individual emails or have them batched
    157   into a few emails per day.  You can unsubscribe at any time through the subscribe link above.
    158 
    159   <a name="FAQ"><h3><b>Frequently Asked Questions</b></h3></a>
    160 
    161   There is a <b>Frequently Asked Questions</b> (FAQ) page at
    162   <a href="https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions">https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions</a>.
    163   Look in there and search the mailing list archives before asking questions on the ANUGA user's mailing list.
    164   Someone may already have asked your question!
    165   <p>
    166   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
    167   it would be helpful to others.
    16862</body>
    16963</html>

  • DVD_images/extra_files/BatemansBay/modifications.html

    r7271 r7300  
    2626  Here we talk about how you 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
    28   areas, or maybe you want to see the result of different events.
     28  areas, or maybe you want to see the result for different events.
    2929  <p>
    3030  First we describe the uses of the script files you might change, then we walk through a few examples
    … …  
    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_boundary.py</font></td><td>Builds ...</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>
    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>
    … …  
    4444  <a name="project.py"><h4><b>project.py</b></h4></a>
    4545
    46   This file is the heart of the simulation.  Here we specify many things, including the tide level, the simulation
    47   star and stop times, input data files, and so on.  Because we are using python as the programming language in
     46    This file is the heart of the simulation. The project script introduces all files that are necessary to run all accompanying scripts.
     47    By changing one of the variables in this script the output could be completely different.
     48    For further details on changing parameters see <a href="#change">Making changes to a simulation</a>.
     49
     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
    4852  these files, we can use the power of the language to speed up our development.  We use this by <i>parameterising</i>
    4953  data as much as possible.
    5054  <p>
    51   As an example, let's look at the <b>model</b> variable we define in <font color="red">project.py</font>:
     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>:
    5257  <table class="code">
    53     <tr><td>model = 'small'&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;# different size model - 'small' or 'large'</td></tr>
     58    <tr><td>scenario_name = 'hobart'&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;# name of the scenario</td></tr>
    5459  </table>
    5560  <p>
    56   We define this variable solely to quickly change other input filenames.  Where we want a different input file
     61  We define this variable solely to quickly change other input filenames.  Where we want a different input files for
     62  a different scenario,
    5763  depending on whether we want a 'small' or 'large' model, we build the filenames using the <b>model</b> variable.
    5864  Some examples are:
    5965  <p>
    6066  <table class="code">
    61     <tr><td>bounding_polygon_filename = 'bounding_polygon_'+ model + '.csv'</td></tr>
    62     <tr><td>land_initial_conditions_filename = [['initial_conditions_' + model +'.csv', 0]]</td></tr>
    63     <tr><td>landward_boundary_filename = 'landward_boundary_'+ model +'.csv'</td></tr>
     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>
    6470  </table>
    6571  <p>
    … …  
    7177  This speeds up development and make errors less likely.  If you want to add another model to the two
    7278  we show above, just set <b>model</b> to 'medium' and create appropriate input files with the string
    73   'medium' in the filename.
     79  'medium' in the filename. -->
    7480
    75   <a name="build_boundary.py"><h4><b>build_boundary.py</b></h4></a>
     81  <a name="build_elevation.py"><h4><b>build_elevation.py</b></h4></a>
    7682
    77   [text about build_boundary.py]<br>
    78   [In particular, need to run this if elevation data changes.]
     83  This script combines all input elevation files into one PTS file.
     84  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>.
    7986  <p>
    8087
    8188  <a name="setup_model.py"><h4><b>setup_model.py</b></h4></a>
    8289
    83   [text about project.py]
     90  This script is used to transform data into a specific format for <font color="red">run_model.py</font>,
     91  if required, and to generate warning messages if you are missing data.
    8492  <p>
    8593
    8694  <a name="run_model.py"><h4><b>run_model.py</b></h4></a>
    8795
    88   [text about project.py]
     96  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
     99  <a href="#change">Making changes to a simulation</a>.
    89100  <p>
    90101
    91102  <a name="change"><h3><b>Making changes to a simulation</b></h3></a>
    92103
    93   Now we walk through some examples of changes you might make.  There are many ways to change a simulation - here
    94   we discuss just a few.
     104  There are many parameters that you can change within the <font color="red">project.py</font> script,
     105  but the following four parameters are those most commonly changed.
    95106  <p>
    96107
    97   <a name="events"><h4><b>Changing events</b></h4></a>
     108  <a name="tide"><h4><b>Tide</b></h4></a>
    98109
    99   [some events text here]
     110  The <b>tide</b> parameter is used to change the mean stage of the simulation.  When <b>tide</b> is set to 0
     111  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.
    100113  <p>
    101114
    102   <a name="elevation"><h4><b>Changing elevation data</b></h4></a>
     115  <a name="events"><h4><b>Events</b></h4></a>
    103116
    104   [some elevation text here]
     117  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>
    105125  <p>
    106126
     127  <a name="elevation"><h4><b>Elevation</b></h4></a>
     128
     129  Elevation data can be changed in the <font color="red">project.py</font> elevation script.
     130  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.
     132  <p>
     133
     134  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>
     138  <p>
     139
     140  An ASC file header has the format:
     141  <table class="code">
     142    <tr><td><pre>ncols         868
     143nrows         856
     144xllcorner     418933.86055096
     145yllcorner     5151810.6668096
     146cellsize      250
     147NODATA_value  -9999</pre></td></tr>
     148  </table>
     149  <p>
     150
     151  The header of a PRJ file has the format:
     152  <table class="code">
     153    <tr><td><pre>Projection    UTM
     154Zone          55
     155Datum         D_GDA_1994
     156Zunits        NO
     157Units         METERS
     158Spheroid      GRS_1980
     159Xshift        500000
     160Yshift        10000000
     161Parameters</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>
     166  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                   'Batemans_BBHD_MGA_1995.csv',
     171                   'moruya_AHD_MGA_2000.csv']
     172
     173ascii_grid_filenames = ['sd100031996_p',
     174                        'sd100031996_p2',
     175                        'sd100031996_p3',
     176                        'sd100031996_p4']</pre></td></tr>
     177  </table>
     178  <p>
     179
     180  For further information on ANUGA file formats please see the ANUGA User Manual, section 6.1.
     181  <p>
     182
     183  <a name="interior_regions"><h4><b>Interior regions</b></h4></a>
     184
     185  The <b>interior_regions</b> parameter allows you to change the mesh of the model.
     186  <p>
    107187</body>
    108188</html>

  • DVD_images/extra_files/BatemansBay/project/project.py

    r7205 r7300  
    2929
    3030# the event number or the mux file name
    31 ##event_number = 58129  #1 in 200 yr Puyesgur
    32 ##event_number = 58115    #1 in 500 yr Puysegur
    33 ##event_number = 58226    #1 in 1000 yr Puysegur
    34 ##event_number = 58284    #1 in 2000 yr Puysegur
    35 ##event_number = 58286    #1 in 5000 yr Puysegur
    36 ##event_number = 58346      #1 in 10000 yr Puysegur
    37 
    38 ##event_number = 51077  #1 in 200 yr New Hebrides
    39 ##event_number = 51378    #1 in 500 yr New Hebrides
    40 ##event_number = 51347    #1 in 1000 yr New Hebrides
    41 ##event_number = 51292    #1 in 2000 yr New Hebrides
    42 event_number = 51424    #1 in 5000 yr New Hebrides
    43 ##event_number = 51204     #1 in 10000 yr New Hebrides
    44 
    45 ######event_number = 58368    #1 in 100 000 yr Puysegur!!!
    46 ######event_number = 51436    #1 in 100 000 yr New Hebrides!!!
    47 ######event_number = 58272      #1 in 10000 yr Puysegur????
    48 ######event_number = 51445     #1 in 10000 yr New Hebrides????
     31##event_number = 58129     #1 in 200 yr Puyesgur
     32##event_number = 58115     #1 in 500 yr Puysegur
     33##event_number = 58226     #1 in 1000 yr Puysegur
     34##event_number = 58284     #1 in 2000 yr Puysegur (Event 3)
     35##event_number = 58286     #1 in 5000 yr Puysegur
     36event_number = 58346     #1 in 10000 yr Puysegur (Event 1)
     37
     38##event_number = 51077     #1 in 200 yr New Hebrides
     39##event_number = 51378     #1 in 500 yr New Hebrides
     40##event_number = 51347     #1 in 1000 yr New Hebrides
     41##event_number = 51292     #1 in 2000 yr New Hebrides
     42##event_number = 51424     #1 in 5000 yr New Hebrides
     43##event_number = 51204     #1 in 10000 yr New Hebrides (Event 2)
     44
     45######event_number = 58368      #1 in 100 000 yr Puysegur
     46######event_number = 51436      #1 in 100 000 yr New Hebrides
     47######event_number = 58272      #1 in ~15000 yr Puysegur
     48######event_number = 51445      #1 in ~15000 yr New Hebrides
    4949
    5050alpha = 0.1             # smoothing parameter for mesh
    … …  
    7878# Used in build_elevation.py
    7979# Format for ascii grids, as produced in ArcGIS + a projection file
    80 ascii_grid_filenames = ['1a',# Topographic data
    81                         '1b',
    82                         '2b',
    83                         '2a_3',
    84                         '3b',
    85                         '3a',
    86                         '4a_2',
    87                         '4b',
    88                         'off1',
    89                         'off2',
    90                         'off3',
    91                         'bbhd',
    92                         'sd100031996_p',
    93                         'sd100031996_p2',
    94                         'sd100031996_p3',
    95                         'sd100031996_p4']
     80ascii_grid_filenames = []
    9681                   
    9782# Format for point is x,y,elevation (with header)
    98 point_filenames = ['SD100031996_jgriffin_clip.csv',
    99                    'tomaga_offshore_AHD_MGA_1997.csv',
    100                    'Batemans_BBHD_MGA_1995.csv',
    101                    'moruya_AHD_MGA_2000.csv']
     83point_filenames = []
    10284         
    10385
    … …  
    135117# Used in run_building_inundation.py
    136118# Format latitude,longitude etc (geographic)
    137 ##building_exposure_filename = 'busselton_res_clip.csv' # from NEXIS
     119##building_exposure_filename = '' # from NEXIS
    138120
    139121# AREA OF IMAGES - Extent of each image to find out highest runup
    140122# Header - easting,northing,id,value
    141123# Used in get_runup.py
    142 images_filename = 'images.csv'
     124images_filename = ''
    143125
    144126# BOUNDING POLYGON - used in build_boundary.py and run_model.py respectively
    … …  
    218200# create paths generated from environment variables.
    219201home = join(os.getenv(ENV_INUNDATIONHOME), 'data') # Absolute path for data folder
    220 
     202   
    221203# check various directories/files that must exist
    222204anuga_folder = join(home, state, scenario_folder, 'anuga')

  • DVD_images/extra_files/BatemansBay/project/setup_model.py

    r7265 r7300  
    6161if not exists(project.gauges_folder):
    6262    print "Sorry, gauges directory '%s' doesn't exist" % project.gauges_folder
     63    sanity_error = True
     64
     65if not exists(project.meshes_folder):
     66    print "Sorry, meshes directory '%s' doesn't exist" % project.meshes_folder
    6367    sanity_error = True
    6468

  • DVD_images/extra_files/GoldCoast/index.html

    r7265 r7300  
    2121  </table>
    2222  <hr>
    23 <!--
    24   <ul class="navbar">
    25     <li><a href="#introduction">Introduction</a>
    26     <li><a href="#installing">Installing</a>
    27     <li><a href="#simulating">Running</a>
    28     <li><a href="#userslist">Mailing list</a>
    29     <li><a href="#auxscripts">Auxiliary scripts</a>
    30     <li><a href="#FAQ">Frequently Asked Questions</a>
    31     <li><a href="#extra">Extra stuff</a>
    32   </ul>
    33 -->
    3423
    3524  <a name="introduction"><h3><b>Introduction</b></h3></a>
     25
    3626  The information on this DVD and the associated report is intended to assist emergency managers in developing preparation and
    3727  response plans that can be used during a tsunami threat or emergency.
    3828  <p>
    3929  The Attorney General's Department (AGD) has supported Geoscience Australia (GA) in developing a range of products to support
    40   the understanding of tsunami hazard through the Australian Tsunami Warning System Project. The work reported here is intended
     30  the understanding of tsunami hazard through the Australian Probabilistic Tsunami Warning System Project. The work reported here is intended
    4131  to further build the capacity of the Jurisdictions in developing inundation models for prioritised locations.
    4232  <p>
    … …  
    4434  software necessary to reproduce and potentially augment the models underpinning the report. This will allow the Jurisdiction
    4535  to rerun the models with minor modifications or new elevation data as needed and also potentially replicate the methodology
    46   to other locations if desired. 
     36  to other locations within the model extent, if desired. 
    4737  <p>
    4838  The data provided on this DVD is:
    4939  <ul>
    50     <li> The Professional Opinion Report 2009/XX entitled <i>Capacity Building for Tsunami Planning and Preparation:
    51          Inundation Models for Four East Coast Australian Communities</i>
    52     <li> Elevation data used with the tsunami inundation model
    53     <li> Input data for a range of tsunami events
     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/queensland/gold_coast_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/queensland/gold_coast_tsunami_scenario_2009/anuga/outputs">timeseries</a> from the models
     45    <li> Combined <a href="data/queensland/gold_coast_tsunami_scenario_2009/anuga/topographies">elevation data</a> used by the simulation
     46    <li> The <a href="data/queensland/gold_coast_tsunami_scenario_2009/anuga/outputs/elevation">Arc grid</a> of the resulting elevation generated by ANUGA
    5447    <li> The Python scripts used to run the models
    5548  </ul>
     49  <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
     52  described in the report.
    5653
    57   <a name="requirements"><h3><b>Requirements</b></h3></a>
     54  <a name="requirements"><h3><b>Report Figures</b></h3></a>
    5855
    59   The tsunami inundation simulations are based on the Open Source software package called ANUGA.
    60   For more information about ANUGA visit <a href="https://datamining.anu.edu.au/anuga">https://datamining.anu.edu.au/anuga</a>.
    61   <p>
    62   ANUGA has been developed and tested under the Windows XP and Linux (Ubuntu, Mint and Red Hat) operating systems. 
    63   ANUGA may also be installed on a Windows Vista system and Debian Linux, but these have not been extensively tested.
    64   <p>
    65   The ANUGA scripts on this DVD require a minimum of 3GB of memory and possibly more, if mesh resolutions are increased. For this reason
    66   we recommend using 64 bit Ubuntu Linux as this operating system can use more than 3GB of memory, whereas Windows XP cannot.
     56  The figures from the report may be found <a href="documents/Figures">here</a>.
    6757
    68   <a name="installing"><h3><b>Installing ANUGA</b></h3></a>
     58  <a name="installation"><h3><b>Simulation Installation and Usage</b></h3></a>
    6959
    70   You must install ANUGA according to the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
    71   As the installation procedure comprises a number of steps we suggest that it is carried out by someone with a
    72   basic understanding of how to install software packages on the operating system of choice.
     60  Information for installing and using the simulation is <a href="installation.html">here</a>.
    7361
    74   <a name="simulating"><h3><b>How to run a simulation</b></h3></a>
    75 
    76   This is how a user should run the model on this DVD.
    77   We assume that you are using Windows and will give examples for that operating system.
    78   The translation to Linux is left as an exercise for the student!
    79   <p>
    80   <hr align="left" width="100">
    81   <p>
    82   First, it is assumed you have installed the ANUGA software according to the
    83   <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
    84   <p>
    85   <hr align="left" width="100">
    86   <p>
    87   Next, you must copy the entire contents of the DVD to a place in your filesystem. Let's assume
    88   that you want to put the data into <b>C:\ANUGA</b>. You would do this in a Command Prompt window:
    89   <table class="code"><tr><td>
    90     C:<br>
    91     cd \<br>
    92     mkdir ANUGA<br>
    93     xcopy /e X:\ ANUGA
    94   </td></tr></table>
    95   <p>
    96   Of course, you could just drag all files on the DVD (X:\ is the assumed drive letter) to the desired target directory with Explorer.
    97   <p>
    98   <hr align="left" width="100">
    99   <p>
    100   Now you must create an environment variable <b>ANUGADATA</b> that points to the directory you just created:
    101   <table class="code"><tr><td>
    102     set ANUGADATA=C:\ANUGA
    103   </td></tr></table>
    104   <p>
    105   Doing the above in a Command Prompt window is temporary - if you open another
    106   window you will not have the ANUGADATA environment variable defined. To make
    107   the variable permanent you must set it in the <b>Start|Settings|Control Panel|System</b>
    108   tool (<b>Advanced</b> tab).  See the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>
    109   if you don't know how to do this.
    110   <p>
    111   <hr align="left" width="100">
    112   <p>
    113   At this point you should run the <font color="red">build_elevation.py</font>
    114   script to convert the raw elevation data to a set of 'combined_elevation'
    115   files ready to be used by the ANUGA system. It is possible that you have not
    116   been given the elevation data on the DVD as it is too large. In that case you
    117   cannot run the <font color="red">build_elevation.py</font> script and you
    118   should skip to the next step.
    119   <table class="code"><tr><td>
    120     cd C:\ANUGA<br>
    121     cd project<br>
    122     python build_elevation.py
    123   </td></tr></table>
    124   <p>
    125   When you get to the point of running the model with your own data, you must
    126   run <font color="red">build_elevation.py</font> to recreate the combined elevation files every time
    127   you change the elevation data.
    128   <p>
    129   <hr align="left" width="100">
    130   <p>
    131   Next, you prepare and execute the model:
    132   <table class="code"><tr><td>
    133     python setup_model.py<br >
    134     python run_model.py
    135   </td></tr></table>
    136   <p>
    137   <hr align="left" width="100">
    138   <p>
    139   This should all run to completion, though it may take several days, depending on
    140   the hardware used.
    141   <p>
    142   If you do get an error from <font color="red">setup_model.py</font>
    143   or <font color="red">run_model.py</font> look for some explanation in the log
    144   files, which you should find somewhere under <b>C:\ANUGA\data</b>. Just keep
    145   drilling down from that point until you find a directory called <b>outputs</b>.
    146   The latest directory in <b>outputs</b> should contain a file called <font color="red">screen_error.txt</font>
    147   with an explanation of the error at the end.
    148   <p>
    149   Once the simulation has completed you may view the results using the ANUGA
    150   viewer as described in the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>
    151   and <a href="documents/anuga_user_manual.pdf">User Manual</a>, run the script
    152   <font color="red">export_results_max.py</font> to generate rasters suitable
    153   for GIS mapping, or write dedicated scripts extracting timeseries at selected
    154   locations.
    155   <p>
    156   The input waves are all derived from events available in the Australian Tsunami
    157   Hazard Map. As this dataset is very large, this DVD only contains the events
    158   described in the report. If other events from the Hazard Map are obtained,
    159   the script <font color="red">build_urs_boundary.py</font> has been designed
    160   to prepare the associated input wave for ingestion into ANUGA.  This script
    161   is documented in the <a href="documents/anuga_user_manual.pdf">User Manual</a>.
    162   <p>
    163   The ANUGA <a href="documents/anuga_user_manual.pdf">User Manual</a> describes
    164   how to use the ANUGA system in general and provides some examples of its use.
    165 
    166   <a name="userslist"><h3><b>How to join the ANUGA user's mailing list</b></h3></a>
    167 
    168   One of the quickest ways to get your ANUGA questions answered is by asking them on the <b>ANUGA-user</b> mailing list.
    169   You can subscribe to the list <a href="https://lists.sourceforge.net/lists/listinfo/anuga-user">here</a>
    170   and can view the mailing list <a href="https://sourceforge.net/mailarchive/forum.php?forum_name=anuga-user">archives</a>.
    171   <p>
    172   It costs nothing to register and you can choose to have list mail sent to you as individual emails or have them batched
    173   into a few emails per day.  You can unsubscribe at any time through the subscribe link above.
    174 
    175   <a name="auxscripts"><h3><b>How to use the auxiliary scripts</b></h3></a>
    176 
    177   On this disk there are a selection of auxiliary scripts that you can use to extract various pieces of information
    178   from the generated SWW files.  The <a href="auxiliary_scripts.html">auxiliary scripts</a> page explains how to use the scripts.
    179 
    180   <a name="FAQ"><h3><b>Frequently Asked Questions</b></h3></a>
    181 
    182   There is a <b>Frequently Asked Questions</b> (FAQ) page at
    183   <a href="https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions">https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions</a>.
    184   Look in here and search the mailing list archives before asking questions on the ANUGA user's mailing list.
    185   Someone may already have asked your question!
    186   <p>
    187   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
    188   it would be helpful to others.
    18962</body>
    19063</html>

  • DVD_images/extra_files/GoldCoast/project/project.py

    r7205 r7300  
    3636    event_number = 51469    # the event number or the mux file name
    3737
    38 event_number_list = [51469, 50863, 51392] # To piggy back multiple events
    39 
    40 tide = 0
     38event_number_list = [51469, 51392, 50863] # To piggy back multiple events
     39
     40# Event Details:
     41# Event 1 (51469)
     42# Source Zone = New Hebrides
     43# Return Period = 10 000 years
     44# Wave height at 100 m = 2.3 m
     45#
     46# Event 2 (51392)
     47# Source Zone = New Hebrides
     48# Return Period = 5000 years
     49# Wave height at 100 m = 1.7 m
     50#
     51# Event 3 (50863)
     52# Source Zone = New Hebrides
     53# Return Period = 200 years
     54# Wave height at 100 m = 0.3 m
     55
     56tide = 0                # Mean Sea Level = 0,
     57                        # Highest Astronomical Tide = 1.1 m for Gold Coast                       
    4158alpha = 0.1             # smoothing parameter for mesh
    42 friction=0.01           # manning's friction coefficient
    43 starttime=0             # start time for simulation
    44 finaltime=80000         # final time for simulation
     59friction = 0.01           # manning's friction coefficient
     60starttime = 0             # start time for simulation
     61finaltime = 80000         # final time for simulation
    4562
    4663setup = 'final'         # This can be one of three values
    … …  
    6077#-------------------------------------------------------------------------------
    6178
    62 output_comment = [setup, tide, '250m', event_number]
     79output_comment = [setup, tide, event_number]
    6380
    6481#-------------------------------------------------------------------------------
    … …  
    6986# Used in build_elevation.py
    7087# Format for ascii grids, as produced in ArcGIS + a projection file
    71 ascii_grid_filenames = ['grid250m_all_pro'] # 2005 250m grid
    72 ##                      ['GC_DTM_30m']] # supplied DEM
     88ascii_grid_filenames = []
    7389
    7490# Format for point is x,y,elevation (with header)
    7591point_filenames = []
    76 
    77 ### Add csv header list to all files in point_filenames
    78 ##headerlist = ['x', 'y', 'elevation']
    79 ##for f in point_filenames:
    80 ##    add_csv_header(join(topographies_folder, f), headerlist)
    8192
    8293# BOUNDING POLYGON - for data clipping and estimate of triangles in mesh
    8394# Used in build_elevation.py
    8495# Format for points easting,northing (no header)
    85 bounding_polygon_filename = 'bounding_polygon_sml.csv'
     96bounding_polygon_filename = 'bounding_polygon.csv'
    8697bounding_polygon_maxarea = 125000
    8798
    … …  
    89100# Used in run_model.py
    90101# Format for points easting,northing (no header)                   
    91 interior_regions_data = []
     102interior_regions_data = [['area_of_interest.csv', 500],
     103                         ['intermediate.csv', 25000]]
    92104
    93105# LAND - used to set the initial stage/water to be offcoast only
    94106# Used in run_model.py.  Format for points easting,northing (no header)
    95 land_initial_conditions_filename = [['initial_conditions_sml.csv', 0]]
     107land_initial_conditions_filename = [['initial_conditions.csv', 0]]
    96108
    97109# GAUGES - for creating timeseries at a specific point
    … …  
    103115# Used in run_building_inundation.py
    104116# Format latitude,longitude etc (geographic)
    105 building_exposure_filename = 'gold_coast_res_clip.csv' # from NEXIS
     117building_exposure_filename = '' # from NEXIS
    106118
    107119# AREA OF IMAGES - Extent of each image to find out highest runup
    … …  
    118130# Thinned ordering file from Hazard Map (geographic)
    119131# Format is index,latitude,longitude (with header)
    120 urs_order_filename = 'urs_order_sml.csv'
     132urs_order_filename = 'urs_order.csv'
    121133
    122134# Landward bounding points
    123135# Format easting,northing (no header)
    124 landward_boundary_filename = 'landward_boundary_sml.csv'
     136landward_boundary_filename = 'landward_boundary.csv'
    125137
    126138# MUX input filename.
    … …  
    138150#-------------------------------------------------------------------------------
    139151
    140 # ASCII export grid for Gold Coast
    141 xminGold_Coast = 541500
    142 xmaxGold_Coast = 546000
    143 yminGold_Coast = 6893500
    144 ymaxGold_Coast = 6898500
    145 
    146 # ASCII export grid for dune study
    147 xminDune = 536710
    148 xmaxDune = 556150
    149 yminDune = 6881125
    150 ymaxDune = 6926860
     152
     153
    151154
    152155################################################################################
    … …  
    172175# Output filename for elevation
    173176# this is a combination of all the data generated in build_elevation.py
    174 combined_elevation_basename = scenario_name + '_combined_elevation_250m'
     177combined_elevation_basename = scenario_name + '_combined_elevation'
    175178
    176179#-------------------------------------------------------------------------------
    … …  
    246249    images = join(polygons_folder, images_filename)
    247250
    248 # full path to where MUX files (or meta-files) live
    249 mux_input = join(event_folder, mux_input_filename)
    250 
     251

  • DVD_images/extra_files/GoldCoast/project/setup_model.py

    r7205 r7300  
    7777    sanity_error = True
    7878
    79 # if multi_mux is True, check if multi-mux file exists
    80 if project.multi_mux:
    81     if not exists(project.mux_input):
    82         print ("Sorry, MUX input file '%s' doesn't exist"
    83                % project.mux_input)
    84         sanity_error = True
    85 
    8679#-----
    8780# If this directory don't exist, EventSelection hasn't been run.

  • DVD_images/extra_files/Gosford/index.html

    r7265 r7300  
    2121  </table>
    2222  <hr>
    23 <!--
    24   <ul class="navbar">
    25     <li><a href="#introduction">Introduction</a>
    26     <li><a href="#installing">Installing</a>
    27     <li><a href="#simulating">Running</a>
    28     <li><a href="#userslist">Mailing list</a>
    29     <li><a href="#auxscripts">Auxiliary scripts</a>
    30     <li><a href="#FAQ">Frequently Asked Questions</a>
    31     <li><a href="#extra">Extra stuff</a>
    32   </ul>
    33 -->
    3423
    3524  <a name="introduction"><h3><b>Introduction</b></h3></a>
     25
    3626  The information on this DVD and the associated report is intended to assist emergency managers in developing preparation and
    3727  response plans that can be used during a tsunami threat or emergency.
    3828  <p>
    3929  The Attorney General's Department (AGD) has supported Geoscience Australia (GA) in developing a range of products to support
    40   the understanding of tsunami hazard through the Australian Tsunami Warning System Project. The work reported here is intended
     30  the understanding of tsunami hazard through the Australian Probabilistic Tsunami Warning System Project. The work reported here is intended
    4131  to further build the capacity of the Jurisdictions in developing inundation models for prioritised locations.
    4232  <p>
    … …  
    4434  software necessary to reproduce and potentially augment the models underpinning the report. This will allow the Jurisdiction
    4535  to rerun the models with minor modifications or new elevation data as needed and also potentially replicate the methodology
    46   to other locations if desired. 
     36  to other locations within the model extent, if desired. 
    4737  <p>
    4838  The data provided on this DVD is:
    4939  <ul>
    50     <li> The Professional Opinion Report 2009/XX entitled <i>Capacity Building for Tsunami Planning and Preparation:
    51          Inundation Models for Four East Coast Australian Communities</i>
    52     <li> Elevation data used with the tsunami inundation model
    53     <li> Input data for a range of tsunami events
     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
     45    <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
    5447    <li> The Python scripts used to run the models
    5548  </ul>
     49  <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
     52  described in the report.
    5653
    57   <a name="requirements"><h3><b>Requirements</b></h3></a>
     54  <a name="requirements"><h3><b>Report Figures</b></h3></a>
    5855
    59   The tsunami inundation simulations are based on the Open Source software package called ANUGA.
    60   For more information about ANUGA visit <a href="https://datamining.anu.edu.au/anuga">https://datamining.anu.edu.au/anuga</a>.
    61   <p>
    62   ANUGA has been developed and tested under the Windows XP and Linux (Ubuntu, Mint and Red Hat) operating systems. 
    63   ANUGA may also be installed on a Windows Vista system and Debian Linux, but these have not been extensively tested.
    64   <p>
    65   The ANUGA scripts on this DVD require a minimum of 3GB of memory and possibly more, if mesh resolutions are increased. For this reason
    66   we recommend using 64 bit Ubuntu Linux as this operating system can use more than 3GB of memory, whereas Windows XP cannot.
     56  The figures from the report may be found <a href="documents/Figures">here</a>.
    6757
    68   <a name="installing"><h3><b>Installing ANUGA</b></h3></a>
     58  <a name="installation"><h3><b>Simulation Installation and Usage</b></h3></a>
    6959
    70   You must install ANUGA according to the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
    71   As the installation procedure comprises a number of steps we suggest that it is carried out by someone with a
    72   basic understanding of how to install software packages on the operating system of choice.
     60  Information for installing and using the simulation is <a href="installation.html">here</a>.
    7361
    74   <a name="simulating"><h3><b>How to run a simulation</b></h3></a>
    75 
    76   This is how a user should run the model on this DVD.
    77   We assume that you are using Windows and will give examples for that operating system.
    78   The translation to Linux is left as an exercise for the student!
    79   <p>
    80   <hr align="left" width="100">
    81   <p>
    82   First, it is assumed you have installed the ANUGA software according to the
    83   <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
    84   <p>
    85   <hr align="left" width="100">
    86   <p>
    87   Next, you must copy the entire contents of the DVD to a place in your filesystem. Let's assume
    88   that you want to put the data into <b>C:\ANUGA</b>. You would do this in a Command Prompt window:
    89   <table class="code"><tr><td>
    90     C:<br>
    91     cd \<br>
    92     mkdir ANUGA<br>
    93     xcopy /e X:\ ANUGA
    94   </td></tr></table>
    95   <p>
    96   Of course, you could just drag all files on the DVD (X:\ is the assumed drive letter) to the desired target directory with Explorer.
    97   <p>
    98   <hr align="left" width="100">
    99   <p>
    100   Now you must create an environment variable <b>ANUGADATA</b> that points to the directory you just created:
    101   <table class="code"><tr><td>
    102     set ANUGADATA=C:\ANUGA
    103   </td></tr></table>
    104   <p>
    105   Doing the above in a Command Prompt window is temporary - if you open another
    106   window you will not have the ANUGADATA environment variable defined. To make
    107   the variable permanent you must set it in the <b>Start|Settings|Control Panel|System</b>
    108   tool (<b>Advanced</b> tab).  See the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>
    109   if you don't know how to do this.
    110   <p>
    111   <hr align="left" width="100">
    112   <p>
    113   At this point you should run the <font color="red">build_elevation.py</font>
    114   script to convert the raw elevation data to a set of 'combined_elevation'
    115   files ready to be used by the ANUGA system. It is possible that you have not
    116   been given the elevation data on the DVD as it is too large. In that case you
    117   cannot run the <font color="red">build_elevation.py</font> script and you
    118   should skip to the next step.
    119   <table class="code"><tr><td>
    120     cd C:\ANUGA<br>
    121     cd project<br>
    122     python build_elevation.py
    123   </td></tr></table>
    124   <p>
    125   When you get to the point of running the model with your own data, you must
    126   run <font color="red">build_elevation.py</font> to recreate the combined elevation files every time
    127   you change the elevation data.
    128   <p>
    129   <hr align="left" width="100">
    130   <p>
    131   Next, you prepare and execute the model:
    132   <table class="code"><tr><td>
    133     python setup_model.py<br >
    134     python run_model.py
    135   </td></tr></table>
    136   <p>
    137   <hr align="left" width="100">
    138   <p>
    139   This should all run to completion, though it may take several days, depending on
    140   the hardware used.
    141   <p>
    142   If you do get an error from <font color="red">setup_model.py</font>
    143   or <font color="red">run_model.py</font> look for some explanation in the log
    144   files, which you should find somewhere under <b>C:\ANUGA\data</b>. Just keep
    145   drilling down from that point until you find a directory called <b>outputs</b>.
    146   The latest directory in <b>outputs</b> should contain a file called <font color="red">screen_error.txt</font>
    147   with an explanation of the error at the end.
    148   <p>
    149   Once the simulation has completed you may view the results using the ANUGA
    150   viewer as described in the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>
    151   and <a href="documents/anuga_user_manual.pdf">User Manual</a>, run the script
    152   <font color="red">export_results_max.py</font> to generate rasters suitable
    153   for GIS mapping, or write dedicated scripts extracting timeseries at selected
    154   locations.
    155   <p>
    156   The input waves are all derived from events available in the Australian Tsunami
    157   Hazard Map. As this dataset is very large, this DVD only contains the events
    158   described in the report. If other events from the Hazard Map are obtained,
    159   the script <font color="red">build_urs_boundary.py</font> has been designed
    160   to prepare the associated input wave for ingestion into ANUGA.  This script
    161   is documented in the <a href="documents/anuga_user_manual.pdf">User Manual</a>.
    162   <p>
    163   The ANUGA <a href="documents/anuga_user_manual.pdf">User Manual</a> describes
    164   how to use the ANUGA system in general and provides some examples of its use.
    165 
    166   <a name="userslist"><h3><b>How to join the ANUGA user's mailing list</b></h3></a>
    167 
    168   One of the quickest ways to get your ANUGA questions answered is by asking them on the <b>ANUGA-user</b> mailing list.
    169   You can subscribe to the list <a href="https://lists.sourceforge.net/lists/listinfo/anuga-user">here</a>
    170   and can view the mailing list <a href="https://sourceforge.net/mailarchive/forum.php?forum_name=anuga-user">archives</a>.
    171   <p>
    172   It costs nothing to register and you can choose to have list mail sent to you as individual emails or have them batched
    173   into a few emails per day.  You can unsubscribe at any time through the subscribe link above.
    174 
    175   <a name="auxscripts"><h3><b>How to use the auxiliary scripts</b></h3></a>
    176 
    177   On this disk there are a selection of auxiliary scripts that you can use to extract various pieces of information
    178   from the generated SWW files.  The <a href="auxiliary_scripts.html">auxiliary scripts</a> page explains how to use the scripts.
    179 
    180   <a name="FAQ"><h3><b>Frequently Asked Questions</b></h3></a>
    181 
    182   There is a <b>Frequently Asked Questions</b> (FAQ) page at
    183   <a href="https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions">https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions</a>.
    184   Look in here and search the mailing list archives before asking questions on the ANUGA user's mailing list.
    185   Someone may already have asked your question!
    186   <p>
    187   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
    188   it would be helpful to others.
    18962</body>
    19063</html>

  • DVD_images/extra_files/Gosford/project/project.py

    r7205 r7300  
    99from os.path import join, exists
    1010import csv
     11#import run_model_later
    1112
    1213
    … …  
    2526#-------------------------------------------------------------------------------
    2627
    27 
    28 # Model specific parameters.
    29 # One or all can be changed each time the run_model script is executed
    30 tide = 0.0                # difference between MSL and HAT in metres
     28tide = 0.0   
     29             # difference between MSL and HAT in metres
    3130zone = 56               # specify zone of model
    3231#event_number = 58242    # Puysegur 1 in 10 000 # the event number or the mux file name
    33 event_number = 51436    # New Hebrides 1 in 10 000
     32#event_number = 51436    # New Hebrides 1 in 10 000
    3433#event_number = 58349    # Puysegur 1 in 5000
    3534#event_number = 58284    # Puysegur 1 in 2000
    3635#event_number = 58187    # Puysegur 1 in 1000
    3736#event_number = 58113    # Puysegur 1 in 500
    38 #event_number = 58025    # Puysegur 1 in 200
    39 
     37event_number = 58025    # Puysegur 1 in 200
    4038
    4139alpha = 0.1             # smoothing parameter for mesh
    … …  
    6967# Used in build_elevation.py
    7068# Format for ascii grids, as produced in ArcGIS + a projection file
    71 ascii_grid_filenames = ['e151_s34_clip2',
    72                         'aus197_topo2raster_clip2',
    73                         'hydro_topo2raster_clip2']
    74                         #'aus197_topo2raster_terrigal']   #GA data??
     69ascii_grid_filenames = []   
    7570                   
    76 
    77 
    78 #Get long list of Lidar filenames.
    79 ENV_INUNDATIONHOME = 'ANUGADATA'
    80 home = join(os.getenv(ENV_INUNDATIONHOME), 'data')
    81 anuga_folder = join(home, state, scenario_folder, 'anuga')
    82 topographies_folder = join(anuga_folder, 'topographies/original')
    83 
    84 #This reads a file containing lidar filenames and appends to a list
    85 file_list = join(topographies_folder, 'file_list.csv')
    86 fid = csv.reader(open(file_list))
    87 lidar_filenames = []
    88 for row in fid:
    89     lidar_filenames.append(','.join(row))
    90 
    91 
    9271# Format for point is x,y,elevation (with header)
    93 point_filenames = ['estuaries.txt',
    94 ##                   'XYHI341_HSDB_SD100035103',
    95 ##                   'XYAHD',
    96 ##                   'XYSCHOOL_11_99_HSDB_SD100021002_MGA',
    97                    'ENT5C1S08_03_AHD_prepared.txt',
    98                    'ENT5C1S09_03_AHD_prepared.txt',
    99                    'ENT5C1S10_03_AHD_prepared.txt',
    100 ##                   'XYAHD',
    101 ##                   'XYHI341_HSDB_SD100035103_MGA',
    102 ##                   'XYHI339_F_HSDB_SD100031669_MGA',
    103 ##                   'AUS197_MGA_AHD_1972.txt',
    104                    'hydro_clip_neg.txt'
    105                    ]
    106 point_filenames.extend(lidar_filenames)
    107 #print point_filenames
    108          
    109 
    110 ### Add csv header list to all files in point_filenames
    111 ##headerlist = ['x', 'y', 'elevation']
    112 ##for f in point_filenames:
    113 ##    add_csv_header(join(topographies_folder, f), headerlist)
    114 
    115     # BOUNDING POLYGON - for data clipping and estimate of triangles in mesh
     72point_filenames = []
     73       
     74
     75# BOUNDING POLYGON - for data clipping and estimate of triangles in mesh
    11676# Used in build_elevation.py
    11777# Format for points easting,northing (no header)
    … …  
    147107# Header - easting,northing,id,value
    148108# Used in get_runup.py
    149 images_filename = 'images.csv'
     109images_filename = ''
    150110
    151111# BOUNDING POLYGON - used in build_boundary.py and run_model.py respectively
    … …  
    201161host = get_host_name()
    202162
     163# Environment variable names.
     164# The inundation directory, not the data directory.
     165ENV_INUNDATIONHOME = 'ANUGADATA'
     166
    203167#-------------------------------------------------------------------------------
    204168# Output Elevation Data
    … …  
    221185# create paths generated from environment variables.
    222186home = join(os.getenv(ENV_INUNDATIONHOME), 'data') # Absolute path for data folder
    223  
     187    
    224188# check various directories/files that must exist
    225189anuga_folder = join(home, state, scenario_folder, 'anuga')
    226 topographies_folder = join(anuga_folder, 'topographies/original')
     190topographies_folder = join(anuga_folder, 'topographies')
    227191polygons_folder = join(anuga_folder, 'polygons')
    228192boundaries_folder = join(anuga_folder, 'boundaries')

  • DVD_images/extra_files/Gosford/project/run_model.py

    r7205 r7300  
    157157
    158158t0 = time.time()
    159 ##for t in domain.evolve(yieldstep=project.yieldstep,
    160 ##                       finaltime=1440,
    161 ##                       skip_initial_step=False):
    162 ##    print domain.timestepping_statistics()
    163 ##    print domain.boundary_statistics(tags='ocean')
    164 ##
    165 ##for t in domain.evolve(yieldstep=5,
    166 ##                       finaltime=6000,
    167 ##                       skip_initial_step=True):
    168 ##    print domain.timestepping_statistics()
    169 ##    print domain.boundary_statistics(tags='ocean')
    170 
    171159
    172160for t in domain.evolve(yieldstep=project.yieldstep,
    … …  
    175163    print domain.timestepping_statistics()
    176164    print domain.boundary_statistics(tags='ocean')
     165    print domain.volumetric_balance_statistics()
    177166
    178167print 'Simulation took %.2f seconds' % (time.time()-t0)

  • DVD_images/extra_files/Hobart/index.html

    r7265 r7300  
    2121  </table>
    2222  <hr>
    23 <!--
    24   <ul class="navbar">
    25     <li><a href="#introduction">Introduction</a>
    26     <li><a href="#installing">Installing</a>
    27     <li><a href="#simulating">Running</a>
    28     <li><a href="#userslist">Mailing list</a>
    29     <li><a href="#auxscripts">Auxiliary scripts</a>
    30     <li><a href="#FAQ">Frequently Asked Questions</a>
    31     <li><a href="#extra">Extra stuff</a>
    32   </ul>
    33 -->
    3423
    3524  <a name="introduction"><h3><b>Introduction</b></h3></a>
     25
    3626  The information on this DVD and the associated report is intended to assist emergency managers in developing preparation and
    3727  response plans that can be used during a tsunami threat or emergency.
    3828  <p>
    3929  The Attorney General's Department (AGD) has supported Geoscience Australia (GA) in developing a range of products to support
    40   the understanding of tsunami hazard through the Australian Tsunami Warning System Project. The work reported here is intended
     30  the understanding of tsunami hazard through the Australian Probabilistic Tsunami Warning System Project. The work reported here is intended
    4131  to further build the capacity of the Jurisdictions in developing inundation models for prioritised locations.
    4232  <p>
    … …  
    4434  software necessary to reproduce and potentially augment the models underpinning the report. This will allow the Jurisdiction
    4535  to rerun the models with minor modifications or new elevation data as needed and also potentially replicate the methodology
    46   to other locations if desired. 
     36  to other locations within the model extent, if desired. 
    4737  <p>
    4838  The data provided on this DVD is:
    4939  <ul>
    50     <li> The Professional Opinion Report 2009/XX entitled <i>Capacity Building for Tsunami Planning and Preparation:
    51          Inundation Models for Four East Coast Australian Communities</i>
    52     <li> Elevation data used with the tsunami inundation model
    53     <li> Input data for a range of tsunami events
     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/tasmania/hobart_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/tasmania/hobart_tsunami_scenario_2009/anuga/outputs">timeseries</a> from the models
     45    <li> Combined <a href="data/tasmania/hobart_tsunami_scenario_2009/anuga/topographies">elevation data</a> used by the simulation
     46    <li> The <a href="data/tasmania/hobart_tsunami_scenario_2009/anuga/outputs/elevation">Arc grid</a> of the resulting elevation generated by ANUGA
    5447    <li> The Python scripts used to run the models
    5548  </ul>
     49  <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
     52  described in the report.
    5653
    57   <a name="requirements"><h3><b>Requirements</b></h3></a>
     54  <a name="requirements"><h3><b>Report Figures</b></h3></a>
    5855
    59   The tsunami inundation simulations are based on the Open Source software package called ANUGA.
    60   For more information about ANUGA visit <a href="https://datamining.anu.edu.au/anuga">https://datamining.anu.edu.au/anuga</a>.
    61   <p>
    62   ANUGA has been developed and tested under the Windows XP and Linux (Ubuntu, Mint and Red Hat) operating systems. 
    63   ANUGA may also be installed on a Windows Vista system and Debian Linux, but these have not been extensively tested.
    64   <p>
    65   The ANUGA scripts on this DVD require a minimum of 3GB of memory and possibly more, if mesh resolutions are increased. For this reason
    66   we recommend using 64 bit Ubuntu Linux as this operating system can use more than 3GB of memory, whereas Windows XP cannot.
     56  The figures from the report may be found <a href="documents/Figures">here</a>.
    6757
    68   <a name="installing"><h3><b>Installing ANUGA</b></h3></a>
     58  <a name="installation"><h3><b>Simulation Installation and Usage</b></h3></a>
    6959
    70   You must install ANUGA according to the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
    71   As the installation procedure comprises a number of steps we suggest that it is carried out by someone with a
    72   basic understanding of how to install software packages on the operating system of choice.
     60  Information for installing and using the simulation is <a href="installation.html">here</a>.
    7361
    74   <a name="simulating"><h3><b>How to run a simulation</b></h3></a>
    75 
    76   This is how a user should run the model on this DVD.
    77   We assume that you are using Windows and will give examples for that operating system.
    78   The translation to Linux is left as an exercise for the student!
    79   <p>
    80   <hr align="left" width="100">
    81   <p>
    82   First, it is assumed you have installed the ANUGA software according to the
    83   <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
    84   <p>
    85   <hr align="left" width="100">
    86   <p>
    87   Next, you must copy the entire contents of the DVD to a place in your filesystem. Let's assume
    88   that you want to put the data into <b>C:\ANUGA</b>. You would do this in a Command Prompt window:
    89   <table class="code"><tr><td>
    90     C:<br>
    91     cd \<br>
    92     mkdir ANUGA<br>
    93     xcopy /e X:\ ANUGA
    94   </td></tr></table>
    95   <p>
    96   Of course, you could just drag all files on the DVD (X:\ is the assumed drive letter) to the desired target directory with Explorer.
    97   <p>
    98   <hr align="left" width="100">
    99   <p>
    100   Now you must create an environment variable <b>ANUGADATA</b> that points to the directory you just created:
    101   <table class="code"><tr><td>
    102     set ANUGADATA=C:\ANUGA
    103   </td></tr></table>
    104   <p>
    105   Doing the above in a Command Prompt window is temporary - if you open another
    106   window you will not have the ANUGADATA environment variable defined. To make
    107   the variable permanent you must set it in the <b>Start|Settings|Control Panel|System</b>
    108   tool (<b>Advanced</b> tab).  See the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>
    109   if you don't know how to do this.
    110   <p>
    111   <hr align="left" width="100">
    112   <p>
    113   At this point you should run the <font color="red">build_elevation.py</font>
    114   script to convert the raw elevation data to a set of 'combined_elevation'
    115   files ready to be used by the ANUGA system. It is possible that you have not
    116   been given the elevation data on the DVD as it is too large. In that case you
    117   cannot run the <font color="red">build_elevation.py</font> script and you
    118   should skip to the next step.
    119   <table class="code"><tr><td>
    120     cd C:\ANUGA<br>
    121     cd project<br>
    122     python build_elevation.py
    123   </td></tr></table>
    124   <p>
    125   When you get to the point of running the model with your own data, you must
    126   run <font color="red">build_elevation.py</font> to recreate the combined elevation files every time
    127   you change the elevation data.
    128   <p>
    129   <hr align="left" width="100">
    130   <p>
    131   Next, you prepare and execute the model:
    132   <table class="code"><tr><td>
    133     python setup_model.py<br >
    134     python run_model.py
    135   </td></tr></table>
    136   <p>
    137   <hr align="left" width="100">
    138   <p>
    139   This should all run to completion, though it may take several days, depending on
    140   the hardware used.
    141   <p>
    142   If you do get an error from <font color="red">setup_model.py</font>
    143   or <font color="red">run_model.py</font> look for some explanation in the log
    144   files, which you should find somewhere under <b>C:\ANUGA\data</b>. Just keep
    145   drilling down from that point until you find a directory called <b>outputs</b>.
    146   The latest directory in <b>outputs</b> should contain a file called <font color="red">screen_error.txt</font>
    147   with an explanation of the error at the end.
    148   <p>
    149   Once the simulation has completed you may view the results using the ANUGA
    150   viewer as described in the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>
    151   and <a href="documents/anuga_user_manual.pdf">User Manual</a>, run the script
    152   <font color="red">export_results_max.py</font> to generate rasters suitable
    153   for GIS mapping, or write dedicated scripts extracting timeseries at selected
    154   locations.
    155   <p>
    156   The input waves are all derived from events available in the Australian Tsunami
    157   Hazard Map. As this dataset is very large, this DVD only contains the events
    158   described in the report. If other events from the Hazard Map are obtained,
    159   the script <font color="red">build_urs_boundary.py</font> has been designed
    160   to prepare the associated input wave for ingestion into ANUGA.  This script
    161   is documented in the <a href="documents/anuga_user_manual.pdf">User Manual</a>.
    162   <p>
    163   The ANUGA <a href="documents/anuga_user_manual.pdf">User Manual</a> describes
    164   how to use the ANUGA system in general and provides some examples of its use.
    165 
    166   <a name="userslist"><h3><b>How to join the ANUGA user's mailing list</b></h3></a>
    167 
    168   One of the quickest ways to get your ANUGA questions answered is by asking them on the <b>ANUGA-user</b> mailing list.
    169   You can subscribe to the list <a href="https://lists.sourceforge.net/lists/listinfo/anuga-user">here</a>
    170   and can view the mailing list <a href="https://sourceforge.net/mailarchive/forum.php?forum_name=anuga-user">archives</a>.
    171   <p>
    172   It costs nothing to register and you can choose to have list mail sent to you as individual emails or have them batched
    173   into a few emails per day.  You can unsubscribe at any time through the subscribe link above.
    174 
    175   <a name="auxscripts"><h3><b>How to use the auxiliary scripts</b></h3></a>
    176 
    177   On this disk there are a selection of auxiliary scripts that you can use to extract various pieces of information
    178   from the generated SWW files.  The <a href="auxiliary_scripts.html">auxiliary scripts</a> page explains how to use the scripts.
    179 
    180   <a name="FAQ"><h3><b>Frequently Asked Questions</b></h3></a>
    181 
    182   There is a <b>Frequently Asked Questions</b> (FAQ) page at
    183   <a href="https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions">https://datamining.anu.edu.au/anuga/wiki/FrequentlyAskedQuestions</a>.
    184   Look in here and search the mailing list archives before asking questions on the ANUGA user's mailing list.
    185   Someone may already have asked your question!
    186   <p>
    187   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
    188   it would be helpful to others.
    18962</body>
    19063</html>

  • DVD_images/extra_files/Hobart/project/project.py

    r7206 r7300  
    88from time import localtime, strftime, gmtime
    99from os.path import join, exists
    10 
    11 #-------------------------------------------------------------------------------
    12 # Fitting Scenario
    13 #-------------------------------------------------------------------------------
    14 
    15 extent = None #'small' #None #'sw' # 'aos1' ##'aos1'
    16 extent_maxarea = 30000
    1710
    1811#-------------------------------------------------------------------------------
    … …  
    3225# Model specific parameters.
    3326# One or all can be changed each time the run_model script is executed
    34 tide = 0.8                # difference between MSL and HAT in metres
     27tide = 0                # difference between MSL and HAT in metres
     28                        # Highest Astronomical Tide = 0.8 m for Hobart
    3529zone = 55               # specify UTM zone of model
    36 event_number = 58292    # 58280, 64477 the event number or the mux file name
     30event_number = 58260    # 58280, 64477 the event number - See event_chosen.xls
     31                        # in anuga/boundaries for more details
    3732alpha = 0.1             # smoothing parameter for mesh
    3833friction=0.01           # manning's friction coefficient
    … …  
    5651#-------------------------------------------------------------------------------
    5752
    58 output_comment = [setup, tide, event_number, extent]
     53output_comment = [setup, tide, event_number]
    5954
    6055#-------------------------------------------------------------------------------
    … …  
    6459# ELEVATION DATA
    6560# Used in build_elevation.py
    66 if extent == None:
    67     ascii_grid_filenames = ['topo_grid_notsw', 'fitting_problem_sw_elevation']
    68     point_filenames = []
    69 elif extent == 'sw':
    70     # Format for ascii grids, as produced in ArcGIS + a projection file
    71     ascii_grid_filenames = ['hob3_pro_extract', 'grid_250m_project', 'ldr_bbay',
    72                             'ldr_bellerive', 'ldr_brunyislandneck',
    73                             'ldr_calvertsbeach', 'ldr_carltonbeach',
    74                             'ldr_connelly', 'ldr_cremorne', 'ldr_dodge1',
    75                             'ldr_dodge2', 'ldr_kingston', 'ldr_lauderdale',
    76                             'ldr_linersfarne', 'ldr_oppossumbay', 'ldr_primrose',
    77                             'ldr_rosny', 'ldr_sandybay', 'ldr_selfspoint',
    78                             'ldr_sevenmile', 'ldr_southarm1', 'ldr_southarm2',
    79                             'ldr_sullivanscove', 'ldr_tranmere', 'tasdem_mask']
    80 
    81     # Format for point is x,y,elevation (with header)
    82     point_filenames = ['Topo_1.txt','Topo_2.txt','Topo_3.txt',
    83                        'tasmania_data.txt',    # The data from Tasmania
    84                        'hydro_data.txt']       # Data from Hydro
    85 
    86 ### Add csv header list to all files in point_filenames
     61ascii_grid_filenames = []
     62## Add csv header list to all files in point_filenames
    8763##headerlist = ['x', 'y', 'elevation']
    88 ##for f in point_filenames:
    89 ##    add_csv_header(join(topographies_folder, f), headerlist)
     64point_filenames = []
     65
    9066
    9167# BOUNDING POLYGON - for data clipping and estimate of triangles in mesh
    … …  
    9874# Used in run_model.py
    9975# Format for points easting,northing (no header)                   
    100 if extent == 'sw':
    101     interior_regions_data = [['aos1.csv', 1500],
    102                              ['aos2.csv', 1500]]
    103     PriorityArea_filename = 'PriorityAreas.csv'
    104 elif extent == 'aos1':
    105     interior_regions_data = []
    106     PriorityArea_filename = 'PriorityAreas_aos1.csv'
    107 elif extent == 'aos2':
    108     interior_regions_data = []
    109     PriorityArea_filename = 'PriorityAreas_aos2.csv'
    110 elif extent == 'small':
    111     interior_regions_data = [['aoi_bruny.csv', 500],
    112                              ['aoi_S_arms.csv', 500],
    113                              ['aos1_small.csv', 1500],
    114                              ['aos2.csv', 1500],
    115                              ['sw.csv', 30000]]
    116     PriorityArea_filename = None
    117 elif extent == None:
    118     interior_regions_data = [['aos1.csv', 1500],
    119                              ['aos2.csv', 1500],
    120                              ['sw.csv', 30000]]
    121     PriorityArea_filename = 'PriorityAreas.csv'
     76interior_regions_data = [['aos1.csv', 1500],
     77                         ['aos2.csv', 1500],
     78                         ['sw.csv', 30000]]
     79PriorityArea_filename = 'PriorityAreas.csv'
    12280   
    12381# LAND - used to set the initial stage/water to be offcoast only
    12482# Used in run_model.py.  Format for points easting,northing (no header)
    125 land_initial_conditions_filename = 'initial_conditions.txt'
     83land_initial_conditions_filename = 'initial_conditions.csv'
    12684
    12785# GAUGES - for creating timeseries at a specific point
    12886# Used in get_timeseries.py. 
    12987# Format easting,northing,name,elevation (with header)
    130 gauges_filename = 'time_of_arrival_hobart.csv' #'TideGaugesPoints.csv' #'tsunamipointsMGA.csv'
    131 
    132 # BUILDINGS EXPOSURE - for identifying inundated houses
    133 # Used in run_building_inundation.py
    134 # Format latitude,longitude etc (geographic)
    135 building_exposure_filename = 'busselton_res_clip.csv' # from NEXIS
    136 
    137 # AREA OF IMAGES - Extent of each image to find out highest runup
    138 # Header - easting,northing,id,value
    139 # Used in get_runup.py
    140 images_filename = 'images.csv'
    141 
    142 # BOUNDING POLYGON - used in build_boundary.py and run_model.py respectively
     88gauges_filename = 'time_of_arrival_all.csv' #'TideGaugesPoints.csv'
     89                                            #'tsunamipointsMGA.csv'
     90
     91# FINAL BOUNDING POLYGON - used in build_boundary.py and run_model.py respectively
    14392# NOTE: when files are put together the points must be in sequence
    14493# For ease go clockwise!
    … …  
    153102landward_boundary_filename = 'landward_boundary.csv'
    154103
    155 # MUX input filename.
    156 # If a meta-file from EventSelection is used, set 'multi-mux' to True.
    157 # If a single MUX stem filename (*.grd) is used, set 'multi-mux' to False.
    158 ##mux_input_filename = event_number # to be found in event_folder
    159                                     # (ie boundaries/event_number/)
    160 ##multi_mux = False
    161 mux_input_filename = 'event.list'
    162 multi_mux = True
    163 
    164104#-------------------------------------------------------------------------------
    165105# Clipping regions for export to asc and regions for clipping data
    … …  
    167107#-------------------------------------------------------------------------------
    168108
    169 # ASCII export grid for Bruny
    170 xminBruny = 523900
    171 xmaxBruny = 533200
    172 yminBruny = 5204300
    173 ymaxBruny = 5213100
    174 
    175 # ASCII export grid for South Arms
    176 xminSArms = 532497
    177 xmaxSArms = 534326
    178 yminSArms = 5237028
    179 ymaxSArms = 5238465
    180 
    181 # ASCII export grid for Hobart Large
     109# ASCII export grid for Hobart Communities
    182110xminHobart = 520000
    183111xmaxHobart = 545000
    … …  
    283211    gauges = join(gauges_folder, gauges_filename)       
    284212
    285 # The absolute pathname for the building file
    286 # Used for run_building_inundation.py
    287 if building_exposure_filename:
    288     building_exposure = join(gauges_folder, building_exposure_filename)
    289 
    290 # The absolute pathname for the image file
    291 # Used for get_runup.py
    292 if images_filename:
    293     images = join(polygons_folder, images_filename)
    294 
    295 
    296 # full path to where MUX files (or meta-files) live
    297 mux_input = join(event_folder, mux_input_filename)
    298 
    299213#Multiple polygons in one CSV file to make internal polygons
    300 if not PriorityArea_filename == None:
    301     PriorityAreas = join(polygons_folder, PriorityArea_filename)
    302 
    303 
     214PriorityAreas = join(polygons_folder, PriorityArea_filename)
     215
     216

  • DVD_images/extra_files/Hobart/project/run_model.py

    r7206 r7300  
    6868# Create the STS file
    6969if not os.path.exists(project.event_sts + '.sts'):
    70     bub.build_urs_boundary(project.mux_input_filename, project.event_sts)
     70    print 'sts file has not been generated'
    7171
    7272# Read in boundary from ordered sts file

  • DVD_images/extra_files/Hobart/project/setup_model.py

    r7206 r7300  
    7777    sanity_error = True
    7878
    79 # if multi_mux is True, check if multi-mux file exists
    80 if project.multi_mux:
    81     if not exists(project.mux_input):
    82         print ("Sorry, MUX input file '%s' doesn't exist"
    83                % project.mux_input)
    84         sanity_error = True
    85 
    8679#-----
    8780# If this directory don't exist, EventSelection hasn't been run.
    … …  
    154147           % type(project.land_initial_conditions_filename))
    155148    raise Exception, msg
     149
    156150# Create list of interior polygons with scaling factor
    157151project.interior_regions = []

  • DVD_images/extra_files/browser_files/style.css

    r7205 r7300  
    1616table.code {
    1717        border-width: 1px 1px 1px 1px;
    18         border-spacing: 0px;
     18        border-spacing: -10px;
    1919        border-style: dashed dashed dashed dashed;
    2020        border-color: gray gray gray gray;
    2121        border-collapse: separate;
    22         background-color: rgb(250, 240, 230);
    23 }
    24 table.code th {
    25         border-width: 5px 5px 5px 5px;
    26         padding: 5px 5px 5px 5px;
    27         border-style: none none none none;
    28         border-color: gray gray gray gray;
    29         background-color: white;
    30         -moz-border-radius: 0px 0px 0px 0px;
     22        background-color: #ffffe6;
     23        -moz-border-radius: 5px 5px 5px 5px;
    3124}
    3225table.code td {
    33         border-width: 5px 5px 5px 5px;
    34         padding: 5px 5px 5px 5px;
     26      height: 20px;
     27        border-width: 0px 0px 0px 0px;
     28        padding: 0px 0px 0px 0px;
    3529        border-style: none none none none;
    3630        border-color: gray gray gray gray;
    3731        background-color: #ffffe6;
    38         -moz-border-radius: 0px 0px 0px 0px;
    3932}
     33
     34

  • DVD_images/update_DVD_images.py

    r7271 r7300  
    6565 'copy_proj_files': ['build_elevation.py', 'project.py', 'run_model.py',
    6666                     'export_results_max.py',  'get_timeseries.py',
    67                      'setup_model.py'],
     67                     'setup_model.py', 'build_urs_boundary.py'],
    6868
    6969 # copy 'visualisations' files or directories
    … …  
    8080 'data_src_path':   'data/new_south_wales/batemans_bay_tsunami_scenario_2009/anuga',
    8181 'arcgis_src_path': 'data/new_south_wales/batemans_bay_tsunami_scenario_2009/ArcGIS',
    82  'viz_src_path':    'data/tasmania/hobart_tsunami_scenario_2009/visualisations',
     82 'viz_src_path':    'data/new_south_wales/batemans_bay_tsunami_scenario_2009/visualisations',
    8383 'proj_src_path':   'sandpits/jgriffin/ANUGA/anuga_work/production/new_south_wales/batemans_bay',
    8484
    … …  
    118118                     'setup_model.py', 'build_elevation.py',
    119119                     'export_results_max.py',
    120                      'file_length.py'],
     120                     'file_length.py', 'build_urs_boundary.py'],
    121121
    122122 # copy 'arcgis' files or directories
    … …  
    130130 'data_src_path':   'data/new_south_wales/gosford_tsunami_scenario_2009/anuga',
    131131 'arcgis_src_path': 'data/new_south_wales/gosford_tsunami_scenario_2009/ArcGIS',
    132  'viz_src_path':    'data/tasmania/hobart_tsunami_scenario_2009/visualisations',
     132 'viz_src_path':    'data/new_south_wales/gosford_tsunami_scenario_2009/visualisations',
    133133 'proj_src_path':   'sandpits/jgriffin/ANUGA/anuga_work/production/new_south_wales/gosford',
    134134
    … …  
    163163 'copy_proj_files': ['export_results_max.py', 'file_length.py',
    164164                     'project.py', 'run_model.py', 'build_elevation.py',
    165                      'get_timeseries.py', 'setup_model.py'
     165                     'get_timeseries.py', 'setup_model.py',
     166                     'build_urs_boundary.py'
    166167                    ],
    167168
    … …  
    176177 'data_src_path':   'data/queensland/gold_coast_tsunami_scenario_2009/anuga',
    177178 'arcgis_src_path': 'data/queensland/gold_coast_tsunami_scenario_2009/ArcGIS',
    178  'viz_src_path':    'data/tasmania/hobart_tsunami_scenario_2009/visualisations',
     179 'viz_src_path':    'data/queensland/gold_coast_tsunami_scenario_2009/visualisations',
    179180 'proj_src_path':   'sandpits/lfountain/anuga_work/production/gold_coast_2009',
    180181
    … …  
    208209 'copy_proj_files': ['build_elevation.py', 'export_results_max.py', 'file_length.py',
    209210                     'project.py', 'run_model.py', 'setup_model.py',
    210                      'get_timeseries.py'
     211                     'get_timeseries.py', 'build_urs_boundary.py'
    211212                    ],
    212213
Note: See TracChangeset for help on using the changeset viewer.