Changeset 3439
- Timestamp:
- Aug 2, 2006, 2:55:51 PM (18 years ago)
- Location:
- documentation
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
documentation/planning/priorities.tex
r3381 r3439 194 194 \item Streamlined end-to-end process including production management of files (Nick + Hamish, Neil, Ole, Jane, Duncan) 195 195 In addition to Nick's automatic log of scripts generating the data, also log username and ANUGA version if possible. 196 \item The Black Screen of Death - ill-conditioned system, non-convergence of conjugate gradient solver (Jane). Has now become an issue of dealing with duplicate vertices, see ticket:43 197 196 198 197 \item Map2PDF vs ArcReader (Neil, Lisa) 199 198 \item Easy interface to building regions of variable resolution (Duncan) … … 209 208 \end{itemize} 210 209 \item Automatic coastline buffering. 211 210 \item Improve memory efficiency of mesh generator. 212 211 \end{enumerate} 213 212 It is the hope that most of these priorities will be adressed before 30 June 2006. … … 228 227 \item IM 229 228 \item TRIM 230 \item budget231 229 \end{itemize} 232 230 Take responsibility for one or more research projects, and contribute to production on a needs basis. -
documentation/requirements/anuga_API_requirements.tex
r3230 r3439 104 104 105 105 \chapter{Internal API} 106 107 \section{Point files - ideas} 108 109 Currently title information must be given for points files. The api 110 could be changed so the titles are an input. These titles could be 111 used if the file does not have titles. This should reduce the amount 112 of file pre-processing. 113 114 Remove the ability of points files to have geo-refferencing 115 information. The values be absolute. Cons - zone information is lost. 116 Pros - text files will be a csv format. 117 106 118 107 119 \section{Damage Model - Requirements} … … 175 187 \item damage cost to content 176 188 \item damage cost to structure 189 \item inundation above ground height 177 190 \end{itemize} 178 191 -
documentation/user_manual/anuga_user_manual.tex
r3275 r3439 2092 2092 one UTM zone. However, the computation will use that of the mesh for 2093 2093 numerical stability. 2094 2095 When generating a mesh it is assumed that polygons do not cross. 2096 Having polygons tht cross can cause the mesh generation to fail or bad 2097 meshes being produced. 2094 2098 2095 2099
Note: See TracChangeset
for help on using the changeset viewer.