1 | %FIXME: Take stuff from future_directions.txt and wiki |
---|
2 | |
---|
3 | \documentclass[11pt]{report} |
---|
4 | |
---|
5 | \title{AnuGA Inundation Modelling Project - Planning and Priorities - Draft} |
---|
6 | \author{Ole Nielsen, Duncan Gray, Jane Sexton, Nick Bartzis,\\ Trevor Dhu, Neil Corby, Stephen Roberts, ...} |
---|
7 | |
---|
8 | |
---|
9 | \date{7 April, 2006} % update before release! |
---|
10 | % Use an explicit date so that reformatting |
---|
11 | % doesn't cause a new date to be used. Setting |
---|
12 | % the date to \today can be used during draft |
---|
13 | % stages to make it easier to handle versions. |
---|
14 | |
---|
15 | %\release{1.0} % release version; this is used to define the |
---|
16 | % \version macro |
---|
17 | |
---|
18 | \makeindex % tell \index to actually write the .idx file |
---|
19 | |
---|
20 | \begin{document} |
---|
21 | \maketitle |
---|
22 | |
---|
23 | \section*{Overview} |
---|
24 | |
---|
25 | The ANUGA inundation modelling project is a collaborative effort between |
---|
26 | Geoscience Australia (GA) and the Australian National University |
---|
27 | (ANU). GA is largely responsible for the software development, |
---|
28 | applications to scenario and risk modelling projects as well as |
---|
29 | contributions to the Australian National Research Priorities. |
---|
30 | ANU is mainly responsible for the mathematical and numerical modelling approach and the continued development of the model. |
---|
31 | |
---|
32 | |
---|
33 | This |
---|
34 | document outlines the agreed priorities for the inundation modelling |
---|
35 | project predominantly seen from the GA perspective, but including the ANU where appropriate. |
---|
36 | Priorities are organised into three separate streams focusing at the following objectives: |
---|
37 | \begin{enumerate} |
---|
38 | \item Deliverables of specific case studies. These are typically |
---|
39 | tasks that are requested by GA's clients. |
---|
40 | \item Research topics that have emerged and would advance the |
---|
41 | understanding of the science of hydrodynamic inundation |
---|
42 | \item Development and maintenance issues that are necessary for the |
---|
43 | continued health of the software itself. |
---|
44 | \end{enumerate} |
---|
45 | where the first is primarily resourced by Jane Sexton and Nick Bartzis, the second by Stephen Roberts and Ole Nielsen, while the third is the responsibility of Ole Nielsen and Duncan Gray. Significant overlaps are expected and names assigned to tasks are tentative only. |
---|
46 | |
---|
47 | Overarching these three streams is a fourth stream, management, which covers coordination of the FESA project and management of the inundation modelling team. |
---|
48 | |
---|
49 | \section*{Specific case studies (production)} |
---|
50 | |
---|
51 | |
---|
52 | |
---|
53 | The list in order of importance but subject to availability of |
---|
54 | topographic data and URS/MOST input is |
---|
55 | |
---|
56 | \begin{enumerate} |
---|
57 | \item Continual work on WA localities, in particular |
---|
58 | \item Onslow, WA. This study mainly supports the FESA funded WA study, but has synergies with |
---|
59 | projects in other lists as well (Jane, Ole, Nick) |
---|
60 | \item Wrap up Sydney (Benfield) project including refinements and damage modelling. |
---|
61 | This project has synergies with the ANUGA Demo initiative (Everyone) |
---|
62 | \item Port Hedland. Also part of the WA project. (Jane, Nick) |
---|
63 | \item Rerun Wollongong with slump (pending better defition of slump sizes) (Nick, Adrian), 2-3 weeks |
---|
64 | \item NSW state study (deferred until 2007 - Matt) |
---|
65 | \item SE Qld study |
---|
66 | \item Hobart |
---|
67 | \item Other study areas may be identified when the national hazard map has been completed (expected |
---|
68 | within the next 12 months) and consultation has occurred with stakeholders. |
---|
69 | \end{enumerate} |
---|
70 | Given that the production line is in a start-up phase and the needs |
---|
71 | outlined in the research and development streams, only priority 1 and |
---|
72 | 2 are guaranteed to complete before 30 June 2006. However, once |
---|
73 | streamlined, we expect a production rate of about one scenario per |
---|
74 | month. |
---|
75 | |
---|
76 | |
---|
77 | |
---|
78 | \section*{Research topics} |
---|
79 | |
---|
80 | The list is |
---|
81 | |
---|
82 | \begin{enumerate} |
---|
83 | \item Sensitivity study using Onslow project (Jane, Ole) |
---|
84 | \item Validation (Ole et al with David Burbidge \& Tom Baldock UQ). Also PDC and Suva data. |
---|
85 | \item Comparison of MOST and ANUGA over a stretch of deep water. Also, where to pick up boundary condition. |
---|
86 | \item Momentum sink study (Duncan) |
---|
87 | \item Submarine landslide modelling paper with Dr Mueller or Russell Blong (Ask him), Sydney (Jane, Ole, Adrian, Matt). Perhaps use Wollongong as the study area. |
---|
88 | \item Probabilistic integration with URS model, pending URS data (Ole, Trevor). Ask PDC. |
---|
89 | \item Automatic definition of mesh-resolution based on data (e.g. depth or gradients). Perhaps use wavelet transforms. Stephen has a link to a researcher at Imperial College, London. |
---|
90 | \item Investigate behaviour near steep and shallow bathymetries, where artifitial fluxes may be generated. |
---|
91 | \item Effect of debris on flow and damage (Under way at JCU - shawn) |
---|
92 | \item Write ANUGA in term of latitudes and longitudes |
---|
93 | \item Incorporate coriolis effect for large study areas |
---|
94 | \item Revive storm surge model (Rosh DNR) |
---|
95 | \item Riverine flooding (Rosh DNR) |
---|
96 | \item Collaboration with Hans Peter ?? (Stephen Roberts) |
---|
97 | \item Solution uncertainty (interaction with Hugh Durrant-Whyte and |
---|
98 | Suresh Kumar from USyd) |
---|
99 | \item Scenario database (future); this could complement the ATWS |
---|
100 | operational centre. (how often would it need to be updated, i.e how |
---|
101 | long will the results remain valid? eg, effect of sediment transport |
---|
102 | affecting local bathymetry, change in sea levels due to climate |
---|
103 | change). This is a product for the ATWS, states and EMA. |
---|
104 | \end{enumerate} |
---|
105 | No more than priority 1-4 are expected to complete before 30 June 2006. |
---|
106 | |
---|
107 | |
---|
108 | \section*{Development and maintenance issues.} |
---|
109 | |
---|
110 | The list is |
---|
111 | |
---|
112 | \begin{enumerate} |
---|
113 | \item Bug fixing (see tickets in TRAC) - ongoing (Duncan \& Ole) |
---|
114 | \item Integrated damage modelling (Nick?) |
---|
115 | \item Streamlined end-to-end process including production management of files (Ole, Neil, Nick, Jane, Duncan) |
---|
116 | \item Map2PDF vs ArcReader (Neil) |
---|
117 | \item Easy interface to building regions of variable resolution (Duncan) |
---|
118 | \item Sydney demo (Jane, Duncan, Ole) - Ask |
---|
119 | \item Deploy parallel version (Ole, Nick) |
---|
120 | \item Userguide, technical documentation and installation process (Everyone) |
---|
121 | \item OSS License (Ole) |
---|
122 | \item Visualisation (Nick, Ole) |
---|
123 | \begin{itemize} |
---|
124 | \item Hand crafted using Houdini |
---|
125 | \item Take Swollen-viewer further, e.g.\ by colour coding quantitios or applying contour plots |
---|
126 | \end{itemize} |
---|
127 | |
---|
128 | \end{enumerate} |
---|
129 | It is the hope that most of these priorities will be adressed before 30 June 2006. |
---|
130 | |
---|
131 | |
---|
132 | \section*{Roles and responsibilities} |
---|
133 | |
---|
134 | |
---|
135 | This is a first cut only. Please comment! |
---|
136 | |
---|
137 | |
---|
138 | \subsection*{Inundation modelling team} |
---|
139 | \begin{enumerate} |
---|
140 | \item \textbf{Duncan}: Take responsibility for the code development and maintenance. |
---|
141 | Represent the inundation modelling project in the corporate IM context. |
---|
142 | Take responsibility for one or more research projects, and contribute to production on a needs basis. |
---|
143 | \item \textbf{Jane}: Coordinate FESA production project, take responsibility for one or |
---|
144 | more research projects and contribute to production and code development on a needs basis. In the longer term, maintenance of other stakeholder relationships (?). |
---|
145 | \item \textbf{Nick}: Take responsibility for the production stream, develop visualisation techniques, |
---|
146 | and contribute to code development on a needs basis. |
---|
147 | \item \textbf{Ole}: Coordinate the inundation modelling project. |
---|
148 | Manage the balance and requirements between the research, development and production stream. |
---|
149 | Take responsibility for the code development and maintenance as well as one or more research projects. |
---|
150 | Contribute to production on a needs basis. |
---|
151 | \end{enumerate} |
---|
152 | |
---|
153 | |
---|
154 | \subsection*{Stakeholders} |
---|
155 | \begin{enumerate} |
---|
156 | \item \textbf{Adrian or Monica}: Provide input to submarine landslide research. |
---|
157 | \item \textbf{Hamish}: Coordinate collection and supply of topographic data. |
---|
158 | \item \textbf{Neil and Ingo}: Coordinate development of GIS decision tool. |
---|
159 | Assist with collection and supply of topographic data. |
---|
160 | \item \textbf{Stephen}: Contribute to research and further development of hydrodynamic model. |
---|
161 | \item \textbf{Trevor}: Develop new engagements with external stakeholders such as state governments. |
---|
162 | \item \textbf{Lisa}: Arcview exposure database with Neil |
---|
163 | |
---|
164 | \item Others? |
---|
165 | \end{enumerate} |
---|
166 | |
---|
167 | \subsection*{Potential contacts} |
---|
168 | |
---|
169 | \begin{itemize} |
---|
170 | \item Lex Nielsen from SMEC in order to explore |
---|
171 | how they can get involved |
---|
172 | \item Lutz Grosz from ACcESS |
---|
173 | \item Tom Baldock UQ |
---|
174 | \item Tariq Rahiman (tir14@student.canterbury.ac.nz, tariq@mrd.gov.fj) (Suva scenario) |
---|
175 | \item Allen L. Clark PDC (aclark@pdc.org) |
---|
176 | \item Roy Walters, NIWA (tsunami modelling) |
---|
177 | \item Russell Blong, Benfield (landslide modelling) |
---|
178 | \item Ray Steedman, WA oceanography (By way of Norm Schramm) |
---|
179 | \item Rosh Ranasinghe (DPNR) |
---|
180 | \item Suresh Kumar (ACFR) |
---|
181 | \end{itemize} |
---|
182 | |
---|
183 | |
---|
184 | \subsection*{Resources} |
---|
185 | |
---|
186 | The allocation to the different streams from the core inundation modelling team in terms of |
---|
187 | 4 full time equivalents (FTE) are |
---|
188 | |
---|
189 | \begin{itemize} |
---|
190 | \item \textbf{Production}: 1.25 FTE (Mainly Nick) |
---|
191 | \item \textbf{Research}: 1 FTE |
---|
192 | \item \textbf{Code development and maintenance}: 1 FTE |
---|
193 | \item \textbf{Management}: 0.75 FTE (0.5 WA-FESA Project coordination, 0.25 TEAM) |
---|
194 | \end{itemize} |
---|
195 | |
---|
196 | |
---|
197 | \chapter{Detailed planning} |
---|
198 | |
---|
199 | \section{Validation of ANUGA} |
---|
200 | |
---|
201 | \subsection{Laboratory Data} |
---|
202 | 25 July 2005: Benchmark data from wave tank experiments |
---|
203 | were deemed suitable for |
---|
204 | initial validation exercises and we should proceed with these |
---|
205 | immediately using the existing acquired datasets. In addition, data |
---|
206 | from vertical wall run-ups will be relevant. Andrew's letter to key |
---|
207 | players regarding other existing laboratory datasets is deemed |
---|
208 | extremely valuable and should go ahead. |
---|
209 | This has now completed in the form of the Okushiri island validation |
---|
210 | |
---|
211 | 7 April 2006: Next exercise along these lines seems to be wavetank |
---|
212 | data from UQ as conducted by Tom Baldock et al. These experiments |
---|
213 | include friction. Duncan will visit Tom in May and possibly conduct a |
---|
214 | validation project depending on his findings. |
---|
215 | |
---|
216 | |
---|
217 | |
---|
218 | \subsection{Historical Data} |
---|
219 | Andrew McPherson has contacted relevant organisations regarding sources and |
---|
220 | availability of existing post-tsunami field survey data. We agreed |
---|
221 | that a scenario from e.g. Banda Aceh or Thailand (Phuket) |
---|
222 | demonstrating the detailed effect of bathymetric variations would be |
---|
223 | an ideal study and could form the basis of a scientific paper. Matt is |
---|
224 | considering whether this would fit into his research priorities. |
---|
225 | |
---|
226 | Promising leads are |
---|
227 | \begin{itemize} |
---|
228 | \item Suva data (Tariq) |
---|
229 | \item Boxing day event conducted by the Grilli and Asavanant (Stephen Roberts). This has been flagged as a \$15K ANU project in FY 6/7 |
---|
230 | \item The Connection to Sri Lanka (John Schneider) |
---|
231 | \end{itemize} |
---|
232 | |
---|
233 | |
---|
234 | \subsection{Other} |
---|
235 | Validation against analytical solutions is well under way and |
---|
236 | is considered an integral component of the validation process. |
---|
237 | The same is true for the Lake Merimbula tidal validation project. |
---|
238 | Stephen, John Jakeman and Chris are looking after these. |
---|
239 | |
---|
240 | |
---|
241 | |
---|
242 | |
---|
243 | \section{Potential joint PhD projects (GA and ANU)} |
---|
244 | Ole to investigate if GA would fund a PhD student: Project could be |
---|
245 | "Algorithms for augmentation of unstructured grids" or "Algorithms for |
---|
246 | unification of geodesic systems in unstructured grids" the latter |
---|
247 | capturing the notion of being able to model the synoptic, deep water |
---|
248 | wave propagation in latitudes and longitudes with a seemless connection |
---|
249 | to detailed modelling using UTM projections. |
---|
250 | A PhD scholarship is worth about \$20K per annum. |
---|
251 | |
---|
252 | 7 April 2006: We are putting \$10K in the 06-07 budget. |
---|
253 | |
---|
254 | |
---|
255 | \section{Long term aim} |
---|
256 | |
---|
257 | We agreed that having a detailed, reproducible and validated |
---|
258 | inundation scenario from the Boxing Day Tsunami running in parallel |
---|
259 | (and being faster than the sequential code) would be a worthwhile goal. |
---|
260 | |
---|
261 | |
---|
262 | \end{document} |
---|
263 | |
---|
264 | |
---|
265 | |
---|