[7301] | 1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> |
---|
| 2 | <html> |
---|
| 3 | <head> |
---|
| 4 | <title>Geoscience Australia</title> |
---|
| 5 | <link rel="stylesheet" href="browser_files/style.css"> |
---|
| 6 | <link REL="SHORTCUT ICON" HREF="browser_files/favicon.ico"> |
---|
| 7 | </head> |
---|
| 8 | <body> |
---|
| 9 | <table cellspacing="10" border="0"> |
---|
| 10 | <tr> |
---|
| 11 | <td> |
---|
| 12 | <img src="browser_files/logo.jpg" alt="Australian Government, Geoscience Australia" width="327" height="80" border="0"/> |
---|
| 13 | </td> |
---|
| 14 | <td width="50"> |
---|
| 15 | |
---|
| 16 | </td> |
---|
| 17 | <td> |
---|
[7331] | 18 | <H1>Tsunami Inundation Models for south east Tasmania</H1> |
---|
[7301] | 19 | </td> |
---|
| 20 | </tr> |
---|
| 21 | </table> |
---|
| 22 | <hr> |
---|
| 23 | |
---|
| 24 | <a name="modifications"><h2><b>Modifying a simulation</b></h2></a> |
---|
| 25 | |
---|
[7331] | 26 | Here we talk about how to change a simulation. Why would you need to change a simulation? Well, |
---|
[7301] | 27 | 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 for different events. |
---|
| 29 | <p> |
---|
[7331] | 30 | First we describe the usage of the script files you might change, then we walk through a few examples |
---|
[7301] | 31 | of changes you might make. |
---|
| 32 | <p> |
---|
| 33 | |
---|
| 34 | <a name="project_files"><h3><b>The project scripts</b></h3></a> |
---|
| 35 | |
---|
| 36 | In the <b>project</b> directory are the scripts that control the simulation. These scripts are: |
---|
| 37 | <table class="code"> |
---|
| 38 | <tr><td><font color="red">project.py</font></td><td>Defines the input data used, where to place output, etc.</td></tr> |
---|
[7331] | 39 | <tr><td><font color="red">build_elevation.py</font></td><td>Combines the elevation data specified by <font color="red">project.py</font> into one file; with the extension .PTS</td></tr> |
---|
[7301] | 40 | <tr><td><font color="red">setup_model.py</font></td><td>Prepares the simulation before actually running it</td></tr> |
---|
| 41 | <tr><td><font color="red">run_model.py</font></td><td>Runs the simulation</td></tr> |
---|
| 42 | </table> |
---|
| 43 | |
---|
| 44 | <a name="project.py"><h4><b>project.py</b></h4></a> |
---|
| 45 | |
---|
| 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 | <a name="build_elevation.py"><h4><b>build_elevation.py</b></h4></a> |
---|
| 51 | |
---|
[7331] | 52 | This script combines all input elevation files into a single elevation point file (PTS file). |
---|
[7301] | 53 | We have provided you with the PTS file used to create the outputs on this DVD. |
---|
[7331] | 54 | If you would like to change the elevation, see <a href="#change">Making changes to a simulation</a>. |
---|
[7301] | 55 | <p> |
---|
| 56 | |
---|
| 57 | <a name="setup_model.py"><h4><b>setup_model.py</b></h4></a> |
---|
| 58 | |
---|
| 59 | This script is used to transform data into a specific format for <font color="red">run_model.py</font>, |
---|
| 60 | if required, and to generate warning messages if you are missing data. |
---|
| 61 | <p> |
---|
| 62 | |
---|
| 63 | <a name="run_model.py"><h4><b>run_model.py</b></h4></a> |
---|
| 64 | |
---|
| 65 | This script runs a tsunami inundation scenario. It relies on the parameters set in <font color="red">project.py</font> |
---|
[7331] | 66 | as well as the elevation and event input files (PTS and STS files respectively). |
---|
| 67 | An STS file has been generated for each event listed in the <u>boundaries</u> directory. For further details on events see |
---|
[7301] | 68 | <a href="#change">Making changes to a simulation</a>. |
---|
| 69 | <p> |
---|
| 70 | |
---|
| 71 | <a name="change"><h3><b>Making changes to a simulation</b></h3></a> |
---|
| 72 | |
---|
| 73 | There are many parameters that you can change within the <font color="red">project.py</font> script, |
---|
| 74 | but the following four parameters are those most commonly changed. |
---|
| 75 | <p> |
---|
| 76 | |
---|
[7331] | 77 | <a name="output"><h4><b>Output Folder Name</b></h4></a> |
---|
| 78 | |
---|
| 79 | The <b>output folder name</b> should be unique between different runs on different data. |
---|
| 80 | The list of items below will be used to create the folder in your <u>output</u> directory. |
---|
| 81 | Your user name and time+date will be automatically added. For example, |
---|
| 82 | <pre><font color="brown"> |
---|
| 83 | output_comments = [setup, tide, event_number]</font></pre> |
---|
| 84 | will result in a folder name like |
---|
| 85 | <pre><font color="brown"> |
---|
| 86 | 20090212_091046_run_final_0_27283_rwilson</font> |
---|
| 87 | Where you (<u>rwilson</u>) ran a <u>run</u> script at <u>9:10.46</u> in the morning on the <u>2/12/09</u>, <b>setup</b> = <u>final</u>, |
---|
| 88 | <b>tide</b> = <u>0</u>, <b>event_number</b> = <u>27283</u> - refer below for more information on these parameters </pre> |
---|
| 89 | <p> |
---|
| 90 | You can also add strings to this list |
---|
| 91 | <pre><font color="brown"> |
---|
| 92 | output_comments = [setup, tide, event_number, 'large']</font></pre> |
---|
| 93 | will result in a folder name like |
---|
| 94 | <pre><font color="brown"> |
---|
| 95 | 20090212_091046_run_final_0_27283_large_rwilson</font></pre> |
---|
| 96 | <p> |
---|
| 97 | <p> |
---|
| 98 | <a name="setup"><h4><b>Setup</b></h4></a> |
---|
| 99 | |
---|
| 100 | The <b>setup</b> parameter determines the type of run. This can be one of three values: |
---|
| 101 | <pre><font color="brown"> |
---|
| 102 | 'trial' <font color="black">- coarsest mesh, fast </font> |
---|
| 103 | 'basic' <font color="black">- coarse mesh</font> |
---|
| 104 | 'final' <font color="black">- fine mesh, slowest</font> |
---|
| 105 | </pre></font> |
---|
| 106 | Note: <b>'final'</b> must be used if determining the best estimate of inundation for your area of interest. |
---|
| 107 | <p> |
---|
[7301] | 108 | <a name="tide"><h4><b>Tide</b></h4></a> |
---|
| 109 | |
---|
[7331] | 110 | The <b>tide</b> parameter is used to change the mean inital water level of the simulation. When <b>tide</b> is set to 0 |
---|
[7301] | 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. |
---|
[7331] | 112 | This setting will also increase non tidal lakes and rivers inside the model. To compensate a mask is used on land called |
---|
| 113 | <b>initial conditions</b> which brings the internal water bodies back to 0. Within ANUGA <b>tide</b> is modelled as a constant. |
---|
[7301] | 114 | <p> |
---|
| 115 | |
---|
| 116 | <a name="events"><h4><b>Events</b></h4></a> |
---|
| 117 | |
---|
| 118 | The <b>event_number</b> variable contains the event number that initiates the tsunami we are modelling. |
---|
[7331] | 119 | You can change <b>event_number</b> to any event number in the <u>boundaries</u> directory. |
---|
| 120 | <a href="data/tasmania/hobart_tsunami_scenario_2009/anuga/boundaries/events_chosen.xls">Click here</a> for more information on the events. |
---|
| 121 | An STS file has been generated for all events listed in the <u>boundaries</u> directory. |
---|
[7301] | 122 | <p> |
---|
[7331] | 123 | The event numbers correspond to a quake ID from the Probabilistic Tsunami Hazard Map Assessment of Australia. |
---|
| 124 | |
---|
| 125 | <pre><font color="brown"> |
---|
| 126 | event_number = 58260 # 1 in 10000 yr event from Puysegur Trench</font></pre> |
---|
| 127 | |
---|
[7301] | 128 | <p> |
---|
| 129 | |
---|
| 130 | <a name="elevation"><h4><b>Elevation</b></h4></a> |
---|
| 131 | |
---|
[7331] | 132 | Elevation data can be changed in the <font color="red">project.py</font> script under ELEVATION DATA. |
---|
[7301] | 133 | Elevation data can be read as either a point file, comma delimited, or as an ASCII grid file |
---|
[7331] | 134 | (ASC) with an accompanying projection file (PRJ). All elevation input should sit in <u>topographies</u> and must be projected in the correct UTM zone. |
---|
[7301] | 135 | <p> |
---|
| 136 | |
---|
| 137 | A header for a CSV file has the format: |
---|
[7331] | 138 | |
---|
| 139 | <pre><font color="brown"> |
---|
| 140 | x,y,elevation</font></pre> |
---|
| 141 | |
---|
[7301] | 142 | <p> |
---|
| 143 | |
---|
| 144 | An ASC file header has the format: |
---|
[7331] | 145 | |
---|
| 146 | <pre><font color="brown"> |
---|
| 147 | ncols 868 |
---|
| 148 | nrows 856 |
---|
| 149 | xllcorner 418933.86055096 |
---|
| 150 | yllcorner 5151810.6668096 |
---|
| 151 | cellsize 250 |
---|
| 152 | NODATA_value -9999</font></pre> |
---|
| 153 | |
---|
[7301] | 154 | <p> |
---|
| 155 | |
---|
| 156 | The header of a PRJ file has the format: |
---|
[7331] | 157 | |
---|
| 158 | <pre><font color="brown"> |
---|
| 159 | Projection UTM |
---|
| 160 | Zone 55 |
---|
| 161 | Datum D_GDA_1994 |
---|
| 162 | Zunits NO |
---|
| 163 | Units METERS |
---|
| 164 | Spheroid GRS_1980 |
---|
| 165 | Xshift 500000 |
---|
| 166 | Yshift 10000000 |
---|
| 167 | Parameters</font></pre> |
---|
| 168 | |
---|
[7301] | 169 | <p> |
---|
| 170 | |
---|
[7331] | 171 | The elevation filenames in <font color="red">project.py</font> must be listed in either <b>point_filenames</b> or <b>ascii_grid_filenames</b> |
---|
[7301] | 172 | depending on their format. Point files need to have their extension shown however the ascii grid files have the .asc extension assumed: |
---|
| 173 | |
---|
[7331] | 174 | <pre><font color="brown"> |
---|
| 175 | point_filenames = ['point1.csv', |
---|
| 176 | 'point2.csv', |
---|
| 177 | 'point3.csv'] |
---|
| 178 | |
---|
| 179 | ascii_grid_filenames = ['grid1', |
---|
| 180 | 'grid2', |
---|
| 181 | 'grid3']</font></pre> |
---|
| 182 | |
---|
[7301] | 183 | <p> |
---|
| 184 | |
---|
| 185 | For further information on ANUGA file formats please see the ANUGA User Manual, section 6.1. |
---|
| 186 | <p> |
---|
| 187 | |
---|
| 188 | <a name="interior_regions"><h4><b>Interior regions</b></h4></a> |
---|
| 189 | |
---|
[7331] | 190 | The user can specify a number of internal polygons within each of which the resolution of the mesh can be specified. |
---|
| 191 | Mesh resolution is the maximum allowable area specified for each region, defining the largest area an indivdual |
---|
| 192 | triangular element of the mesh can take (and therefore the minimum mesh resolution). |
---|
| 193 | These polygons need to be nested within each other with no overlapping edges. |
---|
[7301] | 194 | <p> |
---|
[7331] | 195 | The <b>interior regions</b> can be changed in the <font color="red">project.py</font> script under INTERIOR REGIONS. |
---|
| 196 | Interior regions can be read as either seperate CSV files for each polygon displayed as a listed paired with its |
---|
| 197 | resolution and/or one CSV file for all polygons, where its resolution is defined within the csv under 'id'. |
---|
| 198 | All file inputs should sit in <u>polygons</u> and must be projected in the correct UTM zone. |
---|
| 199 | <p> |
---|
| 200 | The format for a CSV file with ONE polygon has the format: |
---|
| 201 | <pre><font color="brown"> |
---|
| 202 | easting,northing </font><font color="black"> Note: NO Header </font></pre> |
---|
| 203 | |
---|
| 204 | |
---|
| 205 | The header for a CSV file with MANY polygons has the format: |
---|
| 206 | <pre><font color="brown"> |
---|
| 207 | easting,northing,id,value</font></pre> |
---|
| 208 | <p> |
---|
| 209 | Where id = polygon number and value = maximum allowable area. |
---|
| 210 | <p> |
---|
| 211 | The <font color="red">project.py</font> script for this section looks like this: |
---|
| 212 | |
---|
| 213 | |
---|
| 214 | <pre><font color="brown"> |
---|
| 215 | interior_regions_list = [['aos1.csv', 1500], |
---|
| 216 | ['aos2.csv', 1500], |
---|
| 217 | ['sw.csv', 30000]] |
---|
| 218 | interior_regions_multiple_csv = 'PriorityAreas.csv'</font></pre> |
---|
| 219 | |
---|
| 220 | <p> |
---|
| 221 | |
---|
| 222 | For further information on ANUGA file formats please see the ANUGA User Manual, section 5.1. |
---|
| 223 | <p> |
---|
[7301] | 224 | </body> |
---|
| 225 | </html> |
---|
[7331] | 226 | |
---|