1Blurb::
2Hessians will not be used
3
4Description::
5The \c no_hessians specification means that the method does not
6require %Dakota to manage the computation of any Hessian
7information. Therefore, it will neither be retrieved from the
8simulation nor computed by %Dakota. The \c no_hessians keyword is a
9complete specification for this case. Note that, in some cases,
10Hessian information may still be being approximated internal to an
11algorithm (e.g., within a quasi-Newton optimizer such as \c
12optpp_q_newton); however, %Dakota has no direct involvement in this
13process and the responses specification need not include it.
14
15Topics::
16Examples::
17Theory::
18Faq::
19See_Also::	responses-numerical_hessians, responses-quasi_hessians, responses-analytic_hessians, responses-mixed_hessians
20