1Blurb:: 2Deactivate Dakota interface features for simplicity or efficiency 3 4Description:: 5The optional \c deactivate specification block allows a user to 6deactivate interface features in order to simplify interface 7development, increase execution speed, and/or reduce memory and disk 8requirements. Any or all of these features may be specified 9concurrently. 10 11\li Active set vector (ASV) control: deactivate so that Dakota expects 12 the same response data (all functions, gradients, Hessian) back 13 from the simulation on every evaluation, instead of only those 14 components required by the method for this particular function 15 evaluation. 16 17\li Function evaluation cache: save memory by not caching the function 18 evaluation history. May result in additional (duplicate) function 19 evaluations. 20 21\li Strict cache equality: allow a relaxed tolerance when detecting 22 duplicate function evaluations. Can be useful when importing data 23 or restarting across machines. 24 25\li Restart file: improve efficiency and eliminate restart file 26 storage at the risk of not being able to recover a failed or 27 partial %Dakota study. 28 29Topics:: 30Examples:: 31Theory:: 32Faq:: 33See_Also:: 34