- Timestamp:
- Sep 3, 2009, 2:04:19 PM (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
anuga_work/publications/boxing_day_validation_2008/results.tex
r7470 r7473 51 51 hand corner of the figure. The cross marks show the location of 52 52 the pivot line (the region between the uplift and subsided region 53 where the uplift is zero) derived from remote sensing 54 (FIXME(Jane): How was that possible?). All the 53 where the uplift is zero) derived from remote sensing of where there 54 were no changes in the amount of reef or land exposure before and after 55 the earthquake (\cite{meltzner06}). All the 55 56 observational data are from the dataset collated 56 57 by~\cite{chlieh07}.} … … 69 70 sequence of grids was used. The grid resolution of the nested grids 70 71 went from 27 arc seconds in the coarsest grid, down to nine arc seconds 71 in the second grid, three arc seconds in the third grid and finally one arc 72 second in the finest grid near Patong. The computational domain is 72 in the second grid and three arc seconds in the third grid. The computational domain is 73 73 shown in Figure~\ref{fig:computational_domain}. 74 74 … … 118 118 for the \textsc{anuga} model. The interface between the \textsc{ursga} 119 119 and \textsc{anuga} models was chosen to roughly follow the 100~m depth 120 contour along the west coast of Phuket Island. The computational 120 contour along the west coast of Phuket Island. Data from the 121 3 second grid was decimated to match the resolution chosen in ANUGA. 122 The computational 121 123 domain is shown in Figure~\ref{fig:computational_domain}. 122 124 … … 133 135 region in Patong Bay. The coarse resolution was chosen to be 134 136 commensurate with the model output from the \textsc{ursga} model (FIXME (Ole): Richard says that the ursga model used all four grids which would mean that the 135 resolution at the ANUGA boundary was 1 second or about 30 m.137 resolution at the ANUGA boundary was 1 second or about 30 m. 136 138 This is not consistent with my memory and certainly not with us choosing a 137 resolution of 440 m. John, do you remember what the spacing was between the139 resolution of 440 m. John, do you remember what the spacing was between the 138 140 URSGA points? Did we weed them out or did we take them as they were?) 139 141
Note: See TracChangeset
for help on using the changeset viewer.