Details

  • Type: Bug Bug
  • Status: Reopened Reopened
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: 2.2.2, 2.2.3, 2.3.0
  • Fix Version/s: 2.3.1
  • Component/s: pseudo
  • Security Level: Public (Everybody can see)
  • Labels:
    None

Description

The solver is not properly cleaned up once an optimal solution is found.
Literals propagated at decision level 0 by pseudo boolean constraints used during the optimization are not properly removed.

While this does not affect our major tools (PB or MAXSAT solvers) since they aim only at finding one optimal solution, it is an issue when one wants to find several optimal solutions. See TestLonca to see the problem in action.

Activity

Hide
Daniel Le Berre added a comment -

That issue becomes critical to be able to do lexico optimization on weighted optimization functions (i.e. in p2cudf).

Show
Daniel Le Berre added a comment - That issue becomes critical to be able to do lexico optimization on weighted optimization functions (i.e. in p2cudf).
Hide
Daniel Le Berre added a comment -

That issue is our show stopper for release 2.3.1. Need to be fixed ASAP.

Show
Daniel Le Berre added a comment - That issue is our show stopper for release 2.3.1. Need to be fixed ASAP.
Hide
Daniel Le Berre added a comment -

Added a potential fix in r1084 for MaxWatchPb constraints. Need to be adapted to MinWatch too.

Show
Daniel Le Berre added a comment - Added a potential fix in r1084 for MaxWatchPb constraints. Need to be adapted to MinWatch too.
Hide
Daniel Le Berre added a comment -

Fixed the last issue in r1092.

Show
Daniel Le Berre added a comment - Fixed the last issue in r1092.
Hide
Daniel Le Berre added a comment -

The fix breaks 15 tests cases on our functional tests!!!!

Show
Daniel Le Berre added a comment - The fix breaks 15 tests cases on our functional tests!!!!

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated: