curve-fitting problem: Unrecognized option name 'showstatus' in OPTIMSET ?

Question

Andreas Baas 2019-6-21

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/468285-curve-fitting-problem-unrecognized-option-name-showstatus-in-optimset

回答： Andreas Baas 2023-2-19

在 MATLAB Online 中打开

Hi all,

I'm having problems fitting a custom model because I keep getting an error message I don't know what to do about.

I have vector data X and vector data Y, and I want to curve-fit (nonlinearleastsquares) a custom equation.

Here's a snippet of code:

given: independent data vector X, dependent data vector Y

fo=fitoptions('Method', 'NonlinearLeastSquares', 'StartPoint', [1, 4]);
g = fittype( @(a, b, x) a*((x-b).^2), 'options', fo)
[fitobject,gof,output] = fit(X, Y, g);

This generates an error message:

Error using fit>iFit (line 340)
Unrecognized option name 'showstatus'.  See OPTIMSET for possibilities.
Error in fit (line 108)
[fitobj, goodness, output, convmsg] = iFit( xdatain, ydatain, fittypeobj, ...

I have used curve-fitting with library models without any problems. The error occurs when I try to fit a custom model.

Can anyone help?

Thanks,

Andy

15 个评论
显示 13更早的评论隐藏 13更早的评论

Andreas Baas 2019-6-21

在 MATLAB Online 中打开

Thank you Matt, dpd. I get the error message with your code snippets as well.

I've literally copied&pasted Matt's code and I get the same error as before.

here is my version info:

-----------------------------------------------------------------------------------------------------
MATLAB Version: 9.4.0.813654 (R2018a)
MATLAB License Number: 860095
Operating System: Microsoft Windows 10 Home Version 10.0 (Build 17134)
Java Version: Java 1.8.0_144-b01 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
-----------------------------------------------------------------------------------------------------
MATLAB                                                Version 9.4         (R2018a)
Control System Toolbox                                Version 10.4        (R2018a)
Curve Fitting Toolbox                                 Version 3.5.7       (R2018a)
DSP System Toolbox                                    Version 9.6         (R2018a)
Data Acquisition Toolbox                              Version 3.13        (R2018a)
Global Optimization Toolbox                           Version 3.4.4       (R2018a)
Image Processing Toolbox                              Version 10.2        (R2018a)
Instrument Control Toolbox                            Version 3.13        (R2018a)
Mapping Toolbox                                       Version 4.6         (R2018a)
Neural Network Toolbox                                Version 11.1        (R2018a)
Optimization Toolbox                                  Version 8.1         (R2018a)
Signal Processing Toolbox                             Version 8.0         (R2018a)
Statistics and Machine Learning Toolbox               Version 11.3        (R2018a)
Symbolic Math Toolbox                                 Version 8.1         (R2018a)
Wavelet Toolbox                                       Version 5.0         (R2018a)

Andreas Baas 2019-6-21

OK, I tried the debub stop, see here screenshot with outcome:

Not much more informative, unfortunately...

dpb 2019-6-21

But that does show that the property name 'showstatus' was somehow passed to the optimget routine and as doc shows, there isn't any such property.

Now, how that got generated as a parameter is the kicker...perhaps there is some sort of namespace resolution thingie going on and it did somehow get into a ML object when should have been calling some Java method--TMW has got everything so entwined now it's impossible to know just what might end up using it.

You could just confirm the input arguments to the function when in debug mode, but backtracking to how that got generated is, as you say, probably only something the developers can manage.

Looks like time for an official bug report to me...

请先登录，再进行评论。

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

Answer 1

Matt J 2019-6-21

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/468285-curve-fitting-problem-unrecognized-option-name-showstatus-in-optimset#answer_380303

编辑：Matt J 2019-6-21

Not much more informative, unfortunately...

But now that you've trapped the error with dbstop you can dbup and dbdown through the call stack and investigate how that call was made...

Personally, I wonder why any code in R2018a is using optimset. It should be deprecated in that version in favor of optimoptions. I begin to wonder if code from a previous partially uninstalled version of Matlab has made its way into the mix. A complete, clean reinstall of Matlab might be necessary. "Clean" means you delete the entire R2018a install folder before re-installing.

2 个评论
显示无隐藏无

dpb 2019-6-21

编辑：dpb 2019-6-22

"I wonder why any code in R2018a is using optimset. It should be deprecated in that version in favor of optimoptions"

But, TMW has made such a convoluted mess out of all these it's impossible to know what is/isn't "the right stuff!" The doc for optimset says optimoptions is recommended instead of optimset for all solvers except fzero, fminbnd, fminsearch, and lsqnonneg" until they've changed their tune in current release. It's absolutely impossible to keep up... :(

To make it even worse, optimset and optimoptions are defined for the optimization routines in the Optimization Toolbox; fit and fitoptions belong to their own TB and have a different class name.

It's just a proverbual bollux of competing stuff stumbling all over itself. There doesn't seem to be any one coherent design for Matlab at all, any more...

J.D. Johnston 2023-2-18

编辑：J.D. Johnston 2023-2-18

Not sure if this is helpful, but I had the same error. It had something to do with one of the custom subroutines included in my PATH. When I revised everything in PATH to just the basics, custom fitting worked fine.

请先登录，再进行评论。

Answer 2

Andreas Baas 2023-2-19

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/468285-curve-fitting-problem-unrecognized-option-name-showstatus-in-optimset#answer_1174945

Thanks J.D.; yes I found the same resolution: I removed all my own scripts and functions from the PATH and then it worked. I must have had a .m file in there with the same name as something in this OPTIMSET thing (though I certainly didn't have a script or function called "showstatus"...)