\documentclass[11pt]{report}

\title{AnuGA Inundation Modelling Project - Planning and Priorities - Draft}
\author{Ole Nielsen, Duncan Gray, Jane Sexton, Nick Bartzis,\\ Trevor Dhu, Neil Corby, Stephen Roberts, ...}


\date{7 February, 2006}		% update before release!
				% Use an explicit date so that reformatting
				% doesn't cause a new date to be used.  Setting
				% the date to \today can be used during draft
				% stages to make it easier to handle versions.

%\release{1.0}			% release version; this is used to define the
				% \version macro

\makeindex			% tell \index to actually write the .idx file

\begin{document}
\maketitle

\section*{Overview}

The ANUGA inundation modelling project is a collaborative effort between
 Geoscience Australia (GA) and the Australian National University
 (ANU). GA is largely responsible for the software development,
 applications to scenario and risk modelling projects as well as
 contributions to the Australian National Research Priorities.  
 ANU is mainly responsible for the mathematical and numerical modelling approach and the continued development of the model. 
 
 
 This
 document outlines the agreed priorities for the inundation modelling
 project predominantly seen from the GA perspective, but including the ANU where appropriate. 
 Priorities are organised into three separate streams focusing at the following objectives: 
 \begin{enumerate}  
   \item Deliverables of specific case studies. These are typically
   tasks that are requested by GA's clients.
   \item Research topics that have emerged and would advance the
   understanding of the science of hydrodynamic inundation
   \item Development and maintenance issues that are necessary for the
   continued health of the software itself.
\end{enumerate} 
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. 

Overarching these three streams is a fourth stream, management, which covers coordination of the FESA project and management of the inundation modelling team.

\section*{Specific case studies (production)}



The list in order of importance but subject to availability of
topographic data and URS/MOST input is

\begin{enumerate} 
  \item Onslow, WA. This study mainly supports the FESA funded WA study, but has synergies with 
    projects in other lists as well (Jane, Ole, Nick)
  \item Wrap up Sydney (Benfield) project including refinements and damage modelling. 
    This project has synergies with the ANUGA Demo initiative (Everyone)
  \item Port Hedland. Also part of the WA project. (Jane, Nick)
  \item Rerun Wollongong with slump (pending better defition of slump sizes) (Nick, Adrian)
  \item NSW state study  
  \item SE Qld study
  \item Hobart 
  \item Other study areas may be identified when the national hazard map has been completed (expected
within the next 12 months) and consultation has occurred with stakeholders.
\end{enumerate}
Given that the production line is in a start-up phase and the needs outlined in the research and development streams, no more than priority 1-2 are expected to complete before 30 June 2006. However, once streamlined, we expect a production rate of about one scenario per month.



\section*{Research topics}

The list is

\begin{enumerate} 
  \item Sensitivity study using Onslow project (Jane, Ole)
  \item Validation (Ole et al with David Burbidge \& Tom Baldock UQ)  
  \item Momentum sink study (Duncan)
  \item Submarine landslide modelling paper with Dr Mueller, Sydney (Jane, Ole, Adrian)  
  \item Probabilistic integration with URS model, pending URS data (Ole, Trevor)    
  \item Automatic definition of mesh-resolution based on data (e.g. depth or gradients). Perhaps use wavelet transforms. 
  \item Effect of debris on flow and damage 
  \item Write ANUGA in term of latitudes and longitudes
  \item Incorporate coriolis effect for large study areas
  \item Revive storm surge model
  \item Riverine flooding
  \item Solution uncertainty (interaction with Hugh Durrant-Whyte and
  Suresh Kumar from USyd)
  \item Scenario database (future); this could complement the ATWS
 operational centre. (how often would it need to be updated, i.e how
 long will the results remain valid?  eg, effect of sediment transport
 affecting local bathymetry, change in sea levels due to climate
 change)
\end{enumerate}
No more than priority 1-4 are expected to complete before 30 June 2006.


\section*{Development and maintenance issues.}

The list is

\begin{enumerate} 
  \item Bug fixing (see tickets in TRAC) - ongoing (Duncan \& Ole)
  \item Integrated damage modelling (Nick?)
  \item Streamlined end-to-end process including production management of files (Ole, Neil, Nick, Jane, Duncan)
  \item Map2PDF vs ArcReader (Neil)
  \item Easy interface to building regions of variable resolution (Duncan)
  \item Sydney demo (Jane, Duncan, Ole)
  \item Deploy parallel version (Ole, Nick)
  \item Userguide, technical documentation and installation process (Everyone)
  \item OSS License (Ole)
  \item Visualisation (Nick, Ole)
  \begin{itemize}
    \item Hand crafted using Houdini
    \item Take Swollen-viewer further, e.g.\ by colour coding quantitios or applying contour plots
  \end{itemize}
  
\end{enumerate}
It is the hope that most of these priorities will be adressed before 30 June 2006.


\section*{Roles and responsibilities}


This is a first cut only. Please comment!


\subsection*{Inundation modelling team}
\begin{enumerate} 
  \item \textbf{Duncan}: Take responsibility for the code development and maintenance.
  Represent the inundation modelling project in the corporate IM context.     
  Take responsibility for one or more research projects, and contribute to production on a needs basis.  
  \item \textbf{Jane}: Coordinate FESA production project, take responsibility for one or 
  more research projects and contribute to production and code development on a needs basis.
  \item \textbf{Nick}: Take responsibility for the production stream, develop visualisation techniques, 
  and contribute to code development on a needs basis.
  \item \textbf{Ole}: Coordinate the inundation modelling project. 
  Manage the balance and requirements between the research, development and production stream. 
  Take responsibility for the code development and maintenance as well as one or more research projects. 
  Contribute to production on a needs basis.    
\end{enumerate}


\subsection*{Stakeholders}
\begin{enumerate} 
  \item \textbf{Adrian}: Provide input to submarine landslide research.
  \item \textbf{Hamish}: Coordinate collection and supply of topographic data.    
  \item \textbf{Neil}: Coordinate development of GIS decision tool. 
    Assist with collection and supply of topographic data.  
  \item \textbf{Stephen}: Contribute to research and further development of hydrodynamic model.   
  \item \textbf{Trevor}: Develop new engagements with external stakeholders such as state governments.  
  \item Others?
\end{enumerate}
    

The allocation to the different streams from the core inundation modelling team in terms of 
4 full time equivalents (FTE) are

\begin{itemize} 
\item \textbf{Production}: 1.25 FTE  (Mainly Nick)
\item \textbf{Research}: 1 FTE
\item \textbf{Code development and maintenance}: 1 FTE
\item \textbf{Management}: 0.75 FTE (0.5 FESA, 0.25 TEAM)
\end{itemize}

        
    
    
\end{document}



