[SCIP] The strange behavior of the CONSENFOLP callback assertion

[Abbas Omidi]

Dear support team,

I am working on the problem, and I am willing to use SCIP's*onshdlr*
callback, preferably PySCIPopt, to check how the constraints might be added
to the model. The problem I have is a simple linear program, MILP, that is
solved optimality. I sum up my questions as follows and am wondering if,
you can advise me.

1) As the definition of *consenfolp/consenfops *is very specific and
contains the term *price-and-cut loop*, What does the price-and-cut loop
mean?

2) What is the difference between *consenfolp/consenfops *and *conscheck* when
applied to the model?

2) As my problem has a primal feasible solution, actually optimal one, and
already other callbacks seem to work fine, how is it possible to reject the
constraints/solution by *consenfolp/consenfops*?

3) Is it still necessary to use *conshdlr.createData* when we want to add
the constraint?


(The link <http://listserv.zib.de/pipermail/scip/2023-July/004687.html> to
my previous post)
Best regards
Abbas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserv.zib.de/pipermail/scip/attachments/20230729/70ade14d/attachment.html>