Changeset 4205

Timestamp:

Feb 1, 2007, 9:45:42 AM (18 years ago)

Author:

ole

Message:

Added a FAQ about model time based on Matt Barnes' question.

File:

• anuga_core/documentation/user_manual/anuga_user_manual.tex (modified) (3 diffs)

anuga_core/documentation/user_manual/anuga_user_manual.tex

@@ -763 +763 @@
 
 \subsection{Changing boundary conditions on the fly}
+\label{sec:change boundary}
 
 Here is the code for the second version of the channel flow \file{channel2.py}:
@@ -789 +790 @@
     domain.set_boundary({'right': Bo})
 \end{verbatim}}
-This type of dynamically varying boundary could for example be used to model the 
+This type of dynamically varying boundary could for example be 
+used to model the 
 breakdown of a sluice door when water exceeds a certain level. 
 
@@ -3332 +3334 @@
 
 \subsubsection{Can I change boundary conditions during the simulation?}
-Not sure, but it would be nice :-)
+Yes - see example on page \pageref{sec:change boundary} in Section 
+\ref{sec:change boundary}.
+
+\subsubsection{How do I access model time during the simulation?}
+The variable \code{t} in the evolve for loop is the model time.
+{\small \begin{verbatim}
+    for t in domain.evolve(yieldstep = 0.1, duration = 4.0):
+        if t > 15:
+            <Do something>
+\end{verbatim}}
+The model time can also be accessed through the public interface \code{domain.get\_time()}, or changed (at your own peril) through \code{domain.set\_time()}.
+
 
 \subsubsection{Why does a file\_function return a list of numbers when evaluated?}