Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Manuals/Bibliography/commoncommands.tex
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@
tabsize=4,
rulecolor=,
language=Fortran,
basicstyle=\footnotesize\ttfamily,
basicstyle=\small\ttfamily,
upquote=true,
aboveskip={\baselineskip},
belowskip={\baselineskip},
Expand Down
96 changes: 4 additions & 92 deletions Manuals/FDS_User_Guide/FDS_User_Guide.tex
Original file line number Diff line number Diff line change
Expand Up @@ -1029,7 +1029,6 @@ \subsection{Multiple Meshes}

For cases involving many meshes, you might want to assign them colors using either the character string \ct{COLOR} or the integer triplet \ct{RGB}. You may also want to consider using the multiplying feature to easily create a 3-D array of meshes. See Sec.~\ref{info:MULT} for details.

One other useful parameter for larger MPI jobs is called \ct{VERBOSE} on the \ct{MISC} line. This logical parameter suppresses information related to MPI process and OpenMP thread assignments that is printed to the diagnostic output files. By default, its value is \ct{T} for MPI jobs involving 50 or less processes, and \ct{F} for larger jobs.


\subsection{Mesh Alignment}
Expand Down Expand Up @@ -12800,7 +12799,7 @@ \section{\texorpdfstring{{\tt MISC}}{MISC} (Miscellaneous Parameters)}
\ct{TURBULENCE_MODEL} & Character & Section~\ref{info:LES} & & \ct{'DEARDORFF'} \\ \hline
\ct{TURBULENT_DEPOSITION} & Logical & Section~\ref{info:deposition} & & \ct{T} \\ \hline
\ct{UNFREEZE_TIME} & Real & Section~\ref{info:FREZ} & & \\ \hline
\ct{VERBOSE} & Logical & Section~\ref{info:multimesh} & & \\ \hline
\ct{VERBOSE} & Logical & Section~\ref{out:file} & & \ct{F} \\ \hline
\ct{VISIBILITY_FACTOR} & Real & Section~\ref{info:visibility} & & 3 \\ \hline
\ct{VN_MAX} & Real & Section~\ref{info:VN} & & 1.0 \\ \hline
\ct{VN_MIN} & Real & Section~\ref{info:VN} & & 0.8 \\ \hline
Expand Down Expand Up @@ -14608,6 +14607,9 @@ \section{Diagnostic Output ({\tt .out})}

Following the completion of a successful run, a summary of the CPU usage per subroutine is listed in the file called \ct{CHID_cpu.csv} (Section~\ref{out:CPU}). This is useful in determining where most of the computational effort is being placed.

Add \ct{VERBOSE=T} to the \ct{MISC} line to add addiational information about time usage to the diagnostic file.


\section{Heat Release Rate and Related Quantities (\ct{_hrr.csv})}
\label{out:hrr}

Expand Down Expand Up @@ -14691,96 +14693,6 @@ \section{CPU Usage Data}
\section{Time Step Data}
\label{out:timestep}

The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
\begin{lstlisting}
Time Step,Wall Time,Step Size,Simulation Time,CPU Time
\end{table}

The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.

\section{Time Step Data}
\label{out:timestep}

The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
\begin{lstlisting}
Time Step,Wall Time,Step Size,Simulation Time,CPU Time
\end{table}

The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.

\section{Time Step Data}
\label{out:timestep}

The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
\begin{lstlisting}
Time Step,Wall Time,Step Size,Simulation Time,CPU Time
\end{table}

The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.

\section{Time Step Data}
\label{out:timestep}

The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
\begin{lstlisting}
Time Step,Wall Time,Step Size,Simulation Time,CPU Time
\end{table}

The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.

\section{Time Step Data}
\label{out:timestep}

The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
\begin{lstlisting}
Time Step,Wall Time,Step Size,Simulation Time,CPU Time
\end{table}

The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.

\section{Time Step Data}
\label{out:timestep}

The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
\begin{lstlisting}
Time Step,Wall Time,Step Size,Simulation Time,CPU Time
\end{table}

The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.

\section{Time Step Data}
\label{out:timestep}

The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
\begin{lstlisting}
Time Step,Wall Time,Step Size,Simulation Time,CPU Time
\end{table}

The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.

\section{Time Step Data}
\label{out:timestep}

The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
\begin{lstlisting}
Time Step,Wall Time,Step Size,Simulation Time,CPU Time
\end{table}

The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.

\section{Time Step Data}
\label{out:timestep}

The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
\begin{lstlisting}
Time Step,Wall Time,Step Size,Simulation Time,CPU Time
\end{table}

The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.

\section{Time Step Data}
\label{out:timestep}

The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
\begin{lstlisting}
Time Step,Wall Time,Step Size,Simulation Time,CPU Time
Expand Down