Rody Oldenhuis

Awesome, thanks :)

@ZAFAR:

You are right -- In one of the updates, I changed the order of the input arguments so that they correspond with fmincon(). However, I did NOT update the documentation to reflect these changes.

I'm unfortunately very short on time now, but I will do my best to update optimize() soon.

@Tarek: thank you for the heads up, it has been corrected and a fixed version will be up as soon as they've approved it!

Very nice, and quite useful, of course. The only design choice that I find a little unfortunate is that the formatting of the uicontrols (as pop-up menu, checkbox, etc...) is selected based on the data type of the initial field values. The consequence of this is that I can really only enter doubles and strings as field data.

Sometimes, however, I want the actual value of a field to be cell-valued, e.g., {'a','b','c'}. In your set-up, though, a cell array of strings always gets interpreted as a list of pop-menu options. The same goes with fields that are logical vectors. Sometimes I want a logical vector to be interpreted as the actual data and not to be as format specifiers.

I wonder if you could have had an input syntax like the following

settingsdlg(Scontent, Sformat)

where Scontent is a structure containing the desired field values and S.format is a structure with the same field names, but specifying whether to format as checkbox, pop-up menu, etc...

Dear Oldenhuis,
Actually my problem (let it be 3 variable problem) has one linear equality constraint e.g. Aeq =[1 1 1], beq = 200 and also there is lower and upper bound for each variable e.g. lb = [30 40 50] and ub = [80 100 85]. Let x0 = [60 70 80]. Let the function is fn. There is no iequality constraint
I write the optimize statement as follows

sol=optimize(@fn,x0,[],[],Aeq,beq,lb,ub)

But it did not work and the message comes to be

Error using optimize/check_input (line 466)
Given linear constraint vector [b] has incompatible
size with given [x0].

Error in optimize (line 347)
check_input;

Kindly advise.