Issue
The handling of plugins in ropt has changed. The main advantage it is not necessary to specify the name of the backend anymore when configuring an optimizer or a sampler. This means that in principle the backend keywords could be removed from the Everest configuration, simplifying configuration for users. I addition, the code in Everest has become slightly more simple.
This PR updates Everest to use the new ropt code, but retains for now the exact behavior as before, i.e. the backend keywords is still needed or set by default to dakota. I suggest that we revisit the backend keyword in the Everest configuration at a later point and possibly remove it (see issue #4)
Issue The handling of plugins in
ropthas changed. The main advantage it is not necessary to specify the name of the backend anymore when configuring an optimizer or a sampler. This means that in principle thebackendkeywords could be removed from the Everest configuration, simplifying configuration for users. I addition, the code in Everest has become slightly more simple.This PR updates Everest to use the new
roptcode, but retains for now the exact behavior as before, i.e. thebackendkeywords is still needed or set by default todakota. I suggest that we revisit thebackendkeyword in the Everest configuration at a later point and possibly remove it (see issue #4)