- Timestamp:
- Aug 21, 2008, 4:32:14 PM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
anuga_core/documentation/user_manual/anuga_user_manual.tex
r5657 r5672 2254 2254 appropriate segments for each conserved quantity. 2255 2255 2256 Optional argument \code{default_boundary} can be used to specify another boundary object to be used in case model time exceeds the time availabel in the file used by \code{File\_boundary}. 2257 The default_boundary could be a simple Dirichlet condition or even another File\_boundary 2256 Optional argument \code{default\_boundary} can be used to specify another boundary object to be used in case model time exceeds the time availabel in the file used by \code{File\_boundary}. 2257 The \code{default\_boundary} could be a simple Dirichlet condition or 2258 even another \code{File\_boundary} 2258 2259 typically using data pertaining to another time interval. 2259 2260 \end{classdesc} 2260 2261 2261 2262 \begin{classdesc}{Field\_boundary}{Boundary} 2263 Module: \module{shallow\_water.shallow\_water\_domain} 2264 2265 This method works in the same way as \code{File\_boundary} except that it 2266 allows for the value of stage to be offset by a constant specified in the 2267 keyword argument \code{mean\_stage}. 2268 2269 This functionality allows for models to be run for a range of tides using 2270 the same boundary information (from .sts, .sww or .tms files). The tidal value 2271 for each run would then be specified in the keyword argument 2272 \code{mean\_stage}. 2273 If \code{mean\_stage} = 0.0, \code{Field\_boundary} and \code{File\_boundary} 2274 behave identically. 2275 2276 2277 Note that if the optional argument \code{default\_boundary} is specified 2278 it's stage value will be adjusted by \code{mean\_stage} just like the values 2279 obtained from the file. 2280 2281 See \code{File\_boundary} for further details. 2282 \end{classdesc} 2262 2283 2263 2284 %%%
Note: See TracChangeset
for help on using the changeset viewer.