I keep getting "Error using / Arguments must be numeric, char, or logical. " in bayesopt.

Question

DODO 2023-2-7

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1908395-i-keep-getting-error-using-arguments-must-be-numeric-char-or-logical-in-bayesopt

评论： Jan 2023-2-8

Hi, I'm trying to use "bayesopt", but I keep getting this error.

What did I do wrong?

%% BayesOpt
fxc = @(x) cos(2*pi*(x/4))+exp(x/5);
xvar = optimizableVariable('x',[0,10],'Type','real');
res = bayesopt(fxc,xvar,'MaxObjectiveEvaluations',10,'PlotFcn',[],'AcquisitionFunctionName','lower-confidence-bound','ExplorationRatio',.1);
figure;
plot(res, @plotAcquisitionFunction);
figure;
plot(res,@plotObjectiveModel);
res=resume(res,'MaxObjectiveEvaluation',1);

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Walter Roberson 2023-2-7

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1908395-i-keep-getting-error-using-arguments-must-be-numeric-char-or-logical-in-bayesopt#answer_1166055

doc bayesopt

fun accepts x, a 1-by-D table of variable values, and returns objective, a real scalar representing the objective function value fun(x).

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

Answer 2

Jan 2023-2-7

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1908395-i-keep-getting-error-using-arguments-must-be-numeric-char-or-logical-in-bayesopt#answer_1166065

在 MATLAB Online 中打开

Anonymous functions are compact, but less useful for debugging. Use a normal function instead:

fxc  = @yourFcn;
xvar = optimizableVariable('x',[0,10],'Type','real');
res  = bayesopt(fxc, xvar, 'MaxObjectiveEvaluations', 10, ...
    'PlotFcn', [], 'AcquisitionFunctionName', 'lower-confidence-bound', ...
    'ExplorationRatio', 0.1);
...
    
function y = yourFcn(x)
y = cos(2 * pi * x / 4) + exp(x / 5);
end

Run the code again. Now I'd expect it to fail inside yourFcn. Use the debugger to check the details:

dbstop if error

This let Matlab stop, when an error occurs. Run the code again, and when it stops, examine the class of x in the command window:

class(x)

What do you see?

2 个评论
显示无隐藏无

Walter Roberson 2023-2-7

I had to use dbstop if caught error

Jan 2023-2-8

@DODO, @Walter Roberson: Yes, if the failing code is included in a TRY/CATCH block, "caught error" is the correct trigger to find the line causing the error.

请先登录，再进行评论。