Changeset 3015


Ignore:
Timestamp:
May 30, 2006, 12:00:56 PM (18 years ago)
Author:
sexton
Message:

including references and more updates to report words

Location:
production
Files:
3 added
9 edited

Legend:

Unmodified
Added
Removed

  • production/onslow_2006/make_report.py

    r3007 r3015  
    234234     
    235235   \section{References}
    236 
     236    \input{references}
     237   
    237238   \section{Metadata}
    238239     \label{sec:metadata}

  • production/onslow_2006/plot_data_extent.py

    r2983 r3015  
    9898   
    9999    figure(3)
    100     figname = 'onslow_polys'
     100    figname = 'onslow_polys_test'
    101101    vec = plot_polygons([project.polyAll,
    102                         project.poly_onslow, project.poly_coast, project.poly_region],
     102                        project.poly_onslow, project.poly_coast],#, project.poly_region],
    103103                        figname,
    104104                        verbose = True)
    … …  
    121121    savefig(figname)
    122122
     123    figure(5)
     124    figname = 'onslow_new_boundary_test'
     125    x50, y50 = poly_xy(project.bounding_poly50)
     126    #x25, y25 = poly_xy(project.bounding_poly25)
     127    #plot(x50,y50,'r-',x25,y25,'r-',x1,y1,'g-')
     128    plot(x50,y50,'r-',x1,y1,'g-')
     129    savefig(figname)
    123130close('all')

  • production/onslow_2006/report/computational_setup.tex

    r3004 r3015  
    1313\begin{figure}[hbt]
    1414
    15   \centerline{ \includegraphics[width=100mm, height=75mm]{../report_figures/onslow_data_poly.png}}
     15  \centerline{ \includegraphics[width=100mm, height=75mm]
     16             {../report_figures/onslow_data_poly.png}}
    1617
    1718  \caption{Study area for Onslow scenario highlighting areas of increased refinement.}
    … …  
    2223\begin{figure}[hbt]
    2324
    24   %\centerline{ \includegraphics[width=100mm, height=75mm]{../report_figures/.png}}
     25  %\centerline{ \includegraphics[width=100mm, height=75mm]
     26  %            {../report_figures/.png}}
    2527
    2628  \caption{Computational mesh for Onslow study area}
    … …  
    4446those regions where complex behaviour will occur, such as the inter-tidal
    4547zone and estuaries.
     48
     49Whilst friction has been incorporated into the model, we have implemented it here.
     50We have an outstanding issue with regard how friction is
     51modelled which is not yet resolved.

  • production/onslow_2006/report/introduction.tex

    r2950 r3015  
    66coastline to tsunamigenic earthquakes originating from
    77the Sunda Arc subduction zone. There is
    8 historic evidence of such events and FESA has sought to assess
     8historic evidence of such events, \bibitem{CB:ausgeo},
     9and FESA has sought to assess
    910the relative risk of its urban and regional communities to the tsunami
    1011threat and develop detailed response plans.
    … …  
    2324ANUGA has been developed by GA and the Australian National University
    2425(ANU) to solve the nonlinear shallow water
    25 wave equation using the finite volume technique (described in [1]).
     26wave equation using the finite volume technique (described in \cite{ON:modsim}).
    2627An advantage of this technique is that the cell resolution can be changed
    2728according to areas of interest and that wetting and drying

  • production/onslow_2006/report/summary.tex

    r2950 r3015  
    11
    2 this will be the summary - put together by the team
     2Further modelling effort is required in the next financial year to
     3investigate the solution sensitivity to cell resolution and
     4bathymetry. Further investigation of the point at which
     5ANUGA can use the deep water model output is also required.

  • production/onslow_2006/report/tsunami_scenario.tex

    r2974 r3015  
    11The tsunamigenic event used for this study is one used
    22to develop the preliminary tsunami hazard assessment which
    3 was delivered to FESA in September 2005 (ref Burbidge, D. and
    4 Cummins, P. 2005). In that assessment, a suite of
     3was delivered to FESA in September 2005,
     4\bibitem{CB:FESA}. In that assessment, a suite of
    55tsunami were evenly spaced along the Sunda Arc subduction zone and there
    66was no consideration of likelihood. Other sources were not considered, such
    … …  
    3131\begin{figure}[hbt]
    3232
    33   \centerline{ \includegraphics[width=100mm, height=75mm]{../report_figures/mw9.jpg}}
     33  \centerline{ \includegraphics[width=100mm, height=75mm]
     34{../report_figures/mw9.jpg}}
    3435
    3536  \caption{Maximum wave height (in cms) for a Mw 9 event off the

  • production/pt_hedland_2006/make_report.py

    r2950 r3015  
    3434* an introduction must be written in introduction.tex; a basic outline and
    3535  some of the core inputs are already in place
    36 * an results.tex file needs to be written for the particular scenario
    37 * the tsunami-genic event should be discussed in tsunami_scenario.tex
     36  * the tsunami-genic event should be discussed in tsunami_scenario.tex
     37* a computational_setup.tex file needs to be written for the particular scenario
     38* the interpretation of the results needs to be written to interpretation.tex
     39* maximum inundation maps need to be included in HAT_map and LAT_map etc.
     40* damage modelling maps need to be included in HAT_damage and LAT_damage etc.
    3841* a summary must be written into summary.tex
    3942* metadata for the scenario data to be included in metadata.tex
    … …  
    4447from os import getcwd, sep, altsep, mkdir, access, F_OK
    4548import project
    46 from pyvolution.util import sww2timeseries
     49from pyvolution.util import sww2timeseries, get_gauges_from_file
    4750
    4851# Derive scenario name
    … …  
    5457    scenario_name = '%s %s' %(test[0], test[1])
    5558
     59# Create report directory
     60reportdir = getcwd()+sep+'report'+sep
     61if access(reportdir,F_OK) == 0:
     62    mkdir (reportdir)
     63   
    5664# User defined inputs
    5765report_title = 'Tsunami impact modelling for the North West shelf: %s' %scenario_name.title()
    … …  
    6068                   '': 'Lowest Astronomical Tide'}
    6169
     70max_maps = {'Highest Astronomical Tide': 'HAT_map',
     71            'Lowest Astronomical Tide': 'LAT_map'}
     72
     73damage_maps = {'Highest Astronomical Tide': 'HAT_damage',
     74               'Lowest Astronomical Tide': 'LAT_damage'}
     75 
    6276# Create sections and graphs for each designated production directory
    6377latex_output = []
    … …  
    7185                             label_id,
    7286                             report = True,
    73                              plot_quantity = ['stage', 'velocity', 'bearing'],
     87                             plot_quantity = ['stage', 'velocity'],
    7488                             time_min = None,
    7589                             time_max = None,
    76                              title_on = False,   
     90                             title_on = False,
    7791                             verbose = True)
    7892
    … …  
    8094
    8195
     96
    8297# Start report generation
    83 reportdir = getcwd()+sep+'report'+sep
    84 if access(reportdir,F_OK) == 0:
    85     mkdir (reportdir)
    8698report_name = reportdir + scenario + '_report.tex'
    8799fid = open(report_name, 'w')
    … …  
    94106% * an introduction must be written in introduction.tex; a basic outline and
    95107%   some of the core inputs are already in place
    96 % * an results.tex file needs to be written for the particular scenario
    97108% * the tsunami-genic event should be discussed in tsunami_scenario.tex
     109% * an computational_setup.tex file needs to be written for the particular scenario
     110% * the interpretation of the results needs to be written to interpretation.tex
     111% * maximum inundation maps need to be included in HAT_map.tex and LAT_map.tex etc.
     112% * damage modelling maps need to be included in HAT_damage and LAT_damage etc.
    98113% * a summary must be written into summary.tex
    99114% * metadata for the scenario data to be included in metadata.tex
    … …  
    151166  \section{Inundation modelling results}
    152167     \label{sec:results}
    153      \input{results}
     168     \input{computational_setup}
    154169     
    155170"""
     171fid.write(s)
     172
     173# Generate latex output for gauges
     174s = '\\begin{table} \label{table:gaugelocations} \n'
     175fid.write(s)
     176s = '\caption{Defined gauge locations for %s study area.}' %scenario_name.title()
     177fid.write(s)
     178s = """
     179\\begin{center}
     180\\begin{tabular}{|l|l|l|l|}\hline
     181\\bf{Gauge Name} & \\bf{Easting} & \\bf{Northing} & \\bf{Elevation}\\\\ \hline
     182"""
     183fid.write(s)
     184
     185gauges, locations = get_gauges_from_file(project.gauge_filename)
     186
     187for name, gauges in zip(locations, gauges):
     188    east = gauges[0]
     189    north = gauges[1]
     190    elev = 0.0
     191    #elev = gauges[2]
     192    s = '%s & %.2f & %.2f & %.2f \\\\ \hline \n' %(name.replace('_',' '), east, north, elev)
     193    fid.write(s)
     194
     195s = '\\end{tabular} \n  \end{center} \n \end{table} \n \n'
     196fid.write(s)
     197
     198s = '\input{interpretation} \n'
    156199fid.write(s)
    157200
    … …  
    162205    s = '\subsection{%s} \n \n' %production_dirs[name]     
    163206    fid.write(s)
    164    
     207
     208    s = '\input{%s} \n \clearpage \n \n' %max_maps[production_dirs[name]]
     209    fid.write(s)
     210
    165211    s = '\input{%s} \n \clearpage \n \n' %latex_output[i]
    166212    fid.write(s)
    167213
    168 
    169 # Closing   
     214# Closing
     215
    170216s = """
    171217   \section{Damage modelling}
    172218     \input{damage}
    173 
    174     \section{Summary}
     219"""
     220fid.write(s)
     221
     222for i, name in enumerate(production_dirs.keys()):
     223
     224    s = '\subsection{%s} \n \n' %production_dirs[name]     
     225    fid.write(s)
     226
     227    s = '\input{%s} \n \clearpage \n \n' %damage_maps[production_dirs[name]]
     228    fid.write(s)
     229
     230
     231s = """
     232   \section{Summary}
    175233     \input{summary}
    176234     
    177235   \section{References}
    178 
     236    \input{references}
     237   
    179238   \section{Metadata}
    180239     \label{sec:metadata}

  • production/pt_hedland_2006/report/computational_setup.tex

    r2983 r3015  
    88other important features such as islands and rivers.
    99The resultant computational mesh is then seen in \ref{fig:mesh_onslow}.
    10 
     10In contrast to the Onslow study, the most northern
     11boundary of the study area is placed approximately around the 50m contour
     12line. The driver for this change was the computational time taken to
     13develop the mesh and associate the points to that mesh. By comparison, the
     14100m contour for the Onslow study is approximately 100km from the coast,
     15with that distance approximately 200km for Pt Hedland. The increased
     16study area then increases the number of triangles, thereby increasing
     17the computational time. However, initial comparisons between the deep water
     18model MOST (Method of
     19Splitting Tsunami) and ANUGA show that they are reasonably well matched
     20to the 50m contour line. More detailed investigations are necessary to
     21confirm this position as the point may be dependent on the local bathymetry.
    1122
    1223\begin{figure}[hbt]
    1324
    14   \centerline{ \includegraphics[width=100mm, height=75mm]{../report_figures/pt_hedland_data_poly.png}}
     25  \centerline{ \includegraphics[width=100mm, height=75mm]
     26             {../report_figures/pt_hedland_data_poly.png}}
    1527
    1628  \caption{Study area for Pt Hedland scenario}
    17   \label{fig:pt_hedland_area}
     29  \label{fig:pthedland_area}
    1830\end{figure}
    1931
    … …  
    2436
    2537  \caption{Computational mesh for Pt Hedland study area}
    26   \label{fig:mesh_pthedland}
     38  \label{fig:meshpthedland}
    2739\end{figure}
     40
     41For the simulations, we have chosen a resolution of 500 m$^2$ for the
     42region surrounding the Pt Hedland town centre. The resolution is increased
     43to 2500 m$^2$ for the region surrounding the coast and further increased
     44to 100000 m$^2$ for the region reaching approximately the 50m contour line.
     45With these resolutions in place, the study area consists of ? triangles.
     46The associated accuracy
     47for these resolutions is approximatly 22m, 50m, and 315m for the increasing
     48resolutions. This means
     49that we can only be confident in the calculated inundation to approximately
     5022m accuracy within the Pt Hedland town centre.
     51This is because ANUGA calculates whether each cell in the triangular
     52mesh is wet or dry. It is important
     53to refine the mesh to be commensurate with the underlying data especially in
     54those regions where complex behaviour will occur, such as the inter-tidal
     55zone and estuaries.
     56
     57Whilst friction has been incorporated into the model, we have implemented it here.
     58We have an outstanding issue with regard how friction is
     59modelled which is not yet resolved.

  • production/pt_hedland_2006/report/introduction.tex

    r2950 r3015  
    66coastline to tsunamigenic earthquakes originating from
    77the Sunda Arc subduction zone. There is
    8 historic evidence of such events and FESA has sought to assess
     8historic evidence of such events, \bibitem{CB:ausgeo},
     9and FESA has sought to assess
    910the relative risk of its urban and regional communities to the tsunami
    1011threat and develop detailed response plans.
    … …  
    2324ANUGA has been developed by GA and the Australian National University
    2425(ANU) to solve the nonlinear shallow water
    25 wave equation using the finite volume technique (described in [1]).
     26wave equation using the finite volume technique (described in \cite{ON:modsim}).
    2627An advantage of this technique is that the cell resolution can be changed
    2728according to areas of interest and that wetting and drying
    2829is treated robustly as part of the numerical scheme.
    29 ANUGA is continually being developed and validated. 
     30ANUGA is continually being developed and validated.
    3031As such, the current results represent ongoing work
    3132and may change in the future.
Note: See TracChangeset for help on using the changeset viewer.