You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I notice that for a number of problems that I am running ALPS reports the following lower bound at node 0
Alps0240I Processed 0 nodes, has 0 nodes, best relaxed 1e+75, best feasible 16
This is for a minimization problem where all problems have lower bounds of 0 and upper bounds of 1. How can the best relaxed value exceed the best feasible value for a minimization?
Note also the following odd number being reported for the depth
Alps0260I Quality of the best solution found: 16 ; depth 2147483647
Thanks
The text was updated successfully, but these errors were encountered:
Comment by @mgalati13 created at 2010-08-24 20:01:46
These are probably for cases that solve in the root node and the overall optimal is probably being found before Alps is updated. Either way, Alps should init the best relaxed at -inf, not inf. Ted - can you correct that.
I am not sure about the depth problem. My guess is that it is another initialization issue. It seems to be init'd at INT_MAX instead of 0.
Issue created by migration from Trac.
Original creator: kmartin
Original creation time: 2010-08-23 01:39:39
I notice that for a number of problems that I am running ALPS reports the following lower bound at node 0
Alps0240I Processed 0 nodes, has 0 nodes, best relaxed 1e+75, best feasible 16
This is for a minimization problem where all problems have lower bounds of 0 and upper bounds of 1. How can the best relaxed value exceed the best feasible value for a minimization?
Note also the following odd number being reported for the depth
Alps0260I Quality of the best solution found: 16 ; depth 2147483647
Thanks
The text was updated successfully, but these errors were encountered: