Constraint tolerance setting is not working
조회 수: 7 (최근 30일)
이전 댓글 표시
I'm using fmincon for optimizing a system for trajectory optimization. Recently, my optimization problem seems to go well below 1e-06 feasibility for the 'interior point' solver. For this project, I will have to perform multiple trajectory optimizations and hence want my sovler to stop < 1e-06 feasibility. When I add the option of constraint tolerance, the solver continues to further iterate. How do I tackle this problem. I found the same problem wiith StepTolerance option as well
댓글 수: 0
답변 (2개)
Matt J
2025년 4월 24일
편집: Matt J
2025년 4월 24일
You need to demonstrate the problem with code, but based on your description, nothing is obviously wrong as far as the constraint tolerance is concerned. Even though you may see the constraint tolerance met, it doesn't mean an optimal point has been found yet. Imagine if you had no constraints. Then the constraint tolerance would be satisfied vacuously at every iteration, but of course it would be wrong for the solver not to iterate...
I found the same problem wiith StepTolerance option as well
That, you would need to demonstrate for us.
댓글 수: 3
Matt J
2025년 4월 24일
Yes, you can just set the objective function to a constant, e.g.,
f=@(x) 0
Then, all points will be optimal and the only criterion fmincon will use for stopping is satisfaction of the constraints.
Matt J
2025년 4월 24일
Alternatively, you can implement your own stopping criterion via the OutputFcn option,
Catalytic
2025년 4월 24일
It is a classic mistake to define the stopping tolerances with optimoptions, but forget to pass them to fmincon, as in -
options=optimoptions('fmincon','StepTolerance',1e-6,'ConstraintTolerance',1e-6);
x = fmincon(fun,x0,A,b,Aeq,beq,lb,ub,nonlcon) %Forgot to give options to fmincon
I wonder if that may be why you aren't seeing your settings obeyed.
댓글 수: 3
Matt J
2025년 4월 25일
편집: Matt J
2025년 4월 25일
That looks alright, to me at least. But as I said in my answer, if you have such little interest in achieving the optimum of the objective, you may as well just set it to a constant.
Aside from that, a few miscellaneous remarks:
lb = [-1500; 0; -10; 0; -100; -0.5*pi; -0.5*pi; -0.5*pi; -0.5*pi; -0.5*pi; -0.5*pi; -50000;
-50000; -50000]; %lower bound of states, control variables and time
lb=[repelem(lb,n);0];
ub = [1000; 1500; 2000; 0; 0; 100;
0.5*pi; 0.5*pi; 0.5*pi; 0.5*pi; 0.5*pi; 0.5*pi; 50000;
50000; 50000]; %upper bound of states, control variables and time
ub=[repelem(ub,n);2000];
(2) Your unknown variables seem to have very different scales. It can sometimes help performance to change units to make them more comparable in scale, for example, by expressing any angles in degrees instead of radians.
참고 항목
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!