1. 27 Apr, 2018 1 commit
    • Tjerk Vreeken's avatar
      Do not use variables for min/max of path goals · b3f098ed
      Tjerk Vreeken authored
      Using variables for the min/max series of path goals resulted in (at
      least) quadratic constraints. These min/max series variables had equal
      bounds, and most solvers remove these variables in the preprocessor of the
      optimization. So although there was no problem for e.g. IPOPT, it was not
      possible for the user or CasADi to easily detect whether the problem was
      linear.
      
      As a concrete example, it was not possible to use CLP (a linear solver),
      because a Hessian check in CasADi would fail. Furthermore, there might be
      solvers that we want to use that do not (by default) support the
      elimination of variables with equal bounds.
      
      Instead of using variables, we can instead specify the min/max series
      as additional constant inputs.
      
      Fixes #1005
      b3f098ed
  2. 14 Feb, 2018 2 commits
  3. 18 Sep, 2017 1 commit
  4. 15 Sep, 2017 5 commits
  5. 30 Aug, 2017 2 commits
  6. 22 Aug, 2017 3 commits
  7. 02 Aug, 2017 1 commit
  8. 01 Aug, 2017 6 commits
  9. 05 Jul, 2017 1 commit
    • Tjerk Vreeken's avatar
      Fix initial state reading from aliases in CSVMixin · f12fb9aa
      Tjerk Vreeken authored
      Also update the test case to set the initial state with an alias. This
      new test case would have failed without the CSVMixin changes made in this
      commit.
      
      Note that the test case for PIMixin has also been updated to keep matching
      the other test case, but that the implementation of aliases in PIMixin
      was already correct.
      
      Regression was introduced in 989632b8.
      f12fb9aa
  10. 22 Jun, 2017 1 commit
  11. 21 Jun, 2017 5 commits
  12. 20 Jun, 2017 1 commit
  13. 15 Jun, 2017 1 commit
  14. 15 May, 2017 3 commits
  15. 25 Apr, 2017 3 commits
  16. 24 Apr, 2017 1 commit
  17. 19 Apr, 2017 1 commit
  18. 17 Feb, 2017 2 commits