Originally posted by: MarkusS.

Hello!

I am using the parameter UseCutFilter in an add(...) in LazyConstraintCallback and get CPLEX Error 1006 as result. With the other two possible parameters, I do not get the error. Has someone an idea why this happens? I am also using add(...) in a UserCutCallback with UseCutFilter, can this cause the problem?

Moreover, what is the default behaviour? (i.e. if I only use add(...) without parameter)
#CPLEXOptimizers
#DecisionOptimization

Originally posted by: SystemAdmin

The "UseCutFilter" value means that CPLEX can decide to not use the cut that you provide.
In a lazy constraint callback, you are generating cuts to cut off an invalid solution.
Thus, in a lazy constraint callback, using the "UseCutFilter" value would mean that CPLEX could decide to not cut off the invalid solution.
This does not make sense, so this value is not allowed for the lazy constraint callback.
Tobias
#CPLEXOptimizers
#DecisionOptimization

Originally posted by: SystemAdmin

Tobias already explained why UseCutFilter is not allowed for lazy constraint callbacks. The default value is UseCutForce. Please also refer to the reference documentation here (C++) or here.
#CPLEXOptimizers
#DecisionOptimization