Originally posted by: SystemAdmin
[shaw said:]
Hello Pierre,
The solution you adopt will really depend on the efficiency of your algorithm vs.
the number of arcs which change value when you go down in the tree. If you are
changing the values of many arcs, then this will incur an overhead in Solver to save
and restore their values on backtracking. If you modify few arcs, it could be
very efficient.
If you want to recompute on backtracking, you need just to store the number of
fails each time you compute the max flow. If the current number of fails is different
from the number of fails the last time you computed the max flow, then it is out
of date and you need to recompute it.
Paul
PS You could you IlcIntSet to maintain the adjacency lists (IlcIntSet is reversible)
#CPOptimizer#DecisionOptimization