MATLAB Answers

Anonymous function to class property method.

17 views (last 30 days)
I have a situation somewhat like the following mockup:
absfoo.m
classdef (Abstract) absfoo
methods (Abstract)
[f] = objfun(o, x)
[c, ceq] = confun(o, x)
end
end
confoo.m
classdef confoo < absfoo
methods
function [f] = objfun(o, x)
f = sin(sum(x.^2));
end
function [c, ceq] = confun(o, x)
c(1) = cos(0.1+x(1).^2);
c(2) = x(1)+x(2);
ceq = [];
end
end
end
bar.m
classdef bar
properties
myfoo
end
methods
function runme(o)
x0 = [0 1];
fmincon(@o.myfoo.objfun,x0,[],[],[],[],[],[],@o.myfoo.confun)
end
end
end
runscr.m
clear all
mf = confoo()
b = bar();
b.myfoo = mf;
b.runme()
Running runscr results in an error message similar to this:
Undefined function or variable 'o.myfoo.objfun'.
Error in fmincon (line 536)
If I add a wrapper method in bar, I can work around this error -- but I'd like to be able to do without the wrapper.
Edited to add commas to fmincon argument list and also empty lb, ub arguments per Steven's correction.

  0 Comments

Sign in to comment.

Accepted Answer

Steven Lord
Steven Lord on 10 Jan 2020
Note: you shouldn't call your class bar as that already has a meaning in MATLAB.
Use this:
fmincon(@(x) objfun(o.myfoo, x),x0,[],[],[],[],[],[],@(x) confun(o.myfoo, x))
The object o.myfoo isa confoo while x will be a double array. This means confoo is the dominant class. By the procedure listed here MATLAB will call the objfun method of the confoo class to call when fmincon tries to evaluate the anonymous objective function. The same holds for confun.
In addition to changing the objective and nonlinear constraint functions I had to add commas between the A, b, Aeq, and beq inputs as well as adding the lb and ub inputs as empty inputs.

  5 Comments

Show 2 older comments
Rob McDonald
Rob McDonald on 10 Jan 2020
That checks out. I pretty much learned Matlab circa v5.0. Of course, I still think of anonymous functions as a cool 'new' feature.
Steven Lord
Steven Lord on 10 Jan 2020
I recommend against using the "beyond the options argument" approach for a couple reasons.
First, as Walter said that approach hasn't been documented in a very long time. Older functions (like fmincon) still accept that approach mainly for backwards compatibility purposes.
Second, using anonymous functions or one of the other techniques given in the "Parameterizing Functions" page to which the fmincon documentation page links allows you to pass those parameters only into the functions that use them. If you were to specify the parameters after the options, all the functions (objective, nonlinear constraint, and any that you specify in the options structure itself like the OutputFcn and PlotFcn) that you pass into fmincon must accept all those parameters regardless of whether or not they use them.
Finally, newer (relatively speaking) functions, especially those introduced since release R14 back in 2004 (which introduced anonymous functions) likely will not accept that approach.
Walter Roberson
Walter Roberson on 10 Jan 2020
Also because of the way that it examines arguments to deduce which calling sequence you are using, there are circumstances under which it can confuse an extra parameter as being one of the regular parameters. This is documented deep in the comments of the code.

Sign in to comment.

More Answers (0)

Sign in to answer this question.

Products


Release

R2017b