Changeset 7620


Ignore:
Timestamp:
Feb 11, 2010, 4:43:41 PM (9 years ago)
Author:
griffin
Message:

Edits to html pages

Location:
DVD_images/extra_files/Geraldton
Files:
4 edited

Legend:

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

    r7514 r7620  
    2323
    2424  <a name="analysis scripts"><h2><b>Analysis Scripts</b></h2></a>
    25   There are number of analysis scripts on this disk that you can use to extract information from the SWW files
     25  There are number of analysis scripts on this disk that can be used to extract information from the ANUGA output (SWW) files
    2626  produced by a simulation run.  These scripts are not meant to be the definitive answer on how to get information
    2727  from SWW files, but are offered as an example of one way to do it.
     
    3232
    3333  <a name="export_results_max.py scripts"><h3><b>export_results_max.py</b></h3></a>
    34   The <font color="red">export_results_max.py</font> script can be used to create an ASC file that contains the maximum
    35   of an ANUGA variable or expression for each point in a user-defined ArcGIS grid on the simulation region.
     34  The <font color="red">export_results_max.py</font> script can be used to create an ASCI (.asc) file that contains the maximum
     35  of an ANUGA variable or expression for each point in a user-defined grid on the simulation region. ASCI files can then be imported into a GIS environment.
    3636  <p>
    37   You must change certain values within the <font color="red">export_results_max.py</font> file to get what you want:
     37  Certain values within the <font color="red">export_results_max.py</font> file must be changed to align with the correct output files:
    3838  <ul>
    39     <li> List the output folder names here, with one for each simulation you have run:
     39    <li> List the output folder names here, with one for each simulation run:
    4040<pre><font color="brown">    time_dir1 = '20090505_150430_run_final_0.8_58292_None_kvanputt'
    4141    time_dir2 = '20090505_150517_run_final_0_58292_None_kvanputt'</font></pre>
     
    4343  <p>Then modify the line:
    4444<pre><font color="brown">    time_dirs = [time_dir1, time_dir2]</font></pre>
    45          to include each of the variables you defined above.
     45         to include each of the variables defined above.
    4646         <p>
    47     <li> Your SWW output will have a name like <font color="red">geraldton.sww</font>. For a large model you
     47    <li> The SWW output will have a name like <font color="red">geraldton.sww</font>. For a large model you
    4848         may have more than one output file with extra filenames like <font color="red">geraldton_37860_0.sww</font>,
    4949         where the <b>37860</b> tells us that the timestep at the start of this file is 37860 sec. The
     
    5555    times = [20000, 40000, 60000]</font></pre>
    5656         <p>
    57          <i>Note we do not have to specify the first SWW file, only the extra file start times. If there are no extra SWW files,
     57         <i>Note that it is not necessary to specify the first SWW file, only the extra file start times. If there are no extra SWW files,
    5858         just do:</i>
    5959         <p>
    6060<pre><font color="brown">    times = []</font></pre>
    6161         <p>
    62     <li> Modify the <b>cellsize</b> value to set the size of the ArcGIS grid you require.  For example:
    63 <pre><font color="brown">    cellsize = 20              # ArcGIS grid cell size in metres</font></pre>
     62    <li> Modify the <b>cellsize</b> value to set the resolution of the output grid required.  For example:
     63<pre><font color="brown">    cellsize = 20              # Grid cell size in metres</font></pre>
    6464         <p>
    6565         <i>Note: That this value should not go beyond the most refined part of the mesh
    6666         i.e. if mesh resolution is 500m<sup>2</sup>, cellsize = (500 </i>x<i> 2)<sup>1/2</sup> = 32m</i>
    6767         <p>
    68     <li> You can get the maximum of a variable or expression over the entire model time, or for a single time in the simulation.
    69          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
     68    <li> Maximum values of a variable or expression may be extracted over the entire model time or for a single time in the simulation.
     69         Set <b>timestep</b> to the required time to extract the maximum for, or set it to <b>None</b> to extract
    7070         the maximum values over all timesteps:
    7171<pre><font color="brown">    timestep = None  # over all timesteps
    7272    #timestep = 0</font></pre>
    7373         <p>
    74          <i>Note that if you want the elevation use <b>timestep = 0</b>. Elevation does not change over time and you only need the
    75          first SWW file.</i>
     74         <i>Note that if extracting elevation use <b>timestep = 0</b>. Elevation does not change over time and therefore only the
     75         first SWW file is needed.</i>
    7676         <p>
    77     <li> If you want to clip the ArcGIS grid to one or more small regions then put the names of the regions of interest
     77    <li> To clip the ASCI grid to one or more small regions then put the names of the regions of interest
    7878         into the <b>area</b> list:
    7979<pre><font color="brown">    area = ['geraldton', 'NW', 'South']</font></pre>
    8080         <p>
    81          <i>Note that the name strings you put into the <b>area</b> list must match the names used in the
     81         <i>Note that the name strings in the <b>area</b> list must match the names used in the
    8282         <font color="red">project.py</font> file.  That is, if you use a name such as 'NW', then the
    8383         <font color="red">project.py</font> file must have lines like:</i>
     
    9191<pre><font color="brown">    area = ['All']             # no region of interest</font></pre>
    9292         <p>
    93     <li> Finally you must decide which variable or expression values you want sampled on your ArcGIS grid.
     93    <li> Finally the variable or expression values to be sampled on your ASCI grid must be specified.
    9494         Define a list <b>var</b> that contains strings defining the required variable or expression:
    9595<pre><font color="brown">    var = ['depth', 'speed']</font></pre>
    96          <i>Note that the strings you supply must be defined in the <b>var_equations</b> dictionary
    97          prior to your definition of <b>var</b>:</i>
     96         <i>Note that the strings supplied must be defined in the <b>var_equations</b> dictionary
     97         prior to definition of <b>var</b>:</i>
    9898<pre><font color="brown">    var_equations = {'stage':     'stage',
    9999                     'momentum':  '(xmomentum**2 + ymomentum**2)**0.5',
     
    101101                     'speed':     '(xmomentum**2 + ymomentum**2)**0.5/(stage-elevation+1.e-6)',
    102102                     'elevation': 'elevation' }</font></pre>
    103          This dictionary maps your <b>var</b> strings to a variable or expression.
     103         This dictionary maps the <b>var</b> strings to a variable or expression.
    104104  </ul>
    105105
     
    108108  data at one or more timeseries gauge points in a simulation.
    109109  <p>
    110   You must change certain values within the <font color="red">get_timeseries.py</font> file to get what you want:
     110  Certain values within the <font color="red">export_results_max.py</font> file must be changed to align with the correct output files:
    111111  <ul>
    112     <li> Depending on how many simulations you have run will determine the number of output folder names you insert here:
     112    <li> List the output folder names here, with one for each simulation run:
    113113<pre><font color="brown">    time_dir1 = '20090505_150430_run_final_0.8_58292_None_kvanputt'
    114114    time_dir2 = '20090505_150517_run_final_0_58292_None_kvanputt'</font></pre>
    115          as necessary. Then modify the line:
     115          Then modify the line:
    116116<pre><font color="brown">    time_dirs = [time_dir1, time_dir2]</font></pre>
    117          to include each of the variables you defined above.
     117         to include each of the variables defined above.
    118118         <p>
    119119    <li> Make sure that the <b>gauges</b> list specified in <font color="red">projects.py</font> contains one or more CSV files
    120          defining the gauges within the simulation that you want the timeseries data for.
     120         defining the synthetic gauges within the simulation that the timeseries data will be extracted for.
    121121         The gauge file must have this format:
    122122<pre><font color="brown">    easting,northing,name,elevation
     
    124124    532441.5164,5239639.686,Opossum,2</font></pre>
    125125  </ul>
     126    <p>
     127  <hr>
     128   <a rel="license" href="http://creativecommons.org/licenses/by-nc/3.0/"><img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by-nc/3.0/88x31.png" /></a><br />
     129  © Commonwealth of Australia (Geoscience Australia) 2010.
     130  This material is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nc/3.0/">Creative Commons Attribution-Noncommercial
     131  3.0 Australia License</a>. 
    126132</body>
    127133</html>
  • DVD_images/extra_files/Geraldton/index.html

    r7596 r7620  
    2424  <a name="introduction"><h3><b>Introduction</b></h3></a>
    2525  The information within this DVD is the result of a validation study of Geoscience Australia's tsunami modelling methodology.
    26   The Australian Government Attorney General’s Department (AGD) has supported Geoscience Australia (GA) in developing a
    27   range of products to support the understanding of tsunami hazard through the Australian Tsunami Warning System Project. This has involved the
    28   development of methodologies for modelling tsunami generation, propagation and inundation. The work reported here validates
     26  This has involved the development of methodologies for modelling tsunami generation, propagation and inundation. The work reported here validates
    2927  the tsunami modelling methodology against observational evidence of the 2004 Indian Ocean Tsunami. Results from deep water propagation modelling
    30   using the URSGA model are compared with satellite altimetry from <a href="http://topex-www.jpl.nasa.gov/mission/jason-1.html">Jason-1</a>. Timeseries from the URSGA model are used to drive
     28  using the URSGA model are compared with satellite altimetry from <a href="http://topex-www.jpl.nasa.gov/mission/jason-1.html">Jason-1</a>. Time series from the URSGA model are used to drive
    3129  the <a href="https://datamining.anu.edu.au/anuga">ANUGA</a> hydrodynamic model to simulate onshore inundation for Geraldton, Western Australia.
    3230  Inundation results are compared with observational data including
    33   <a href="http://www.dpi.wa.gov.au/imarine/19383.asp">tide gauge records</a> obtained from <a href="http://www.dpi.wa.gov.au/">The Department of Transport</a> in Western Australia
     31  <a href="http://www.dpi.wa.gov.au/imarine/19383.asp">tide gauge records</a> obtained from the <a href="http://www.dpi.wa.gov.au/">Department of Transport</a> in Western Australia
    3432  and <a href="field_observations" >field observations</a> collected by Guria Consulting.
    3533  <p>
    3634  While the associated report provides background, model results and interpretations, the DVD contains all data, scripts and
    3735  instructions for installing software necessary to reproduce and potentially augment the ANUGA inundation model underpinning the report.
    38   This includes modelled <a href="data/western_australia/geraldton_tsunami_scenario/anuga/boundaries/wa04_val">timeseries</a> of the 2004 tsunami along the entire Western Australian coast.
     36  This includes modelled <a href="data/western_australia/geraldton_tsunami_scenario/anuga/boundaries/wa04_val">time series</a> of the 2004 tsunami along the entire Western Australian coast.
    3937  This allows other users both to rerun the inundation model to test the validation and also to potentially run simulations for other Western Australian locations.
    4038  <p>
     
    4644    <li> <a href="data/western_australia/geraldton_tsunami_scenario/anuga/outputs/2004_tsunami_validation">Model outputs</a> including:
    4745    <ul>
    48       <li><a href="data/western_australia/geraldton_tsunami_scenario/anuga/boundaries/wa04_val">Mux files</a> containing timeseries of the tsunami for offshore Western Australia
    49       <li><a href="data/western_australia/geraldton_tsunami_scenario/anuga/outputs/2004_tsunami_validation">CSV files</a> containing timeseries of wave height and momentum
     46      <li><a href="data/western_australia/geraldton_tsunami_scenario/anuga/boundaries/wa04_val">Mux files</a> containing time series of the tsunami for offshore Western Australia
     47      <li><a href="data/western_australia/geraldton_tsunami_scenario/anuga/outputs/2004_tsunami_validation">CSV files</a> containing time series of wave height and momentum
    5048      for specific locations in the inundation model</ul>
    51     <li>Combined <a href="data/western_australia/geraldton_tsunami_scenario/anuga/topographies">elevation data</a> used by the simulation. Bathymetry data was supplied by
    52     <a href="http://www.dpi.wa.gov.au/">The Department of Transport</a> in Western Australia and a 1 m resolution onshore DEM was supplied by <a href="https://www.landgate.wa.gov.au/corporate.nsf">
     49    <li>Combined <a href="data/western_australia/geraldton_tsunami_scenario/anuga/topographies">elevation data</a> used by the simulation. Bathymetry data was supplied by the
     50    <a href="http://www.dpi.wa.gov.au/">Department of Transport</a> in Western Australia and a 1 m resolution onshore DEM was supplied by <a href="https://www.landgate.wa.gov.au/corporate.nsf">
    5351    Landgate</a>. Data is for non-commercial use only.
    5452    <li> The <a href="project">Python scripts</a> used to run the models
  • DVD_images/extra_files/Geraldton/installation.html

    r7514 r7620  
    2626  This document describes the installation and running of the simulation software.
    2727  <p>
    28   In addition, we show how to change your simulation, add new elevation data, etc, and how to get help if you have trouble.
     28  In addition, we show how to change a simulation, add new elevation data, etc, and how to get help if you have trouble.
    2929
    3030  <a name="requirements"><h3><b>Requirements</b></h3></a>
     
    4040
    4141  <a name="installing"><h3><b>Installing ANUGA</b></h3></a>
    42   <a href="http://sourceforge.net/projects/anuga/">Download Software</a><i>: please note Internet Explorer has the habit of renaming the
     42  <a href="http://sourceforge.net/projects/anuga/">Download Software</a><i>: please note Internet Explorer will rename the
    4343  .tgz file to .gz - the remedy is to rename them back or use another browser such as Firefox.</i>
    4444  <p>
    4545  You must install ANUGA according to the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
    46   As the installation procedure comprises a number of steps we suggest that it is carried out by someone with a
    47   basic understanding of how to install software packages on the operating system of choice.
    48 
     46  A 'one-click' installer exists for Windows but not for Linux. As the Linux installation procedure comprises a number of steps
     47  we suggest that it is carried out by someone with a basic understanding of how to install software packages.
     48 
    4949  <a name="simulating"><h3><b>How to run a simulation</b></h3></a>
    5050
    51   This is how you should run the model on this DVD.
     51  This is how the model on this DVD should be run.
    5252  We assume that you are using Windows and will give examples for that operating system.
    5353  The translation to Linux should be obvious, but the <a href="#userslist">ANUGA user's mailing list</a>
     
    5858  <hr align="left" width="100">
    5959  <p>
    60   First, it is assumed you have installed the ANUGA software according to the
     60  First, it is assumed the ANUGA software has been installed according to the
    6161  <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>.
    6262  <p>
    6363  <hr align="left" width="100">
    6464  <p>
    65   Next, you must copy the entire contents of the DVD to a place in your file system. Let's assume
    66   that you want to put the data into <b>C:\ANUGA</b>. You could drag all files from the DVD into this folder with Explorer.
     65  Next, copy the entire contents of the DVD to a place in your file system. Let's assume
     66  that you want to put the data into <b>C:\ANUGA</b>. Drag all files from the DVD into this folder with Explorer.
    6767  Or through the Command Prompt window:
    6868  <pre><font color="brown">
     
    7676  <hr align="left" width="100">
    7777  <p>
    78   Now you must create an environment variable <b>ANUGADATA</b> that points to the directory you just created:
     78  Now create an environment variable <b>ANUGADATA</b> that points to the directory just created:
    7979  <pre><font color="brown">
    8080    set ANUGADATA=C:\ANUGA
    8181  </font></pre>
    8282  Doing the above in a Command Prompt window is temporary - if you open another
    83   window you will not have the ANUGADATA environment variable defined. To make
    84   the variable permanent you must set it in the <b>Start|Settings|Control Panel|System</b>
     83  window the ANUGADATA environment variable will not be defined. To make
     84  the variable permanent set it in the <b>Start|Settings|Control Panel|System</b>
    8585  tool (<b>Advanced</b> tab).  See the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>
    8686  if you don't know how to do this.
    8787  <hr align="left" width="100">
    88   Next, you prepare and execute the model:
     88  Next, prepare and execute the model:
    8989  <pre><font color="brown">
    9090    cd C:\ANUGA
     
    107107  viewer as described in the <a href="documents/anuga_installation_guide.pdf">Installation Guide</a>
    108108  and <a href="documents/anuga_user_manual.pdf">User Manual</a>.  You may also
    109   generate rasters suitable for GIS mapping or write dedicated scripts extracting timeseries at selected
     109  generate ASCI grids that can be made suitable for GIS mapping or write dedicated scripts extracting timeseries at selected
    110110  locations.  Some hints to help you do this are at the <a href="analysis.html">analysis page</a>.
    111111  <p>
     
    121121  <a name="modifications"><h3><b>How to modify a simulation</b></h3></a>
    122122
    123   After you have run the supplied simulation you may wish to change it in some way, such as adding improved bathymetry data, for example.
     123  After running the supplied simulation you may wish to change it in some way, such as adding improved bathymetry data, for example.
    124124  The <a href="modifications.html">modifications</a> page explains how to do this.
    125125
     
    140140  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
    141141  it would be helpful to others.
     142 
     143  <p>
     144  <hr>
     145   <a rel="license" href="http://creativecommons.org/licenses/by-nc/3.0/"><img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by-nc/3.0/88x31.png" /></a><br />
     146  © Commonwealth of Australia (Geoscience Australia, Department of Transport Western Australia and Landgate) 2010.
     147  This material is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nc/3.0/">Creative Commons Attribution-Noncommercial
     148  3.0 Australia License</a>. 
     149 
    142150</body>
    143151</html>
  • DVD_images/extra_files/Geraldton/modifications.html

    r7596 r7620  
    2424  <a name="modifications"><h2><b>Modifying a simulation</b></h2></a>
    2525
    26   Here we talk about how to change the simulation.  Why would you need to change the simulation?  Well,
    27   you might have some better elevation data, or you want to run the simulation on a finer mesh in certain
    28   areas.
     26  Here we talk about how to change the simulation.  Reasons for modifying the simulation include the availability of
     27  better elevation data, or a desire to run the simulation on a finer mesh in certain areas.
    2928  <p>
    3029  First we describe the usage of the script files you might change, then we walk through a few examples
     
    111110  the initial water level will be at Mean Sea Level.  If you increase the <b>tide</b> value the water level will become deeper.
    112111  This setting will also increase non tidal lakes and rivers inside the model.  To compensate a mask is used on land called
    113   <b>initial conditions</b> which brings the internal water bodies back to 0.  Within ANUGA <b>tide</b> is modelled as a constant.
     112  <b>initial conditions</b> which brings the internal water bodies back to 0.  Please note that within ANUGA the <b>tide</b> is modelled as a constant
     113  change in sea level and does not vary with time.
    114114  <p>
    115115
     
    175175
    176176  The user can specify a number of internal polygons within each of which the resolution of the mesh can be specified.
    177   Mesh resolution is the maximum allowable area specified for each region, defining the largest area an indivdual
     177  Mesh resolution is the maximum allowable area specified for each region, defining the largest area an individual
    178178  triangular element of the mesh can take (and therefore the minimum mesh resolution).
    179179  These polygons need to be nested within each other with no overlapping edges.
     
    209209  <p>
    210210 
    211     <a name="Mux_files"><h4><b>Obtaining timeseries of the offshore tsunami wave for other locations</b></h4></a>
     211    <a name="Mux_files"><h4><b>Obtaining time series of the offshore tsunami wave for other locations</b></h4></a>
    212212 
    213   Mux files containing timeseries of the tsunami wave at points along the 100 m depth contour around Western Australia were obtained from the URSGA model.
    214   These timeseries form the seaward boundary condition for the ANUGA inundation model. To run an ANUGA simulation for a different area, tsunami timeseries for points
     213  Mux files containing time series of the tsunami wave at points along the 100 m depth contour around Western Australia were obtained from the URSGA model.
     214  These time series form the seaward boundary condition for the ANUGA inundation model. To run an ANUGA simulation for a different area, tsunami time series for points
    215215  offshore the location of interest must be extracted and reformatted into netCDF (.sts) format from the mux files. This is handled by the <font color="red">build_urs_boundary.py</font> script, which is
    216216  called from within <font color="red">run_model.py</font>.
    217   The points for which the timeseries are extracted are defined within the file <a href="data/western_australia/geraldton_tsunami_scenario/anuga/boundaries">urs_order.csv</a>.
     217  The points for which the time series are extracted are defined within the file <a href="data/western_australia/geraldton_tsunami_scenario/anuga/boundaries">urs_order.csv</a>.
    218218  This file must be modified as follows to run a model for a different area.
    219219  <p>
    220   The file <a href="data/western_australia/geraldton_tsunami_scenario/anuga/boundaries">urs_timeseries_locations.csv</a> contains a list of all the points for which timeseries exist within the mux files. This file can be loaded into a GIS environment and the points within the model selected.
    221   Note that you should only choose approximately every 5th points, keeping the points in as close to a straight line as possible.
     220  The file <a href="data/western_australia/geraldton_tsunami_scenario/anuga/boundaries">USRGA_gauges_all_WA.csv</a> contains a list of all the points for which timeseries exist within the mux files. This file can be loaded into a GIS environment and the points within the model selected.
     221  Note that you should only choose approximately every fifth point, keeping the points in as close to a straight line as possible.
    222222  Choosing points too close to each other can cause problems with fitting the mesh to the model domain.
    223223  These points should be written into a .csv file in the following format (including header):
     
    228228  <p>
    229229  If the name of this .csv file is changed from urs_order, then this must be updated in <font color="red">project.py</font>
    230  
     230   <p>
     231  <hr>
     232   <a rel="license" href="http://creativecommons.org/licenses/by-nc/3.0/"><img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by-nc/3.0/88x31.png" /></a><br />
     233  © Commonwealth of Australia (Geoscience Australia, Department of Transport Western Australia and Landgate) 2010.
     234  This material is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nc/3.0/">Creative Commons Attribution-Noncommercial
     235  3.0 Australia License</a>.   
    231236</body>
    232237</html>
Note: See TracChangeset for help on using the changeset viewer.