Changeset 2898
- Timestamp:
- May 17, 2006, 5:16:42 PM (18 years ago)
- Location:
- production
- Files:
-
- 2 deleted
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
production/onslow_2006/make_report.py
r2870 r2898 34 34 * an introduction must be written in introduction.tex; a basic outline and 35 35 some of the core inputs are already in place 36 * an interpretation.tex file needs to be written for the particular scenario36 * an results.tex file needs to be written for the particular scenario 37 37 * any data issues must be included in data_issues.tex (data.tex should 38 38 be revised for future reports) … … 59 59 report_title = 'Tsunami impact modelling for the North West shelf: %s' %scenario_name.title() 60 60 61 production_dirs = {'20060424_020426_duplictate_time_steps': 'Highest Astronomical Tide', 62 '20060426_004129': 'Lowest Astronomical Tide'} 61 #production_dirs = {'20060424_020426_duplictate_time_steps': 'Highest Astronomical Tide', 62 # '20060426_004129': 'Lowest Astronomical Tide'} 63 64 production_dirs = {'20060426_004129': 'Highest Astronomical Tide', 65 '20060426_004237': 'Lowest Astronomical Tide'} 63 66 64 67 # Create sections and graphs for each designated production directory … … 76 79 time_min = None, 77 80 time_max = None, 78 title_on = False, 81 title_on = False, 79 82 verbose = True) 80 83 … … 93 96 % * an introduction must be written in introduction.tex; a basic outline and 94 97 % some of the core inputs are already in place 95 % * an interpretation.tex file needs to be written for the particular scenario98 % * an results.tex file needs to be written for the particular scenario 96 99 % * any data issues must be included in data_issues.tex (data.tex should 97 100 % be revised for future reports) … … 153 156 \label{sec:results} 154 157 \input{results} 155 \input{interpretation}156 158 157 159 """ -
production/onslow_2006/results.tex
r2834 r2898 3 3 computational time and desired resolution in areas of interest, 4 4 particularly in the interface between the on and offshore. The 5 following series offigures illustrate the study extent for the5 following figures illustrate the study extent for the 6 6 scenario and the resulting computational mesh, highlighting areas 7 7 of refinement around areas of particular interest. … … 9 9 \begin{figure}[hbt] 10 10 11 %\centerline{ \includegraphics[width=75mm, height=75mm]{ figures/.eps}}11 %\centerline{ \includegraphics[width=75mm, height=75mm]{.png}} 12 12 13 13 \caption{Study area for Onslow scenario} … … 18 18 \begin{figure}[hbt] 19 19 20 %\centerline{ \includegraphics[width=75mm, height=75mm]{ figures/.eps}}20 %\centerline{ \includegraphics[width=75mm, height=75mm]{.png}} 21 21 22 22 \caption{Computational mesh for Onslow study area} … … 24 24 \end{figure} 25 25 26 For the simulations, we have chosen a resolution of 500 m$^2$ for the 27 region surrounding the Onslow town centre. The resolution is increased 28 to 2500 m$^2$ for the region surrounding the coast and further increased 29 to 20000 m$^2$ for the remainder of the study area. With these 30 resolutions in place, the study area consists of 440150 triangles. The 31 associated accuracy 32 for these resolutions is approximatly 22m, 50m and to 140m. This means 33 that we can only be confident in the calculated inundation to approximately 34 22m accuracy. This is because ANUGA calculates whether each cell in the triangular 35 mesh is is wet or dry. It is important 36 to refine the mesh to be commensurate with the underlying data especially in 37 those regions where complex behaviour will occur, such as the inter-tidal 38 zone and estuaries. 39 40 The following subsections detail the time series at select locations 41 for high, low and zero tide conditions. These locations have 42 been chosen to assist in describing the features of the tsunami wave 43 and the resultant impact ashore. 44 45 \subsection{Features of the tsunami wave} 46 47 direction? multiple waves? amplitude offshore? 48 49 \subsection{Effect of geographical features} 50 51 It is evident for each simulation that the sand dunes west of Onslow 52 are very effective in halting the tsunami wave. The height of these 53 sand dunes are approximately 10m which is more than enough to halt 54 the largest of the tsunami waves which occurs for the 55 high tide simulation. There is inundation between the sand dunes at high 56 tide, however, this water penetrated from the north east (via 57 Onslow town cetnre) rather than seaward. 58 The same feature is evident for the sand dunes east of Onslow which 59 rise to 15m in height. Currently, ANUGA can not model changes 60 to the bathymetry or topography due to effects of the water flow. 61 Therefore, we do not know whether these sand dunes would withstand the 62 transmitted energy of the tsunami wave. 63 64 The wave penetrates the river east of Onslow with increasingly 65 greater inundation as the tide changes from LAT to HAT. 66 67 \subsection{Tidal effects and impact ashore} 68 69 As expected, there is greater inundation at high tide. The major road 70 into Onslow, the Onslow Mount Stuart Rd, remains free of inundation for 71 all tidal scenarios. Beadon Creek Rd which services the wharf in the 72 river becomes increasingly inundated as the tide rises. Only the 73 entry to the wharf on Beadon Creek Rd is sufficiently inundation at LAT 74 to stop traffic, however, at HAT essentially the entire road 75 would be impassable. 76 77 There is significant inundation of at 78 least 2m on the foreshore of Onslow for zero and high tide. 79 The inundation extent increases as the tide rises, pushing the edges 80 of the majority of the road infrastructure in the Onslow town centre. -
production/onslow_2006/run_timeseries.py
r2839 r2898 6 6 7 7 # define directory location of sww and gauge data 8 timestampdir = '2006042 4_020426_duplictate_time_steps'8 timestampdir = '20060426_004129' 9 9 file_loc = project.outputdir + timestampdir + sep #project.outputtimedir 10 10 swwfile = file_loc + project.basename + '.sww' -
production/pt_hedland_2006/make_report.py
r2870 r2898 34 34 * an introduction must be written in introduction.tex; a basic outline and 35 35 some of the core inputs are already in place 36 * an interpretation.tex file needs to be written for the particular scenario36 * an results.tex file needs to be written for the particular scenario 37 37 * any data issues must be included in data_issues.tex (data.tex should 38 38 be revised for future reports) … … 93 93 % * an introduction must be written in introduction.tex; a basic outline and 94 94 % some of the core inputs are already in place 95 % * an interpretation.tex file needs to be written for the particular scenario95 % * an results.tex file needs to be written for the particular scenario 96 96 % * any data issues must be included in data_issues.tex (data.tex should 97 97 % be revised for future reports) … … 153 153 \label{sec:results} 154 154 \input{results} 155 \input{interpretation}156 155 157 156 """
Note: See TracChangeset
for help on using the changeset viewer.