gevfit error: Operands to the || and && operators must be convertible to logical scalar values

Hello,

Using Matlab R2018b, I just run an example GEV Distribution

blocksize = 1000;

nblocks = 250;

rng default % For reproducibility

t = trnd(5,blocksize,nblocks);

x = max(t);

% 250 column maxima

paramEsts = gevfit(x)

I got the error message:

Operands to the || and && operators must be convertible to logical scalar values.

Error in gevfit (line 74)

if n == 0 || ~isfinite(rangex)

Error in huy_test_stats (line 9)

paramEsts = gevfit(x);

Does it a bug? or how could it be solved?

Thanks

[Roby Pad]

Hello, I have the very same problem which started all of a sudden a couple of days ago. I have Matlab2023b version, and I have just tried unistalling and reinstalling again, but it doesn't work.

Can someone help me?

Roby

Answer 1

[the cyclist]

That code works for me, in both 2018b and 2019a.

Does this happen with a freshly started instance of MATLAB?

If so, you might want to use the which command to check whether you are calling the functions from the places you expect. Another common error is to name a variable the same as a function.

[the cyclist]

Copied tanq's comment here, instead of it being an "answer":

===================

This error happens to me in both MATLAB 2016a and 2018b as I am testing two different pcs. Here is: which gevfit for

C:\Program Files\MATLAB\R2018b\toolbox\stats\stats\gevfit.m

I have changes the variables, but the error is still the same. Not sure why

[the cyclist]

Strange. Can you breakpoint the code just before this function gets called, save the workspace into a MAT file, and upload the file?

[wave_buoys]

Dear the cyclist,

the problem was solved after reinstalling MATLAB (the same version 2018b)

Have a great day!

[Colin]

Very old thread here, but I just had the same problem and this appears to be the only thread directly addressing it. What worked for me (using R2023a) was to go into the toolbox/stats/stats/gevfit.m function and change line 73 from

rangex=range(x);

to

rangex = xmax-xmin;

Something seems buggy with the range function, in other words, at least in this setting.