- What do you get if you call fun(x0) before you call fmincon ?
- Your constraints on P are linear - they can be put in matrix A and vector b:
FMINCON with multiple constraints
8 vues (au cours des 30 derniers jours)
Afficher commentaires plus anciens
Víctor García
le 20 Mai 2021
Commenté : Alan Weiss
le 20 Mai 2021
Hello, I am new with the optimization tool of MATLAB and I have two question regarding my optimization function. I have a function with a vector P[1x6] as input and only one scalar output which I want to optimize. Before setting the constraints, I already have a error:
FMINCON requires all values returned by functions to be of data type double.
But my output it's an scalar, so I'm a bit confused. Here my code:
fun = @facturade;
A = []; b = []; Aeq = []; beq = [];
lb = [0 0 0 0 0 0];
ub = [150 150 150 150 150 150];
x0 = [100 100 100 100 100 100];
%nonlcon = @const;
[x,fval] = fmincon(fun,x0,A,b,Aeq,beq,lb,ub)
Then, I would like to know how to write multiple constrains for the problem, such as:
P(1)<=P(2); P(2)<=P(3); P(3)<=P(4); P(4)<=P(5); P(5)<=P(6);
For what I've seen, it's posible with nonlcon function, but as P it's my input vector for my function fun, I'm not sure how to write the function.
6 commentaires
Torsten
le 20 Mai 2021
Modifié(e) : Torsten
le 20 Mai 2021
Insert a print command for the calculated scalar directly in function facturade. What is the output to the screen ?
Further, it seems facturade returns a result of type single, not double. I don't know how this happens since on the terminal where I work, I'm not able to download and read your function file.
Réponse acceptée
Alan Weiss
le 20 Mai 2021
I think that your fracturade function is returning data type SINGLE. Perhaps the quickest fix is to include the following call just before the end of the function:
y = double(y);
A better fix would be to determine why the output is single to begin with and fix that. But calling double will enable you to get on with your work.
Alan Weiss
MATLAB mathematical toolbox documentation
3 commentaires
Alan Weiss
le 20 Mai 2021
Torsten's comment indicates the reason why: the finite difference steps are too small to get a nonzero gradient estimate. You really need more precision in your calculation.
Alan Weiss
MATLAB mathematical toolbox documentation
Plus de réponses (0)
Voir également
Catégories
En savoir plus sur Solver Outputs and Iterative Display dans Help Center et File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!
