Decision Optimization

Decision Optimization

Delivers prescriptive analytics capabilities and decision intelligence to improve decision-making.


#Analytics
#DecisionOptimization
#DecisionOptimization
 View Only
  • 1.  Lazy constraints only checked when an integer-feasible solution is found?

    Posted 06/29/12 11:24 PM

    Originally posted by: J5JK_chao_lei


    The introduction of lazy constraint in the user manual states that "Lazy constraints are only (and always) checked when an integer-feasible solution candidate has been identified".

    This really confuses me, since I am not sure whether lazy constraints are also checked and satisfied when LP relaxation at a new node is solved such that a tighter bound might be produced. This sounds more reasonable to me rather than that lazy constraints are only checked when an integer-feasible solution candidate has been identified.

    Could anyone clarify my confusion? Thanks a lot!
    #CPLEXOptimizers
    #DecisionOptimization


  • 2.  Re: Lazy constraints only checked when an integer-feasible solution is found?

    Posted 07/03/12 07:03 PM

    Originally posted by: SystemAdmin


    It appears that lazy constraint callbacks are only called when CPLEX generates a potential new incumbent. I was working with one today and stuck a print statement in it that executed whenever the callback was entered. It was entered only at those nodes where a new incumbent arose.

    Paul

    Mathematicians are like Frenchmen: whenever you say something to them, they translate it into their own language, and at once it is something entirely different. (Goethe)
    #CPLEXOptimizers
    #DecisionOptimization


  • 3.  Re: Lazy constraints only checked when an integer-feasible solution is found?

    Posted 07/06/12 12:58 AM

    Originally posted by: SystemAdmin


    That is correct. Lazy constraint callbacks are only invoked when a new potential incumbent is found. If you want a callback that is invoked at every node then you need to use a UserCutCallback.
    ATTENTION: By definition a lazy constraint is allowed to cut off integer feasible solutions while a (user) cut may only cut off fractional solutions.
    #CPLEXOptimizers
    #DecisionOptimization


  • 4.  Re: Lazy constraints only checked when an integer-feasible solution is found?

    Posted 07/11/12 04:21 AM

    Originally posted by: J5JK_chao_lei


    Maybe I didn't state my question clear enough. Let me put it in this way: After lazy constraint callbacks is invoked when a new potential incumbent is found and a "lazy" cut is added so that the potential incumbent would be rejected, does this "lazy" cut have any other effects over the model, as like strengthening the best bound or so?
    #CPLEXOptimizers
    #DecisionOptimization


  • 5.  Re: Lazy constraints only checked when an integer-feasible solution is found?

    Posted 07/11/12 04:27 AM

    Originally posted by: SystemAdmin


    The separated lazy constraint is added as a row to the model, so that no future incumbent will ever violate it.
    In that sense it may improve the dual bound of linear relaxations of the model.
    #CPLEXOptimizers
    #DecisionOptimization


  • 6.  Re: Lazy constraints only checked when an integer-feasible solution is found?

    Posted 07/11/12 04:47 AM

    Originally posted by: J5JK_chao_lei


    Thank you very much for your quick response, Daniel.
    #CPLEXOptimizers
    #DecisionOptimization