|
[Sponsors] |
February 25, 2016, 04:23 |
Unintuitive dakota behavior?
|
#1 |
New Member
Benoît Bidaine
Join Date: Feb 2016
Posts: 1
Rep Power: 0 |
I am using Sandia's dakota optimization tool (Design Analysis Kit for Optimization and Terascale Applications) and I understood that some of you also do so.
I am wondering about 2 "unintuitive" behaviors of several SCOLIB algorithms. - The DIRECT algorithm "DIviding RECTangles" can receive a maximum number of evaluations as input. However this maximum is not strictly enforced. Could you explain why? - The COBYLA (Nelder-Mead extension) and Pattern Search algorithms start to probe the design space "at the bottom left", i.e., for the lower bound of all optimization parameters. Is there some reason for this? Would it be possible to start from another point, e.g., the middle or a user-defined location? Thanks a lot in advance for your answers! |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Odd behavior on the outlet | a_habib | OpenFOAM Pre-Processing | 1 | January 7, 2016 14:04 |
Weird time step initialization behavior - Wave generation model | liadpaskin | CFX | 3 | July 11, 2015 06:21 |
behavior of two phase flow in a pipe | Sonia84 | FLUENT | 5 | September 17, 2013 16:31 |
[ANSYS Meshing] difference between hard/soft behavior in sizing in ANSYS meshing? | swamy339 | ANSYS Meshing & Geometry | 1 | August 19, 2013 13:38 |
CFX-Solver, issue with convergence behavior | Andy | CFX | 7 | September 5, 2006 03:24 |