Closed ruairimoran closed 1 year ago
@smokinmirror I noticed that this line does not perform the projection correctly. It only projects the first coordinate of y
. I suppose alm_set_c
has the wrong dimension.
@smokinmirror I found the culprint: in the auto-generated optimiser, in src/lib.rs
, the set C
is defined using
const SET_C_XMIN :Option<&[f64]> = Some(&[std::f64::NEG_INFINITY,]);
const SET_C_XMAX :Option<&[f64]> = Some(&[0.0,]);
The dimension of these vectors should be 2, not 1.
@smokinmirror you just need to change your definition of set_c
to
set_c = og.constraints.Rectangle([-np.infty, -np.infty], [0, 0])
and the problem will be solved. I mean... not solved, since this is an infeasible problem.
Describe the bug
F1 constraints must belong to the set
c = (-\infty, 0]
. The solver returnsConverged
, but the solution does not satisfy (all of) the constraints.To Reproduce
Steps to reproduce the behavior:
create_solver.py
andrun_solver.py
in a foldercreate_solver.py
create_solver.py
run_solver.py
Converged
x
inrun_solver.py
: this should belong to the set c (but it will be positive)Expected behavior
If the
vehicle
shape overlaps with eitherobstacle
shape, solver should not converge. Otherwise, it should converge.System information:
System/Platform [Laptop]
OS: [Windows]
What is the output of
rustup show
?Default host: x86_64-pc-windows-msvc rustup home: C:\Users\40232020.rustup
installed toolchains stable-x86_64-pc-windows-msvc (default) nightly-x86_64-pc-windows-msvc
active toolchain stable-x86_64-pc-windows-msvc (default) rustc 1.65.0 (897e37553 2022-11-02)
rustc -V
?rustc 1.65.0 (897e37553 2022-11-02)
Additional context
The solver always works as expected with the first obstacle you pass in, but doesn't work for any more passed in
create_solver.py
run_solver.py