Changeset 2742
- Timestamp:
- Apr 21, 2006, 8:45:04 AM (19 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
documentation/user_manual/anuga_user_manual.tex
r2741 r2742 1852 1852 This is for example useful in conjunction with a file_boundary, which may start hours before anything hits the model boundary. By assigning a later time for the model to start, computational resources aren't wasted. 1853 1853 1854 \subsubsection{Can I change values for any quantity during the simulation?} 1855 Yes, using \code{domain.set_quantity()} inside the domain.evolve loop you 1856 can change values of any quantity. This is for example useful if you wish to 1857 let the system settle for a while before assigning an initial condition. Another example would be changing the values for elevation to model e.g. erosion. 1858 1859 \subsubsection{Can I change boundary conditions during the simulation?} 1860 Not sure, but it would be nice :-) 1861 1854 1862 \subsubsection{Why does a file\_function return a list of numbers when evaluated?} 1863 Currently, file\_function works by returning values for the conserved 1864 quantities \code{stage}, \code{xmomentum} and \code{ymomentum} at a given point in time and space as a triplet. To access e.g.\ \code{stage} one must specify element 0 of the triplet returned by file\_function. 1855 1865 1856 1866 \subsubsection{Which diagnostics are available to troubleshoot a simulation?}
Note: See TracChangeset
for help on using the changeset viewer.