First of all, it looks like P is maybe supposed to be restricted to be a positive number, and when it's not, your function returns a complex number. However, fzero doesn't respect bounds on the search variable (P in your case): it looks for any value of P that zeros the function, regardless of whether P is postiive or negative. If it encounters a complex function value at some point, however (e.g., in your case if it evaluates F(P) for P<0), fzero doesn't know how to proceed, so it stops and reports an error. This is what you're seeing I believe.
There are various ways you can fix this problem, but the simplest to implement in your case is probably just to do a variable transformation like logP = log(P), P = exp(logP). For any real value of logP, P will be positive here, so you can use fzero to search among values of logP instead of directly for P. Here's how you might implement this:
% Replace the first line of your posted code with the following two:
syms logP
P = exp(logP);
.
. % Then everything is the same until...
.
% replacing what you had, starting from the line P1=[];
logP1=[];
for j = log(0.01:10)
logPP = fzero(F, j);
logP1 = [logP1; logPP];
end
P1 = exp(logP1);
P_cr = min(P1(P1 > 0))
I think this should do what you want.
A couple of other comments/pointers:
- Do you really need to do this with symbolic variables? Couldn't you just write a regular MATLAB function called F.m that contains everything up to just before you start the fzero loop, but where logP is the argument passed into the function, and excluding the syms and the call to matlabFunction? Symbolic math is slow, so if you can avoid it you should.
- You have some crazy scaling on these values. For values of P between 0 and 10, the absolute value of F is on the order of 10^(-16) or smaller, but if you inspect F, these values are arrived at using some intermediate numbers that are on the order of like 10^(+15). That tells me that your F value is likely seriously compromised by numerical precision issues. Are you sure you haven't made a mistake somewhere in your code? It would be pretty unusual to encounter something like this in the real world.
