1Blurb:: 2Control how much method information is written to the screen and output file 3Description:: 4Choose from a total of five output levels during the course of a Dakota study. 5If there is no user specification for output verbosity, then the default 6setting is \c normal. 7 8Specific mappings are as follows: 9\li \c silent (i.e., really quiet): 10 silent iterators, silent model, silent interface, quiet approximation, 11 quiet file operations 12\li \c quiet: 13 quiet iterators, quiet model, quiet interface, quiet approximation, 14 quiet file operations 15\li \c normal: 16 normal iterators, normal model, normal interface, quiet approximation, 17 quiet file operations 18\li \c verbose: 19 verbose iterators, normal model, verbose interface, verbose approximation, 20 verbose file operations 21\li \c debug (i.e., really verbose): 22 debug iterators, normal model, debug interface, verbose approximation, 23 verbose file operations 24 25Note that iterators and interfaces utilize the full granularity in verbosity, 26whereas models, approximations, and file operations do not. 27With respect to iterator verbosity, different iterators implement this control 28in slightly different ways (as described below in the method independent 29controls descriptions for each iterator), however the meaning is consistent. 30 31For models, interfaces, approximations, and file operations, \c quiet 32suppresses parameter and response set reporting and \c silent further 33suppresses function evaluation headers and scheduling output. Similarly, 34\c verbose adds file management, approximation evaluation, and global 35approximation coefficient details, and \c debug further adds diagnostics 36from nonblocking schedulers. 37 38Topics:: dakota_output, method_independent_controls 39Examples:: 40Theory:: 41Faq:: 42See_Also:: 43