The planning horizon is stored as a static IntervalIntDomain in HorizonFilter, the accesssor for which returns it as a mutable reference. This means that successive Solvers configured with different horizons will stomp on prior Solvers' horizons.
Comment #1
Posted on Feb 26, 2011 by Grumpy LionThe attached TestCC.cpp prints the following
Horizon 1 before set [-4503599627370495, 4503599627370495] Horizon 2 before set [-4503599627370495, 4503599627370495] Horizon 1 after set [123, 456] Horizon 2 after set [123, 456] Engines the same 0 Solvers the same 0 All good
- TestCC.cpp 1.12KB
Comment #2
Posted on Apr 20, 2011 by Happy Ox(No comment was entered for this change.)
Comment #3
Posted on Aug 17, 2011 by Happy Ox(No comment was entered for this change.)
Comment #4
Posted on May 30, 2012 by Happy Ox(No comment was entered for this change.)
Comment #5
Posted on Sep 12, 2014 by Swift HippoFixed in r6747
Status: Fixed
Labels:
Type-Defect
Priority-High
Component-Solver
Usability
Milestone-EUROPA-2.7