-
As is right now, the constraints are ignored in Acados interface. There should be an error message if constraints are detected or actually implemented
-
It seems that changing the solver options for ACADOS can only be done once. If done twice, it fails.
For instance
```python
for i in range (10):
sol = ocp.solve(solver=Solver.ACADOS, solve…
-
The second optimization using ACADOS does not behave the same as the first because ACADOS automatically changes X0. It was decided to hamonize with IPOPT which does not change X0
-
The last node when using Lagrange objective function is ignore in ACADOS while in Ipopt it is targeted. They should behave the same. Out of simplicity and intuitiveness, I think that the behavior that…
-
All is in the title
-
-
Hi,
I am wondering whether you have the plan for finishing the examples in the doc [1](https://docs.acados.org/examples/index.html) or providing a really simple and readable C getting started exam…
-
Because ACADOS cannot deal with such bounds.
-
When compiling code that uses the condensing_qpoases solver and linking against
*libacados.a libqpOASES_e.a libhpipm.a libblasfeo.a*
you get following error messages:
```
libacados.a(math.c.o):…
rienq updated
4 years ago
-
See https://github.com/acados/acados/pull/313