View source for Verbosity

[[Category:System Variables]]


[[Verbosity]] is an Analytica [[System variables|system variable]] that controls how much feedback the system gives to users about the processes it is executing, and is therefore useful with [[Debugging Hints|debugging]].

The variable contains a bit field that controls various functions. The <code>verbosity: 2</code> bit should always be set: it controls whether certain error messages are reported when parsing definitions. 

The value of [[Verbosity]] can be set in the [[Typescript]] window which opens when you press ''Ctrl+' '' (control comma) or the ''F12'' key.

[[Syntax]]:
:<code>'''verbosity''': <value></code>  or  <code>'''verb''': <value></code> 

Possible values:
:<code>1</code> verbose;  controls whether certain error messages are reported when parsing definitions
:<code>2</code> does not print tables unless explicitly requested
:<code>4</code> causes each variable evaluation to be printed out
:<code>8</code> is Filetrace
:<code>16</code> is debug mode
:<code>128</code>  causes the evaluating trace to be indented to show evaluation depth
:<code>134</code> starts verbose tracing with indentation indicating the evaluation depth. This  reveals where in the loop each variable evaluation was called from

==Example==
Let's assume that you get a [[Error Messages/40938|stack overflow error]] when [[Evaluate|evaluating]] a model that contains some recursive [[User-Defined Function|user-defined function]] (a UDF that calls itself) because the termination condition of the function is not satisfied, and you would like to find out where exactly the infinite loop is occurring. To do that,

# Press ''Ctrl+' '' or ''F12'' to open the [[Typescript]] Window.
# In the Typescript window, type  <code>Verbosity: 134</code> to start verbose tracing
# Re-evaluate the model until the stack overflow error appears again.
# Examine the trace in the Typescript window.
# Turn tracing back off by typing <code>Verbosity: 2</code>


If your trace is too long to view in the Typescript window, then use these steps:
# Press ''Ctrl+' '' or ''F12'' to open the Typescript Window.
# In the Typescript window, type 
#: <code>Photo "C:\log.txt"</code>  { the [[Photo]] command logs output that is printed to the Typescript window, to a file; pick your own filename }
#: <code>Verbosity: 134 </code> to start verbose tracing 
# Evaluate the model until the stack overflow error reappears.  After the stack overflow has occurred, press ''Ctrl+' '' or ''F12'' again to return to the Typescript window.
# In Typescript, type:
#: <code>EndPhoto</code> to stop logging to the log file
#: <code>Verbosity: 2</code>  to turn tracing back off and to restore the original value of Verbosity
# Open the log file, "C:\Temp\log.txt", in a text editor such as Notepad. The log will contain a series of lines with a number of dots preceding them. Each dot of indentation will indicate one level of recursion, e.g.

<pre style="background:white; border:white; margin-left: 2em;">
....Evaluating Spinning_Reserves_Di[Time=1801] dloop=263 .
.....Evaluating Minimum_Operating_L3.
.....Evaluating Net_Spinning_Reserve[Time=1801] (dynamic) dloop=263 .
......Evaluating Net_Spinning_Reserve[Time=1800] (dynamic) dloop=263 .
.......Evaluating Net_Spinning_Reserve[Time=1799] (dynamic) dloop=263 .
........Evaluating Net_Spinning_Reserve[Time=1798] (dynamic) dloop=263 .
.........Evaluating Net_Spinning_Reserve[Time=1797] (dynamic) dloop=263 .
..........Evaluating Net_Spinning_Reserve[Time=1796] (dynamic) dloop=263 .
...........Evaluating Net_Spinning_Reserve[Time=1795] (dynamic) dloop=263 .
</pre>

==See Also==
* [[System variables]]
* [[File_System_Typescript_Commands#Photo|Photo]]
* [[Typescript]]
* [[Inspection Commands]]
* [[Debugging Hints]]
* [[Error_Messages/41108]]
* [[Error_Messages/40938]]