Ignore:
Timestamp:
Dec 21, 2009, 11:04:40 AM (15 years ago)
Author:
jgriffin
Message:
 
Location:
DVD_images/extra_files/Geraldton
Files:
3 edited

Legend:

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

    r7595 r7596  
    2828  development of methodologies for modelling tsunami generation, propagation and inundation. The work reported here validates
    2929  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. Timeseries from the URSGA model are used to drive
     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
    3131  the <a href="https://datamining.anu.edu.au/anuga">ANUGA</a> hydrodynamic model to simulate onshore inundation for Geraldton, Western Australia.
    32   Inundation results are compared with  <a href="field_observations" >observational data</a>  collected following the the tsunami.
     32  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
     34  and <a href="field_observations" >field observations</a> collected by Guria Consulting.
    3335  <p>
    3436  While the associated report provides background, model results and interpretations, the DVD contains all data, scripts and
    35   instructions for installing software necessary to reproduce and potentially augment the ANUGA model underpinning the report.
    36   This allows other users to rerun the models to test the validation.
     37  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.
     39  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.
    3740  <p>
    3841  The data provided on this DVD is:
     
    4043    <li> Geoscience Australia Record 2009/XX entitled <blink><i><a href="documents/Horspool_et_al_GA_record_2009_XX.pdf">Tsunami modelling validation:
    4144         the impact of the 2004 Indian Ocean Tsunami on Geraldton, Western Australia</a></i></blink>
    42     <li> <a href="field_observations" >Observational data</a> collected from the Western Australian coast following the tsunami
     45    <li> <a href="field_observations" >Field observations</a> collected from the Western Australian coast following the tsunami
    4346    <li> <a href="data/western_australia/geraldton_tsunami_scenario/anuga/outputs/2004_tsunami_validation">Model outputs</a> including:
    4447    <ul>
    45       <li>CSV files containing timeseries for specific locations in the models
    46         <li>Mux files containing timeseries for specific locations in the models</ul>
    47     <li> Combined <a href="data/western_australia/geraldton_tsunami_scenario/anuga/topographies">elevation data</a> used by the simulation
     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
     50      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">
     53    Landgate</a>. Data is for non-commercial use only.
    4854    <li> The <a href="project">Python scripts</a> used to run the models
    4955  </ul>
     
    5359
    5460  Information for installing <a href="https://datamining.anu.edu.au/anuga">ANUGA</a> and using the simulation is <a href="installation.html">here</a>.
     61  <p>
     62  <hr>
     63   <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 />
     64  © Commonwealth of Australia (Geoscience Australia, Department of Transport Western Australia and Landgate) 2010.
     65  This material is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nc/3.0/">Creative Commons Attribution-Noncommercial
     66  3.0 Australia License</a>. 
    5567
    5668</body>
  • DVD_images/extra_files/Geraldton/modifications.html

    r7514 r7596  
    208208  For further information on ANUGA file formats please see the ANUGA User Manual, section 5.1.
    209209  <p>
     210 
     211    <a name="Mux_files"><h4><b>Obtaining timeseries of the offshore tsunami wave for other locations</b></h4></a>
     212 
     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
     215  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
     216  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>.
     218  This file must be modified as follows to run a model for a different area.
     219  <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.
     222  Choosing points too close to each other can cause problems with fitting the mesh to the model domain.
     223  These points should be written into a .csv file in the following format (including header):
     224 
     225   <pre><font color="brown">
     226  index, longitude, latitude</font></pre>
     227
     228  <p>
     229  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 
    210231</body>
    211232</html>
  • DVD_images/extra_files/Geraldton/project/run_model.py

    r7514 r7596  
    1 """Run a tsunami inundation scenario for Gosford, NSW, Australia.
     1"""Run a tsunami inundation scenario for Geraldton, WA, Australia.
    22
    33The scenario is defined by a triangular mesh created from project.polygon, the
    44elevation data is compiled into a pts file through build_elevation.py and a
    5 simulated tsunami is generated through an sts file from build_boundary.py.
     5tsunami boundary condition is generated through an sts file from build_boundary.py.
    66
    77Input: sts file (build_boundary.py for respective event)
Note: See TracChangeset for help on using the changeset viewer.